




If (even after following the instructions at the Windows95.com TCP/IP Setup Page religiously) you are still having problems, try some of the steps on this page. If you're looking for a definition of a word or acronym, try the Windows95.com Hyper-Glossary of Internet Terms. Another great resource for Windows 95 networking troubleshooting information is the Windows 95 Networking FAQ maintained by Rich Graves. If your problem isn't solved by following the steps on this page, check Rich's FAQ.
Before changing any settings, verify that the connection works:
- Go to the DOS prompt
- Type ping 198.105.232.1 (that's Microsoft's FTP server) or try 128.95.1.4 (their DNS server)
If you get a response, then the TCP/IP protocol is working over your connection.
- Type ping FTP.MICROSOFT.COM
If you get a response, then your DNS settings are correct and working. Try firing up those 32-bit Winsock apps!

If your connection isn't working properly, try the following:
- If you have a PPP account, make sure the server type in the connection properties is set to PPP, not SLIP or CSLIP. You can also try disabling software compression in the Server Type... dialog box.
- If you have a SLIP account, make sure you have changed the server type to SLIP or CSLIP (PPP is the default). Make sure you typed in the correct IP address when prompted during the login process.
- For SLIP users: If you can use PING, but you can't use Winsock applications after you're connected, you probably need to switch the server type. Try changing the server type in the connection properties from SLIP to CSLIP or CSLIP to SLIP, depending on the current setting.

If one of your Winsock apps isn't working properly, try the following:
- First, check to see if the application requires a specific WINSOCK.DLL file. Some Winsock apps out there copy their own WINSOCK.DLL file into their directory, which may be the cause of your troubles. Rename the application's WINSOCK.DLL so that Windows 95 only uses the Windows 95 winsock (it's called WSOCK32.DLL). If the application doesn't work with Microsoft's Windows 95 winsock, you may have to rename Windows 95's winsock, and copy the application's WINSOCK.DLL file into the Windows directory. this will probably cause other Winsock applications not to work, so I only recommend it as a last resort, and only if you really want to run that application. Try contacting the application's vendor and ask if they can send you an updated version that will work with Windows 95's WINSOCK.DLL.
- Make sure that a version of WINSOCK.DLL doesn't show up in the path. If Windows 95 encounters the Trumpet WINSOCK.DLL file, for example, intstead of its own, 32-bit apps have a tendency to crash.
- If you're getting an error like "Can't Find TCPMAN.EXE" then WIndows 95 is finding the Trumpet Winsock before it can find the Windows 95 winsock file. Rename the old WINSOCK.DLL file.

Other TCP/IP Issues:
For current release notes on using TCP/IP and Dial-Up Networking with Windows 95, double-click on the Windows 95 Release Notes icon on your desktop. If you deleted it (like I did!) you can use NOTEPAD to view the README.TXT file in the Windows directory.
- If you are using TCP/IP on a Wide Area Network, but it is bound to both the LAN and PPP adapter and no DHCP server is present on the LAN, you may notice a 2 to 3 second pause when the computer accesses the network. To get rid of the pause, unbind the TCP/IP protocol from your LAN adapter. To do this, go into the Network control panel, select Properties, then uncheck TCP/IP in the bindings property area.
- To change MTU and/or RWIN values for your connection, you'll have to edit the registry. In order to simplify this task, you can download these two registry update files (press SHIFT while you click to download to disk): MTU Change and RWIN Change. To set these parameters, simply download the files, then select one, press the right mouse button, then choose Edit. Change the number value of the registry setting to the desired value, then save and exit. Simply double-clicking the .REG will update the reigstry with the new setting. You'll have to reboot for the change to take effect.
©1995 Steve Jenkins
Microsoft, MS, Windows, Windows 95, and the Windows logo are either registered trademarks or trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with Windows95.com. All other trademarks are the sole property of their respective owners.