WinGate Server Not Responding to Clients

[ccsoft]

Hi,

I have a customer who is experiencing sporadic problems with his WinGate 4.51 installation. This is on an NT 4 with SP6, using manual proxy settings.
On what appears to be a total random basis, he finds that the WinGate server will just stop responding to client requests. The Internet Connection is still active but the clients are not receiving anything back.

Here is a snipit of his log file for a period when this happened...

09/23/03 16:10:12 10.160.83.99 Guest 0000051433 Requested: http://www.microsoft.com/isapi/redir.dll
09/23/03 16:10:20 10.160.83.99 Guest 0000051421 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 297} [socket #BDC, 0.0.0.0:3925 to :0] - terminating
09/23/03 16:10:20 10.160.83.99 Guest 0000051421 Terminated exit code 1
09/23/03 16:10:20 10.160.83.99 Guest 0000051433 Debug: WWW Session sending server request in thread f5

09/23/03 16:10:20 10.160.83.99 Guest 0000051421 Debug: Client closed connection in thread 129
09/23/03 16:10:24 10.160.83.105 Guest 0000051435 Requested: http://www.google.ca/
09/23/03 16:10:29 10.160.83.102 Guest 0000051422 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 275} [socket #65C, 0.0.0.0:3926 to :0] - terminating
09/23/03 16:10:29 10.160.83.102 Guest 0000051422 Terminated exit code 1
09/23/03 16:10:29 10.160.83.102 Guest 0000051423 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 294} [socket #A8C, 0.0.0.0:3927 to :0] - terminating
09/23/03 16:10:29 10.160.83.102 Guest 0000051423 Terminated exit code 1
09/23/03 16:10:29 10.160.83.102 Guest 0000051436 Requested: http://www2.marketwatch.com/images/bran ... r-vert.gif
09/23/03 16:10:29 10.160.83.102 Guest 0000051437 Requested: http://cbs.marketwatch.com/images/buttons/go.gif
09/23/03 16:10:32 10.160.83.105 Guest 0000051435 Debug: WWW Session sending server request in thread d7

09/23/03 16:10:38 10.160.83.99 Guest 0000051427 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 320} [socket #AF0, 0.0.0.0:3928 to :0] - terminating
09/23/03 16:10:38 10.160.83.99 Guest 0000051427 Terminated exit code 1
09/23/03 16:10:38 10.160.83.102 Guest 0000051437 Debug: WWW Session sending server request in thread 154

09/23/03 16:10:38 10.160.83.99 Guest 0000051429 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 342} [socket #800, 0.0.0.0:3929 to :0] - terminating
09/23/03 16:10:38 10.160.83.99 Guest 0000051429 Terminated exit code 1
09/23/03 16:10:38 10.160.83.99 Guest 0000051429 Debug: Client closed connection in thread 156
09/23/03 16:10:38 10.160.83.99 Guest 0000051430 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 326} [socket #790, 0.0.0.0:3930 to :0] - terminating
09/23/03 16:10:38 10.160.83.99 Guest 0000051430 Terminated exit code 1

I was going to suggest he move up to version 5.07... but wanted to check and make sure that this would resolve this issue.

Thanks

Joan

[adrien]

that socket error 10049 is WSAENAME - means we tried to connect to a bad name - usually in these cases it was when we tried to connect to 0.0.0.0 because the DNS resolver failed.

There were a bunch of DNS resolver issues that we fixed with 5.0

Adrien

[ccsoft]

Hi Adrien,

I had suspected a DNS issue and we had created a UDP mapping and disabled the DNS Server awhile ago.
Does that change your advice? Or do you still think 5.x will fix him up?

Thanks!
joan

[adrien]

the UDP mapping will only provide service to the LAN clients for DNS, thereby bypassing WinGate's DNS server, which otherwise uses the DNS resolver in WinGate, so basically creating the UDP mapping was a workaround for clients using WinGate as a DNS server only.

WinGate itself still uses the resolver however, so any proxy requests etc would fail if the resolver failed.

So I stick to my earlier advice... I think an upgrade will help them a lot.

[cunham]

Hello all.

Searching for a solution to a similar problem I´m having, I found the link to this forum, which I think will help me, although the last message has been posted a long time ago.

A customer is having the following problem: suddenly, client machines lose connection to Internet(they use www, pop and smtp proxies). And the same way, they return to normal operation after a short time. If I stop and start the Qbik service, this works too.

No errors in log and broadband connection is not lost. It does not seem to be an infrastructure problem, since the wingate machine keeps responding to icmp(echo) packets.

The current Wingate version is 5.2.3, 25 user, running on a win xp pro machine with 512 MB RAM. Plus, as I´m not a Wingate specialist, I noted that client machines are not using Wingate as DNS resolver; instead, they are using internal MS root hint dns servers. Important to say also is that the machines are proxy clients.

Should it be a matter of version upgrade also?

Thanks in advance

Cunha M,

[Nev]

Should it be a matter of version upgrade also? Thanks in advance Cunha M,

Hi,

Yes a version upgrade is highly recommended, the licence will provide the same functions in Wingate with all the fixes for free.