To use NAT you need:
a) The Extended Networking Driver loaded in WinGate; a default install will usually have it.
b) The LAN Client with Yahoo Messenger needs a default gateway set to WinGate's Internal IP Address.
So if the WinGate Server has the following IP Address on its network card pointing towards the LAN
IP Address 192.168.0.1
Subnet Mask 255.255.255.0
Then the LAN Client will have the following settings to facilitate NAT
IP Address 192.168.0.2 (for example)
Subnet Mask 255.255.255.0
DNS 192.168.0.1 (for example)
Default Gateway 192.168.0.1
The easiest way to test for the NAT connection method on the LAN Client is to ping an external server, such as the WinGate website:
(Windows) Start menu --> Run --> CMD ---> ping
http://www.wingate.comSo once you know that you have the NAT Connection method available on the LAN Client you can setup Yahoo Messenger to use it; i.e. don't set any proxies in the Yahoo Messenger application.
Now since you have the WinGate Internet Client (WGIC) installed, there are two options to get Yahoo Messenger working with NAT.
a) Disable the WGIC or Uninstall it.
b) On the LAN Client, setup the WGIC to treat the YahooMessenger.exe (that application name is a guess) to use "Local Access", then the WGIC will ignore any requests from that application and allow NAT to be used.
Personally, there are only a few reasons why I would deploy the WGIC onto LAN Clients.
1. I want to control what applications can access the internet.
2. I want the Users to be able to hang up a Dial Up connection
3. There is a Terminal Server on the internal network. Because if the Terminal Server users are using NAT, there is no way to distinguish which user is creating the connection, so hence the WGIC is a good choice in that scenario since it will associate the connections to the terminal users.