Verify and Test the Network Connection

To detect and avoid network problems, do the following:

1. First, make sure you actually have TCP/IP running correctly on your workstation.
   
   At the DOS prompt type PING nnn.nnn.nnn.nnn to the server host to which you are trying to connect (where nnn.nnn.nnn.nnn equals the IP address of the server). For example:

   C:\>PING 127.0.0.1

   Alternatively, you can PING the same server name you are trying to connect to or resolve (e.g., BROKERSERVER). For example:

   C:\>PING BROKERSERVER

   "PINGing" is a way to test connectivity. PINGing sends an Internet Control Message Protocol (ICMP) packet to the server in question and requests a response. It verifies that the server is running and the network is properly configured.

   If the host is unreachable, there is a network problem and you should consult with your network administrator.

   If you get a time-out, it may be your network configuration on the client workstation, proceed to Step 2.

   If the server is reachable, proceed to Step 4.

2. Check the properties of the WINSOCK.DLL on the client workstation and make sure it's the correct version. Install the latest Service Pack.
   
   
3. Make sure that the files on the client are in the correct directories. In Windows 95, the WINSOCK.DLL expects the HOSTS file to be located in the WINDOWS root directory. You should only have one copy each of the WINSOCK.DLL and the HOSTS file on the client. (However, there may be a second copy that WIN95 keeps in the WINDOWS/SYSBCKUP directory). If Windows 95 detects that some of its core files have been overwritten with older versions, supposedly it will automatically update files on reboot.
   
   
4. Make sure that all of the client workstation TCP/IP settings are correct in the network properties. Typo's, etc. can be a real problem, as can gateways, DNS servers, etc. Try removing items in your WINS configuration/DNS configuration, etc.