Connection Goes Away?

[rboynton]

Since upgrading to 6.6.1, I've had a couple of situations where our network users could not access the internet. I opened a browser on the Proxy server to ensure the internet was accessible (ensured the ISP was not down). I then went back to the client and retried the website and things worked. When this happened again, I repeated my steps to resolve the issue at hand. This did not occur with the older version (believe we were on 6.5.2). We made no other changes other than to upgrade.

[adrien]

Hi

What symptom do you see when the client can't access the Internet? 9/10 times this is related to DNS resolution.

Regards

Adrien

[rboynton]

The user opens a web browser and the page will not come up. Eventually times out with page cannot be displayed.

[logan]

Is the client configured to use the proxy manually, or is the client NATing through WinGate and port 80 is then being intercepted from NAT.

The reason I ask is because if the clients are configured to use the proxy manually, but you see a long delay and a page connot be found error, that probably means the client failed to connect to the WinGate proxy. If the client successfully connected to the WinGate proxy, I would expect your client to see a pretty blue error message from WinGate rather than the generic microsoft error message.

If the client is configured to use the NAT (no manual proxy), then what you are seeing means that the client timed out while trying to resolve the domain name into an IP and so did not attempt to connect to the web server in the first place. This means WinGate would not have a connection to intercept, and so would not be able to serve the webpage, or throw it's pretty blue error message again.

I'm wondering if the connection between your client and WinGate is being lost? Is the WinGate server going to sleep maybe? Or is there a loose connection somewhere.

The next time this happens, try pinging the wingate server from the client to see if your client is actually able to talk to the wingate server at this point in time. Also, try doing an nslookup for a domain to see if the client can resolve domain names at this time.