WGIC / Winsock Redirector Service Not Working

[corneg]

I've installed Wingate on a machine that's sharing an internet connection through a USB modem, and the clients are able to use their browsers if I specify the proxy server on port 80 in the browser on the client pc.

If I don't specify that, or I try to use Outlook or any other web application they don't work. On the server, on the activity tab I can see the request - WRP Control Session - firefox.exe etc. but they don't work. Here's the logfile:

01/21/08 08:52:22 Service started successfully
01/21/08 09:24:19 192.168.1.2 Guest 0000000019 Traffic 88 49 0 0 328s
01/21/08 09:24:20 Service stopped
01/21/08 09:24:25 Service started successfully
01/21/08 09:32:22 Service started successfully
01/21/08 09:57:31 192.168.1.9 Guest 0000000018 Traffic 48 52 0 0 40s
01/21/08 10:05:35 Service started successfully
01/21/08 10:21:32 192.168.1.9 Guest 0000000026 Traffic 48 52 0 0 44s

The internal network adapter is set as internal and the modem as external on the networks tab.

Any ideas?

[adrien]

Hi

We saw a problem like this in the past affecting IE6 - if you ran the network setup wizard, IE would bypass the winsock layered service providers, thereby patching out the WGIC.

But I never heard of this affecting firefox.

Also if you are getting a control connection (i.e you see the WRP control session in GateKeeper), that means that the WGIC has been loaded in the context of that client application. I can only think of 3 possible reasons you wouldn't see the subsequent connections.

1. The browser say is trying to connect to a local site on the local LAN, in which case the WRP server tells the client to connect directly.

2. Some firewall is blocking outbound connections from the client machine, or some other firewall on the WinGate machine is blocking the connection to the TCP redirect port. Note that even though you might be connecting to port 80 for HTTP externally, the connection between the client machine and WinGate won't be on that port.

3. You have more than 1 IP address on your internal adapter, the WWW proxy is only bound to one of those IP addresses, and it is configured to intercept connections.

Regards

Adrien