Wingate 6.01 "This page cannot be displayed"

[kobrien]

I've recently upgraded to the latest release of Wingate, but since I have I've been getting random "This page cannot be displayed" message when browsing from various users. Pressing refresh seems to then load the page, but it's quite agrevating whn in a secure site and having to start over from scratch.

Do you have any ideas as to what causes this?

[Pascal]

Are you using authentication at all, such as NTLM for your clients?

[kobrien]

No I'm not using any authentication. I just limit IP addresses that can access Wingate.

Thanks

[Pascal]

Hm. Two things then. First, add your ISPs DNS server (Or whichever DNS Server you want WinGate to use) in the list of explicitly configured servers in the DNS/WINS Resolver.

Secondly, turn on full debug logging for the WWW Proxy service, and try to catch a snippet from the logfile when this problem occurs. If possible, post that snippet to the forum (Or email to me directly)

[adrien]

One other thing - are you using the Multi-user IP feature in WinGate for these clients?

We found a license counting issue with this - if this is the case, then there should be log entries in the WWW Proxy server log with words to the effect of "license violation - exceeded number of licensed users" or some such.

Is this a trial activation?

Adrien

[kobrien]

No I'm not using the Multi User feature, we only have the pro version so it's not available. Handy to know though as we are looking to upgrade so we can use it.
It's not a trial activation.

Thanks

[kobrien]

Right,

I've added the DNS server and turned on Debug logging, but I've had the error since and nothing out of the ordinary showed in any of the logs as far as I can see.

Any other suggestions?

Thanks

[Pascal]

Okay, then - how do your clients connect? Are you going out through NAT, proxy connection by browser setting or are you using the WinGate Internet Client?

[kobrien]

Our clients connect using the proxy connection in the browser, which has worked fine on all previous version of wingate.

[Pascal]

I'd expect to see something then in the WWW Proxy Log. Either something that says "Caught Exception" or some kind of HTTP Error code. Did you have full debug logging turned on?

[kobrien]

Right now I know what to look for I've had another search through the yesterdays log and have found lots of examples of this error (with different random sites):

Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Host name lookup for 'suk.rd.yahoo.com' failed - terminating

[kobrien]

Here are a few more errors:

Error: Caught socket exception in CWWWSession::OnRead() Not a socket {Thd 242} [socket #FFFFFFFF] - terminating

Error: Caught socket exception in CWWWSession::OnRead() Not a socket {Thd 273} [socket #FFFFFFFF] - terminating

Error: Caught socket exception in CWWWSession::OnRead() Not a socket {Thd 189} [socket #FFFFFFFF] - terminating

Error: Caught socket exception in CWWWSession::OnRead() Socket Error 10058 {Thd 189} [socket #CAC, 0.0.0.0:1341 to 143.166.224.100:80] - terminating

[Pascal]

Which of these errors seem to coincide 'roughly' with the time when you were experiencing the problem?

[kobrien]

This is the error that was closest to point, but it was logged under a different user.

Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Host name lookup for 'suk.rd.yahoo.com' failed - terminating

Could another user having an error like this cause everyone else to get a page cannot be displayed message?

[Pascal]

No, shouldn't do - I was trying to find out which error message was the one for the connection that failed - but I'll check all those error codes when I get into the office. Might point us in a certain direction then.

Edited:
The error code coincides with the previous error messages. The lookup for the server failed and so it's next operation failed as well. Normally, this is because it was unable to resolve the name. This seems to be more prevalent where AD is in use, but it can also happen if WinGate deems there to be no acceptable DNS Servers. Can you check the DNS error logs, to see if there is anything else in there that might be of interest? Also, make doubly sure that you have the IP address of your DNS Server in the DNS/WINS Resolver config. Then WinGate does not have to rely on discovering that information, but will always have a manually entered server available. (Seems to cure this problem most of the time).

One other thing I can think of to check - we're seeing a lot of users who have multiple default routes. Generally, it's not necessary to add a default gateway to your LAN connection on the WinGate server.

Can you check what your route table looks like?