tyt10fi.htm

一个学习tcp/ip协议的教程

Userid for logging in on 147.120.0.1? tparker

331 Password required for tparker.

Password for logging in as tparker on 147.120.0.1? abcdefg

230 User tparker logged in.

ftp:147.120.0.1> ls

.profile

.lastlogin

.odtpref

trash

Initial.dt

XDesktop3

Transferred 265 bytes in 0 seconds

226 Transfer complete.

ftp:147.120.0.1&gt; exit</FONT></PRE><P>This session, which displayed the listing of files on the SCO UNIX server, shows that the ftp command worked properly. The FTP session was closed with the command exit.<BR><P>Following the DOS-based test, start Windows (if it was installed) and ensure that the applications within the PC/TCP Applications program group are available and working. If problems are encountered with Windows starting, it is likely that an error was made in the SYSTEM.INI file. Check the previous instructions for the correct configuration.<BR><P>After all that, the ftp Software PC/TCP system is installed and configured properly. The DOS machine can now be used for TCP/IP applications such as ftp and telnet. If some of the more powerful protocol features were installed, they are also usable. The DOS-based machine installation is now completed. The PC/TCP documentation contains instructions for using the system, as well as fine-tuning the kernel. It also helps users create gateways, routers, mail servers, and several other TCP/IP-related features.<BR><BR><A ID=E68E98 NAME=E68E98></A><H3 ALIGN=CENTER><CENTER><FONT SIZE=5 COLOR=#FF0000><B>Windows-Based TCP/IP: NetManage's Chameleon</B></FONT></CENTER></H3><BR><P>NetManage produces a line of TCP/IP-based software specifically for Windows, Windows 95, and Windows for Workgroups. These applications are designed to provide full access to TCP/IP utilities through the Windows environment. NetManage's line of products includes a basic TCP/IP stack (called Newt), as well as full TCP/IP application packages in several forms, all called Chameleon. The system is also available for Windows NT. You are installing Chameleon on a Windows for Workgroups 3.11 machine on the sample network.<BR><P>Chameleon uses the standard NDIS (Network Device Interface Specification) or the ODI (Open Data Link Interface) for communicating with the network interface card. This enables any card that uses either NDIS or ODI to be used with Chameleon.<BR><P>Prior to installation of Chameleon, the same steps are performed as for the DOS-based TCP/IP package. The network interface card must be installed with suitable IRQ and memory address settings. If Chameleon is being added to an existing Windows for Workgroups system, the network card should already be installed and properly configured. The same information is required as for all TCP/IP installations: the host name, IP address, broadcast mask, subnetwork mask, and any information about gateways or routers that needs to be included.<BR><P>The version of ChameleonNFS used for the sample network had its installation information slightly jumbled because of updates to both Chameleon and Windows for Workgroups. The information supplied today applies to Windows for Workgroups 3.1 and 3.11 and ChameleonNFS version 4.0, although other versions should be similar.<BR><BR><A ID=E69E135 NAME=E69E135></A><H4 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>Installing Chameleon</B></FONT></CENTER></H4><BR><P>Chameleon can be installed over a fully functioning Windows or Windows for Workgroups system. If Windows for Workgroups is used, ensure that the network performs properly (if possible) when talking to other NetBEUI-compatible machines. In this case, that's not possible because the sample network uses only TCP/IP.<BR><P>The installation procedure for Chameleon is simple. From the Program Manager's File menu, select Run, then execute the SETUP.EXE program from the first Chameleon disk. As with most Windows applications, this starts the installation program.<BR><P>The changes made to the system files might cause problems, affecting Windows' capability to boot. Before installing the Chameleon software, make copies of the AUTOEXEC.BAT, CONFIG.SYS, PROTOCOL.INI, WIN.INI, and SYSTEM.INI files. If problems are encountered, these files can return the system to its original state. You should consider making a full system backup before any major changes to software, of course.<P>The Chameleon installation program requires a lengthy serial number and an activation key to ensure that there is only one such version on a network (this locks out multiple installations using the same serial number and activation key.) The installation script prompts for the distribution disks in order and copies all the necessary files.<BR><P>Following the installation process, Chameleon builds the program group with the Chameleon applications included. The ChameleonNFS program group is shown in Figure 10.3. After creating the program group, Chameleon starts a customization screen that lets you specify your IP address, host name, network mask, and broadcast address. Save this information and then exit out of Windows to the DOS prompt to complete the check of the installation.<BR><P><B><A HREF=10tyt03.gif>Figure 10.3. The Chameleon program group.</A></B><BR><P>Because of the different installation variables encountered with different network drivers, it is advisable to check the following configuration files manually:<BR><UL><UL><P>AUTOEXEC.BAT</UL></UL><UL><UL><P>CONFIG.SYS</UL></UL><UL><UL><P>PROTOCOL.INI</UL></UL><BLOCKQUOTE><BLOCKQUOTE><P>SYSTEM.INI<BR></BLOCKQUOTE></BLOCKQUOTE><P>The following sections discuss each of these files in more detail. If the files do not have the information specified in them, add them with a text editor. Failure to check the files properly can result in Windows being unable to boot properly. If this happens, copy the backup files in place of the newly modified files, restart Windows, and reinstall or reconfigure as necessary.<BR><BR><A ID=E70E39 NAME=E70E39></A><H5 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>The AUTOEXEC.BAT File</B></FONT></CENTER></H5><BR><P>The changes to the AUTOEXEC.BAT file necessary to enable Chameleon to run are the inclusion of the installation directory in the PATH environment variable and a network startup command. If Chameleon is installed on a Windows for Workgroups system, the network startup command should already exist.<BR><P>The PATH environment variable must be modified to include the Chameleon installation directory, which by default is C:\NETMANAG. An existing PATH statement can be altered, or a new line can be added below the existing PATH statement that looks like this:<BR><BR><PRE>

<FONT COLOR=#000080>PATH=C:\NETMANAG;%PATH%</FONT></PRE><P>Of course, the correct drive and subdirectory should be substituted. This chapter assumes default values throughout.<BR><P>The command<BR><BR><PRE>

<FONT COLOR=#000080>C:\WINDOWS\NET START</FONT></PRE><P>is already in the AUTOEXEC.BAT file if a Windows for Workgroups system is used (either version 3.1 or 3.11). If Chameleon is installed on a Windows (not Windows for Workgroups) system, the NETBIND command included with the distribution software should be called as well:<BR><BR><PRE>

<FONT COLOR=#000080>C:\NETMANAG\NETBIND</FONT></PRE><P>Chameleon might install a SHARE command in the AUTOEXEC.BAT file if one does not exist. If one doesn't exist, it is advisable to add it if others can access the machine. SHARE is a DOS utility that activates file-sharing and record-locking. If other machines will be accessing the machine, SHARE is necessary to prevent error messages and potential system freezes when file conflicts occur.<BR><P>The completed AUTOEXEC.BAT file looks like this for a Windows for Workgroups 3.1 or 3.11 installation:<BR><PRE>

<FONT COLOR=#000080>PATH=C:\NETMANAG;%PATH%

C:\WINDOWS\NET START

SHARE</FONT></PRE><P>and like this for a Windows installation:<BR><PRE>

<FONT COLOR=#000080>PATH=C:\NETMANAG;%PATH%

C:\NETMANAG\NETBIND

SHARE</FONT></PRE><P>If the NET START or NETBIND command is not executed properly, Windows displays an error message when it loads. In some cases, Windows can lock up while it tries to access the network drivers.<BR><BR><A ID=E70E40 NAME=E70E40></A><H5 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>The CONFIG.SYS File</B></FONT></CENTER></H5><BR><P>The CONFIG.SYS file might be considerably different for each installation. The HIMEM memory device driver is required, and the SMARTDRIVE caching system is recommended. All installations should have adequate values for the FILES and BUFFERS settings, which are normally set by Windows when it is installed. The CONFIG.SYS should have these values as a minimum:<BR><PRE>

<FONT COLOR=#000080>BUFFERS=30

FILES=30

LASTDRIVE=Z

STACKS=9,256</FONT></PRE><P>This creates enough file and buffer settings to enable multiple files to be open at once. Higher values are better, although there is a trade-off of efficiency once the values exceed a certain value (depending on the amount of RAM in a system). The LASTDRIVE setting enables more drives to be open than are physically connected to the system. This is necessary when remote drives are mounted, either through Windows for Workgroups or Chameleon.<BR><P>For a Windows or Windows for Workgroups 3.1 system, Chameleon adds the following commands to the CONFIG.SYS file:<BR><PRE>

<FONT COLOR=#000080>DEVICE=C:\NETMANAG\PROTMAN.DOS /I:C:\NETMANAG

DEVICE=C:\NETMANAG\EXP16.DOS

DEVICE=C:\NETMANAG\NETMANAG.DOS</FONT></PRE><P>These load the device drivers for the protocol manager, the network interface card, and the specific protocol for Chameleon. The protocol manager and network interface card device drivers were discussed in the DOS section earlier today.<BR><P>Windows for Workgroups 3.11 usually has a command in the CONFIG.SYS file that looks like this:<BR><BR><PRE>

<FONT COLOR=#000080>DEVICE=C:\WINDOWS\IFSHLP.SYS</FONT></PRE><P>This automatically loads all the necessary drivers. In some cases, Chameleon adds the command for the Windows for Workgroups 3.1 device drivers to the end of the CONFIG.SYS file, even if the IFSHLP.SYS driver exists. Comment out the added device drivers and try the system without them. The IFSHLP.SYS device driver should be sufficient.<BR><BR><A ID=E70E41 NAME=E70E41></A><H5 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>The SYSTEM.INI File</B></FONT></CENTER></H5><BR><P>The Windows SYSTEM.INI file requires a few changes to ensure that Chameleon is loaded properly. These should be effected by the installation script, but check the lines carefully anyway.<BR><P>The [boot] section of the SYSTEM.INI file should have the following two lines:<BR><PRE>

<FONT COLOR=#000080>[boot]

shell=progman.exe

network.drv=C:\NETMANAG\MULT400.DRV</FONT></PRE><P>The shell line might be different if the system uses a replacement program manager (such as Central Point PC Tools for Windows Desktop Manager). The MULT400 driver supports several networks at a time. The order of these lines in the SYSTEM.INI file is not important, as long as they appear in the proper section. The MULT400 driver takes care of loading all the necessary drivers for each network. Windows for Workgroups should have this line<BR><BR><PRE>

<FONT COLOR=#000080>network.drv=wfwnet.drv</FONT></PRE><P>either commented out with a semicolon at the start of the line or removed entirely. The WFWNET driver is the Windows for Workgroups network driver, which must be replaced by MULT400.<BR><P>The [boot.description] section of the SYSTEM.INI file is changed to<BR><PRE>

<FONT COLOR=#000080>[boot.description]

network.drv=NetManage ChameleonNFS</FONT></PRE><P>or a similar line if another NetManage product is installed.<BR><P>The [386Enh] section has several changes made. These are as follows:<BR><PRE>

<FONT COLOR=#000080>[386Enh]

device=C:\netmanag\nmredir.386

network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386

netmisc=ndis.386,ndis2sup.386

netcard=

transport=nwlink.386,nwnblink.386,netbeui.386

InDOSPolling=FALSE</FONT></PRE><P>The order of the lines in the section doesn't matter. They load the correct network device drivers into the Windows kernel.<BR><P>Finally, the [network drivers] section should have these lines:<BR><PRE>

<FONT COLOR=#000080>[network drivers]

netcard=elnk3.dos

devdir=C:\WINDOWS

LoadRMDrivers=YES

transport=ndishlp.sys,c:\netmanag\netmanag.dos,*netbeui</FONT></PRE><P>The netcard line changes depending on the network interface card used. The LoadRMDrivers line should be changed from the Windows for Workgroups default value of NO to YES.<BR><BR><A ID=E70E42 NAME=E70E42></A><H5 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>The PROTOCOL.INI File</B></FONT></CENTER></H5><BR><P>The PROTOCOL.INI file for a Windows for Workgroups installation doesn't require many changes. The driver information should already exist. A new section added by Chameleon should look like this:<BR><PRE>

<FONT COLOR=#000080>[NETMANAGE]

DRIVERNAME=netmng$

BINDINGS=MS$ELNK3</FONT></PRE><P>The BINDINGS line changes depending on the network interface card. It is easiest to copy the line from another section of the PROTOCOL.INI file.<BR><BR><A ID=E69E136 NAME=E69E136></A><H4 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>Configuring Chameleon</B></FONT></CENTER></H4><BR><P>Once Chameleon has been installed and the startup files checked for proper content, you can configure the software for the sample machine. This is done through the Chameleon CUSTOM application. When started, CUSTOM displays a status screen as shown in Figure 10.4.<BR><P><B><A HREF=10tyt04.gif>Figure 10.4. The Chameleon Custom screen.</A></B><BR><P>If the installation routine didn't add the machine's name and IP address to the Custom screen, use the Setup menu item to select the different aspects of the configuration that must be specified. You should provide a machine name, IP address, subnet mask, and domain name, as well as the interface if not already added (Ethernet, in this case).<BR><P>To enter the names of the other machines on the network and their IP addresses, select the Services menu Host Table option to display the Host Table dialog box. To add the other machines on the sample network, enter a name in the top portion of the window in the field titled Official Name and click the Add button. This shows a window for the IP address, which should be filled in completely. Then click OK. The IP address and the machine name are now entered into the host table. This window is shown in Figure 10.5 with the address for the machine merlin added. If a machine has more than one name, the different names can be added as aliases through this screen, as well.<BR><P><B><A HREF=10tyt05.gif>Figure 10.5. Chameleon's Host Table IP Address </B><B>dialog box.</A></B><BR><BR><A ID=E69E137 NAME=E69E137></A><H4 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>Testing Chameleon</B></FONT></CENTER></H4><BR><P>After the changes to the four configuration files are completed, reboot the system and start Windows. Watch for error messages as the Chameleon lines in the CONFIG.SYS and AUTOEXEC.BAT files are executed. If Windows for Workgroups was installed and working prior to installing Chameleon, there should not be any errors.<BR><P>The easiest way to test the new TCP/IP system is to use the ping utility within the Chameleon program group. When selected, it displays a small dialog box. Select the Start option, which displays another dialog box waiting for a machine name. Enter the name of the local machine. This is shown in Figure 10.6 for the sample network Windows machine pepper.<BR><P><B><A HREF=10tyt06.gif>Figure 10.6. Using </B><B>ping</B><B> to test the local </B><B>host.</A></B><BR><P>The ping window should show a successful result. This is indicated by a message showing the number of bytes received, as well as time information. A sample output from a successful attempt to ping the local machine is shown in Figure 10.7.<BR><P><B><A HREF=10tyt07.gif>Figure 10.7. </B><B>ping</B><B> diagnostic messages.</A></B><BR><P>If the ping attempt is not successful, Chameleon displays a message about the network drivers not installed or about unreachable hosts. Upon receipt of such a message, check the network card settings and all the configuration information through the CUSTOM program.<BR><P>The next step is to use ping to send to another machine on the network. Figure 10.8 shows the output from a ping attempt on freya, the sample network's Linux server and to whitney, the Windows 95 machine that is not booted (and hence should fail). The system timed out on the whitney attempt, as you would expect.<BR><P><B><A HREF=10tyt08.gif>Figure 10.8. </B><B>ping</B><B> across a network.</A></B><BR><P>If the ping attempts across the network fail on all machines, the problem is likely with the configuration. Check all the configuration information (as previously noted), as well as the network cables and cards. Make sure the machines to be pinged are up and running TCP/IP.<BR><P>If the network is operating properly, try the ftp and telnet applications from the Chameleon program group. Full instructions for these utilities are in the documentation. As long as a host table entry has been created and ping succeeded, the other utilities should function properly. Both provide a graphical interface that Windows users will find familiar, instead of the character-based line interface found with DOS. To configure more elaborate functions within Chameleon (such as SNMP, mail, and Gateway routing), consult the Chameleon documentation.<BR><BR><A ID=E68E99 NAME=E68E99></A><H3 ALIGN=CENTER><CENTER><FONT SIZE=5 COLOR=#FF0000><B>Configuring Windows 95 for TCP/IP</B></FONT></CENTER></H3><BR><P>The final client on the sample network that requires configuration is the machine called whitney, with IP address 147.120.0.10. Windows 95 is the easiest of the three clients to configure because everything you need to set up TCP/IP under Windows 95 is included with the software distribution. Windows 95 is configured by default to use NetWare IPX/SPX as the network protocol, but switching to TCP/IP is quite easy.<BR><P>Begin the Windows 95 configuration process by installing the network adapter card. In some cases, when you restart Windows 95 the operating system automatically recognizes the addition of the network card and proceeds to the configuration routines for you. In many cases, though, you have to instruct Windows 95 to look for the network adapter card.<BR><P>To install a network adapter card, open the Windows 95 Control Panel and double-click the Add New Hardware icon. This calls the Add New Hardware Wizard. After you click the Next button on the introductory dialog, Windows 95 gives you the option of having the operating system try to detect the new hardware automatically.<BR><P>It is usually best to let Windows 95 try to find the network adapter by itself, especially if the new card is a plug-and-play type. If Windows 95 can identify the hardware automatically, it saves you having to provide configuration information. If you want Windows 95 to go ahead and look for the network adapter, select the Yes button on this dialog (the default value) and click the Next button. Windows 95 begins searching the system for new hardware. If Windows 95 detects a new network card, it displays a screen showing the parameters it detected and lets you confirm the selection. After a reboot, the network card should be properly recognized and active.<BR><P>If Windows 95 didn't detect the network adapter, you have to install and configure it manually. Windows 95 shows a dialog like the one in Figure 10.9. Clicking the Next button displays the dialog shown in Figure 10.10, which asks for the type of new hardware device you are installing. In this case, you double-click the Network adapters option.<BR><P><B><A HREF=10tyt09.gif>Figure 10.9. This dialog is displayed if Windows 95 </B><B>couldn't detect a new network adapter card.</A></B><BR><P><B><A HREF=10tyt10.gif>Figure 10.10. This dialog asks for the type of </B><B>hardware you are installing.</A></B><BR><P>The next dialog to appear shows a list of network adapter card manufacturers on the left side, and a more detailed list of network card models from the selected manufacturer on the right. Select the proper manufacturer of the network adapter card in the list at left by single-clicking the manufacturer's name, then select the name in the right-side list that matches the specific card.<BR><P>You must be careful that you match the name of the adapter card exactly with the list, because some drivers do not work on other cards from the same manufacturer. If you select the wrong adapter card, you won't cause any damage to either the card or Windows 95, but the network will not be found properly by Windows 95. If you can't find the particular model name of the network adapter card you are using, but you have a driver supplied on disk, use the Have Disk button to read the driver into Windows 95.<P>Once you have selected the proper network card name, Windows 95 displays a window with configuration information shown in it. This dialog is shown in Figure 10.11. The amount of configuration information shown in this dialog, and the settings it shows, are different for each network adapter card.<BR><P><B><A HREF=10tyt11.gif>Figure 10.11. Windows 95 uses this dialog to ask </B><B>for the configuration settings of the network card.</A></B><BR><P>If the network adapter was found by autodetection, the settings shown in this dialog are the ones Windows 95 assumed are correct for the card. If Windows 95 couldn't find the network card, the settings shown are the default values usually used by the manufacturer. Check the documentation supplied with the network adapter card to confirm the settings. After you confirm that the displayed values are correct, Windows 95 installs the software necessary to drive the network adapter card.<BR><BR><A ID=E69E138 NAME=E69E138></A><H4 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>Installing TCP/IP</B></FONT></CENTER></H4><BR><P>You can install the TCP/IP drivers included with Windows 95 by displaying the Network dialog. Click the Network icon in the Control Panel to display the Network dialog shown in Figure 10.12. The dialog should show a few basic entries created when Windows 95 installed itself, as well as the network hardware card. By default, the NetBEUI or NetWare (IPX) protocols might already be loaded.<BR><P><B><A HREF=10tyt12.gif>Figure 10.12. The Network window shows all </B><B>configured hardware and protocols.</A></B><BR><P>To add the TCP/IP protocol drivers to Windows 95, select the Add button below the list of installed components to display the Select Network Component Type dialog shown in Figure 10.13. This window asks for the type of component (adapter card, protocol, service, or client) you want to install. Because you want to install the TCP/IP protocol drivers, choose Protocol. The Select Network Protocol dialog, shown in Figure 10.14, is displayed.<BR><P><B><A HREF=10tyt13.gif>Figure 10.13. The Select Network Component Type </B><B>dialog lets you add a protocol, client, service, or adapter card.</A></B><BR><P><B><A HREF=10tyt14.gif>Figure 10.14. The Select Network Protocol dialog </B><B>lets you choose the type of protocol to add.</A></B><BR><P>From the Select Network Protocol window, select Microsoft in the left scroll list, then move to the right window, which lists all the Microsoft protocols supplied with Windows 95. Choose the TCP/IP entry. You are returned to the Network dialog, and TCP/IP is listed as a supported protocol.<BR><P>To start the configuration process, either double-click the TCP/IP protocol entry in the Network dialog list, or select the TCP/IP protocol entry and click the Properties window. The TCP/IP Properties dialog appears, as shown in Figure 10.15.<BR><P><B><A HREF=10tyt15.gif>Figure 10.15. The TCP/IP Properties dialog has six </B><B>pages of configuration information.</A></B><BR><P>From the TCP/IP Properties dialog, six pages of information are available by choosing one of the tabs across the top of the dialog. For most installations you have to supply only a small part of this information. You can start with the IP Address page, which is the first page shown whenever the TCP/IP Properties window is displayed. Enter the IP address and subnet mask in the spaces provided, making sure to keep the four parts of the dotted-quad notation separate.<BR><BLOCKQUOTE><BLOCKQUOTE><HR ALIGN=CENTER><BR><NOTE><IMG SRC=note.gif WIDTH = 75 HEIGHT = 46>Some larger corporate networks are set up to assign IP addresses to connecting clients automatically using a special protocol. This protocol, called Dynamic Host Configuration Protocol (DHCP) servers, is usually used for machines that connect to a TCP/IP network only occasionally. If your network uses DHCP, you can select the first button on the IP Address page and let Windows 95 obtain your IP address and subnet mask for you. Most networks do not use DHCP.</NOTE><BR><HR ALIGN=CENTER></BLOCKQUOTE></BLOCKQUOTE><P>Next, you move to the Advanced page of the TCP/IP Properties dialog by selecting the Advanced tab at the top of the dialog. This dialog lets you specify that TCP/IP is the default protocol used by the Windows 95 machine by clicking the option at the bottom of the page, as shown in Figure 10.16. If your Windows 95 system is attached to a TCP/IP network and uses TCP/IP most of the time, make sure you select this option; otherwise, Window 95 tries to use NetBIOS or IPX/SPX on the TCP/IP network.<BR><P><B><A HREF=10tyt16.gif>Figure 10.16. Select the default option from the </B><B>Advanced page of the TCP/IP Properties dialog.</A></B><BR><P>For many simple TCP/IP networks, that's all the information you need to supply. Windows 95 now loads the proper drivers into the operating system, using the values supplied for the IP address and subnet mask. After the software has been properly loaded, Windows 95 must be restarted to make the TCP/IP drivers effective.<BR><BR><A ID=E69E139 NAME=E69E139></A><H4 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>Further TCP/IP Configuration</B></FONT></CENTER></H4><BR><P>Some TCP/IP systems require extra configuration to provide Windows 95 with the name of the servers, gateways, or other details. You can make many of these configuration steps at any time, but some services might not be available to you until you do. All of these changes are made through the TCP/IP Properties dialog used to set the IP address and subnet mask.<BR><P>The WINS Configuration page of the TCP/IP Properties window is used to instruct your Windows 95 system how to talk to a Windows Internet Naming Service (WINS) server. WINS lets you use the NetBIOS protocol on a TCP/IP network. Most networks don't use WINS, so you can probably ignore this page completely unless you know you will need to use WINS on your network. If WINS is required on your network, enter the IP address of the primary (and secondary, if used) WINS servers, as well as the Scope ID. If WINS is not used on your network, make sure the Disable WINS Resolution option is selected.<BR><P>The Gateway page lets you specify where your network's gateways are. Gateways are used to connect to other networks, including the Internet. If your netwo