by adrien » Jul 16 09 3:14 pm
Hi
OK, if the clients are using WinGate as a default gateway, yet they don't get net access unless they are configured to use a proxy, that implies that NAT is not operational in WinGate. This can be due to several reasons:
1. NAT isn't enabled in the Extended Networking settings in GateKeeper
2. The adapter settings in GateKeeper (adapter usage) is wrong for NAT - 6.0.3 required the clients to be connecting through an adapter marked internal, and that the connection to the internet be on an adapter marked external. 6.0.3 didn't handle NAT with single network cards. Later versions of WinGate don't have this restriction.
If you're looking to remove WinGate however, then fixing NAT in WinGate isn't going to help, you'll instead need to set the default gateways on the client machines to point to your Cisco.
I presume this is what you're trying to do - remove WinGate? Or just no longer use proxying for connectivity?
if you still want to use WinGate, but not as a proxy (e.g. not require setting client config to use a proxy) then depending on your network config you may need to install a later version of WinGate. Your license will continue to work in the latest version still.
how many network adapters does the WinGate machine have? I'm guessing just one?