TCP/IP

TCP/IP stands for Transport Control Protocol/Internet Protocol a protocol necessary for internet applications to work across our network here at JMU. TCP/IP is one of two protocols we use here at the University. Without TCP/IP installed and functioning properly customers will be unable to use internet applications such as Netscape, Simeon, QVTNet, WS-FTP, and WinVN.

TCP/IP has NO BEARING on accessing the Fileservers on campus. Fileservers and printers on campus use the IPX/SPX Protocol.

What To Do:

When a customer calls and cannot run certain INTERNET applications such as those mentioned above you should begin by verifying that they have a good IP address in the bootp table. For Windows 95 users use the WINIPCFG command. (For Windows 3.x users use the TCPMAN command.)

Win 95:

If their IP address is valid you need to check that they have the TCP/IP protocol as part of their network control panel configuration. Click onStart | Settings | Control Panels | Network.

In the dialog box look at the window "The Following Network Components Are Installed:" in this area you will see TCP/IP listed with the Client, Adapter and other protocols.

If TCP/IP is absent from this list you need to add it. Click on the Add button and then choose Protocol from the list. Choose Microsoft as the Manufacturer and choose TCP/IP from the list.

If the computer is networked: it will copy the necessary files from the network (actually from f:\apps\win95ins) (if this copy bombs it may indicate that the user is not a member of the win95ins group on the file server. If this is the case consider the computer "not networked" and see the next section).

If the computer is NOT currently networked: it will request a windows 95 install disk to copy the files from. If the user does not have a Windows 95 install disk you should log the call to the Dispatcher.

Windows 3.x:

uses TCPMAN for TCP/IP protocol. Check out the link for TCPMAN for more information on how it is used and how to troubleshoot it.

Back to Utils


E-mail comments to Lon Jarvis jarvislb@jmu.edu
last updated 3/17/00