Knowledgebase: General Networking
TCP/IP for WinGate running Windows2000, XP,2003
Posted by Adrien de Croy (Import) on 30 January 2004 02:36 PM
How to setup the correct TCP/IP configuration for WinGate running on a Windows 2000, XP, or 2003 Computer:
  1. Select the ”My Network Places” icon on the desktop and right click to open the context menu and select properties. An alternative to this, is to enter the control panel (via the start menu) and select the Network and Dial-up Connections.
  2. Once the Properties window appears, you will see listed the available network connections (usually marked Local Area Connection ). If there is more then one Network connection listed, select the Interface that will connect the WinGate Server to the rest of your Local Network (not the Internet).
  3. Right click on this Interface and from the menu select Properties.
  4. A dialogue listing the Network adapter (NIC), its Protocols and Services will appear. Scroll down to the entry that says Internet protocol (TCP/IP) and click on the properties button at the bottom.
  5. Under the general tab, select Specify an IP address in the IP address field. Enter a suitable IP address of a private class (in accordance with RFC , (such as 10.0.0.1, 192.168.x.x). This should be in the same range as what the rest of the network will be numbered with.
  6. The subnet mask will be automatically set by Windows after you have entered the IP address, or you can specify a specific mask depending on your requirements.
  7. The next thing to ensure is that the Gateway entry is left empty. This is most important when setting the internal IP interface, as the external interface that is used to connect out to the Internet is the only NIC on the machine that should require a Gateway setting, and this will usually be assigned by the ISP.
  8. Leave the DNS option at the bottom blank as explained above there is no requirement for the Internal interface to have a DNS setting.

    Note if there is a requirement for the DNS to be enabled, the only DNS servers that should be there are that of the ISP, or specified DNS server with an external IP address).

  9. There is no need to adjust anything under the Advanced tab. When WinGate server is is set to run on the machine, you should avoid listing or entering a Wins server as WINS lookups can be configured via the lmhost file in WinGate itself.
To set the correct TCP/IP settings for the WinGate client computer, you will need to first determine the following: How are clients to receive their TCP/IP details, either entered statically or issued via WinGate’s DHCP service.

If clients are to receive their IP details by WinGate’s DHCP service, then the only required configuration they need, is to ensure that in the Internet Protocol (TCP/IP) properties of the clients Network Interface (accessed in the same way as described above) has all options set to Obtain IP Address automatically.

The DHCP scope in the DHCP service in Gatekeeper on the WinGate machine should be set to fully automatic, and this will give the client machines their DNS and Gateway settings when they are assigned an IP address.

If the clients are to be given statically assigned IP addresses then the following settings are required:
  1. Access the Network Interface properties as described in the server scenario above.
  2. Under the general tab of the Internet Protocol (TCP/IP) properties, enter an Internal IP address that is in the same range as the WinGate server (e.g. 192.168.4.*)
  3. After entering the IP the subnet mask field should be filled in automatically or set as specifically as required, and should be the same as the mask used on the Internal Interface of the server. (this ensures they share the same subnet range).
  4. In the Default Gateway field, you should enter the Internal IP address of the WinGate Server
  5. In the DNS field choose the Use this DNS server radio button and again enter the internal IP of the WinGate Server.
As with the WinGate server setup the Advanced tab does not require any configuration and can be left at the system defaults.

This has now completed the correct TCP/IP configuration for your WinGate server and client computers. You will now need to determine what type of access your clients will use to connect thru WinGate to the Internet. (NAT,WGIC,proxy)

Descriptions and example of these connection methods can be found in the WinGate help file.
(1160 vote(s))
Helpful
Not helpful

Comments (0)