As a footnote to Genies comments.
1. Check you have NAT installed. If you do not, reinstall WinGate with the ENS (Extended Networking Service) option
2. Check that your network adapters were detected correctly by WinGate. The network card pointing towards the LAN should be marked as "Internal" and the network card / modem that is pointing towards the internet should be marked as "External". GateKeeper --> View menu --> Network.
3. On the client machine behinds the WinGater server, check that you have TCP/IPs configuration set for NAT. The DNS and Gateway is usually the internal IP address of the WinGate server. Please note, these are example addresses so you can see the pattern; you may have a different ip address sheme on your network.
So if the WinGate servers internal IP address is (you can check by (Windows) Start menu --> Run --> cmd --> ipconfig/all )
IP Address 192.168.0.1
Subnet 255.255.255.0
DNS
Gateway
Then an example clinet configuration to use NAT will be
IP Address 192.168.0.2
Subnet 255.255.255.0
DNS 192.168.0.1
Gateway 192.168.0.1
4. If you are using Windows XP SP2, please check that the Windows Firewall is off for the sake of testing.
On your desktop, right click My Computer
Manage
Services and Applications
Services
Double click: Windows Firewall/Internet Connection Sharing (ICS)
Set the Startup type to disabled.
Click the "Stop" button
5. If you have any other security suites installed, please advise. e.g. Nortons, McAfee, ZoneLarm etc..
To test, on a client machine, open up Internet Explorer and browse to a web page. If you do not get connectivity to the internet, please advise. As a temporary measue, you could set Internet Explorer to use the Proxy service of Wingate to get connectivity while troubleshooting NAT.
Please note, the IP address in this picture may not be correct. The IP address for the proxy server should be the same as the internal network card on the WinGate server.
