wingate 6.6.0 500 socket error

[Pxt]

hi,

We have a wingate 6.5.2 server and i have upgraded it to 6.6.0.After reboot,the proxy does not allow connection to sites ( clients get Socket Error Connection to Remote Host Times out ) and the wwwproxy log shows an entry Error: responding with code 500 Socket error.I have had to revert back to 6,5.2 to get a working scenario again.The Server has 2 Nics, one for internal ,the other for External and there are no dns settings on the internal nic.I have configured WIngate and the external for DNS Servers.

If i upgrade 6.5.2 to 6.6.0 and do not reboot the server and start the wingate engine then clients can browse via the proxy but after reboot same issue.

Any help would be gratefully appreciated.

pxt

[adrien]

OK, that points to a driver issue.

We're looking into it now. Thanks

Adrien

[adrien]

Hi

Looks like a problem introduced with ARP lookups that only affects some gateways so we didn't see it in testing here or other test customer sites. We've a fix, we'll have to release another patch today.

Adrien

[genie]

Hi, Pxt

I can send you the new driver for testing - I need the OS you are running Wingate on and your email address - you can drop me an email with this information.

Regards,
Gene

[Pxt]

Hi genie,

Thanks very much for your reply.We are using 2003 Server Standard R2.my email address is [address removed for privacy reasons].

regards

pxt

[Pxt]

Hi Adrien/Genie,

Thank you very much,the 6.6.1 upgrade fixes the problem.

best wishes

pxt

[Shafqat Niaz]

Wingate Client gets a socket error after 10 minutes of Wingate server(6.6.1) on Windows 2000 Professional SP4.Internet can be accessed on the Wingate server machine but all clients get Socket error message.This problem is coming from last few days.

Socket Error

Socket Error 10049 {Thd 1764} [socket #FCC, 0.0.0.0:4865 to :0]


And Name Look up error faced.

[adrien]

Hi

This indicates that the WinGate DNS resolver isn't able to resolve names. This usually happens when it is configured to use a DNS server that's not responding, or some other DNS service error.

By default WinGate uses the DNS servers specified in the TCP/IP configuration of your network adapters, or discovered by the operating system (e.g. by DHCP or dialup).

It will also use DNS servers you manually specify in the DNS resolver settings in GateKeeper.

So, the steps are:

1. Make sure that any DNS server specified on any network adapter on your system is valid.
2. If a specified DNS server is not valid for internet lookups (e.g an internal Active Directory server), exclude it from WinGate (see below).
3. Make sure any DNS server WInGAte is using, is not itself using WinGate for DNS (loop). If so exclude it as well.

To exclude a DNS server.

1. Start->Programs->WinGate->WinGate advanced options
2. Select DNS
3. Enter the IP address of the DNS server you wish WinGate to exclude.
4. Restart WinGate.

You can also manually specify DNS servers to use. If the above doesn't help, specify your ISP DNS server directly in WinGate.

Regards

Adrien