1. Before you can install the TCP/IP protocol to Windows for Workgroups 3.11 you first need to download the TCP/IP files and unzip them to a new folder.
   
   
2. Remarkably, you can still download the TCP/IP protocol files from the Microsoft FTP server at ftp.microsoft.com/softlib/mslfiles/tcp32b.exe (Self-extracting EXE, 673 KB).
   
   If you have any problems, or Microsoft remove it from their server, you can also download the files from here, these are zipped: tcp32b.zip (ZIP, 661 KB).
   
   
3. Once you have downloaded TCP32B.EXE, copy it to a new folder, e.g. C:\TCPIP and double-click it. It will now automatically unzip into the folder. (If you have downloaded the zip file you will need a 16-bit version of WinZip (Self-extracting EXE, 615 KB) to unzip the file.)
   
   
4. In Program Manager, if it is not already open, double-click the Network group to view its icons.
   
   
5. Now select and then double-click the Network Setup icon (below).

6. A new window, called Network Setup, will open showing the following information:

7. Click the Drivers... button (above) to show a list of the currently installed Network Drivers (below):

8. Now click the Add Protocol... button, on the right-hand side of the window (above).
   
   
9. You will be prompted for the location of the TCP/IP drivers. This will be where you unzipped TCPIP32B.EXE to.

10. Click on the Browse... button (above) and locate the folder you unzipped the drivers to. In this example I unzipped them to C:\TCPIP.

11. Select the folder in the Directories dialog, and then click OK (above).
    
    
12. You will now be returned to the Install Driver dialog, but the text box now contains the location of the TCP/IP drivers. Click the OK button.

13. A new window will appear called Unlisted or Updated Protocol listing the protocol: Microsoft TCP/IP-32 3.11b. By default it should be selected. Click OK.

14. The TCP/IP drivers will now install. When they have installed you will be presented back at the Network Drivers window.
    
15. You will now see that Microsoft TCP/IP-32 3.11b is now added to the list of installed drivers (below).

16. Select the newly installed Microsoft TCP/IP-32 3.11b and click the Setup... button to see the Microsoft TCP/IP Configuration dialog (below).

17. In this dialog you can enter your IP address, Subnet Mask and Default Gateway information (see below). Let me explain a little.

• Enable Automatic DHCP Configuration (Green)
  If you are connecting this PC to a router/switch which has a built-in DHCP (Dynamic Host Configuration Protocol) server then feel free to tick the "Enable Automatic DHCP Configuration" option. Your DHCP server will automatically assign your PC with an IP address and Subnet Mask. You will still need to complete the Default Gateway section (Blue) before you click OK.
  
  
• IP Address and Default Gateway (Red)
  If you are manually assigning an IP address and Subnet Mask you can enter this information here. Each PC must have a unique IP address. For a local area network of two computers I might assign one PC as 192.168.0.1 and the other as 192.168.0.2; you may assign different values here for security reasons (this is the default setting and is easily guessable by anyone trying to hack your PC from the internet). The subnet mask MUST be the same on all PCs on the same network.
  
  
• Default Gateway (Blue)
  If you are only setting up a two computer, peer-to-peer network without a router then you do not need to worry about this setting. If you do have a router/switch attached to your PC, allowing both PCs to access the internet (or another WAN) then enter the IP address of your router here. In this example I have assigned the IP Address 192.168.0.5 to the PC, where the IP address of the router (Default Gateway) is 192.168.0.1.
  
  
• Primary WINS Server and Secondary WINS Server
  WINS stands for Windows Internet Name Service. This is a Windows NT service that dynamically associates the NetBIOS name of a host with a domain name. You do not need to worry about this in this setup.

If you are connecting to a router/switch

18. If you are connecting this PC to a Router/Switch to connect to the internet then you may need to set where the Domain Name Service is located. Click the DNS... button (below).
    
    If you are NOT connecting to a Router/Switch then go to step 24 below.

19. Enter the IP address of your Router/Switch in the Domain Name Service (DNS) Search Order box (red) and click the Add -> button (green). The IP address will be added to the box on the right. Now click OK (blue).

20. Click OK (blue) and this will return you to the Microsoft TCP/IP Configuration window (below).
21. Now click the Advanced... button.

22. There shouldn't really be much you have to worry about in this section (I think!). I have both the Windows Networking Paramaters selected: Enable DNS for Windows Name Resolution and Enable LMHOSTS Lookup.

23. Click OK. This will return you to the Microsoft TCP/IP Configuration window.

Exiting and rebooting

24. Click OK to return you to the Network Setup window (below).

25. Now click OK to exit the Network Setup window and confirm all the changes you have made.
26. A dialog box will pop up to inform you that your SYSTEM.INI file has been updated and where the old version has been saved to (below).

27. Click OK and you will be asked to reboot the machine.

Test your TCP/IP connection

28. One very good way of testing whether your TCP/IP protocol is installed properly and working is to use the PING command.
    
    Once you have rebooted, start an MS-DOS-Prompt window, and at the prompt type
    
    ping 192.168.0.1
    
    then press Enter.
    
    (Obviously substitute the 192.168.0.1 for the IP address of a PC or router on your network, if necessary.)

29. If your TCP/IP connection is up and running well, you should see something similar to the output above. If you are experiencing problems you will see something similar to the screenshot below.

{^top}

Next step

Setting up a proxy server

With your TCP/IP network up and running, if you don't have your PC connected to a Router/Switch, you can now use a Proxy Server to connect your Windows for Workgroups 3.11 machine to the internet via a PC with a dial-up connection.

Proceed to step 5 Setting up a Proxy Server.

{^top}