Socket Error when downloading MS Updates from clients

[ALainONE]

Hello!

I am currently using the latest version of WinGate (6.2.2) with 50 concurrent-user license running on a Windows Server 2003 with NTLM Authentication.

My problem is... whenever client computers try to download updates from MS WebSite, they always get the message:

Socket Error
Socket Error 10049 {Thd 2396} [socket #5994, 192.168.2.2:3395 to :0]

But if I try to download from the WinGate server itself, the download is always successful.

I don't have KAV or PureSight installed. My WinGate Server is running from a separate server and separate from the Domain and is NOT my DNS server.

Here's my current IP-configurations:
Domain (AD) Server : 10.19.98.1
WinGate Server : 10.19.98.2 (LAN-NIC) / 192.168.2.2 (ADSL-NIC)
ADSL Router : 192.168.1.1

All Client IP Addresses are through DHCP with DNS pointing to 10.19.98.1.

Any ideas? Please help.

Best regards,
Alain

[logan]

This sounds like a known problem with limited recursive DNS lookups. Try the following build and see if it fixes the problem.

http://www.wingate.com/downloads/WinGat ... 39-USE.EXE

[ALainONE]

Hello, Mr. Logan! How are you?

I just want to thank you for the update you have sent. IT SOLVED THE PROBLEM and now clients are being able to download the updates from MS.

Again, thank you very much!
Please do send my regards to the entire staff!

Best regards,
Alain Garcia

[frputz]

@logan

can you explain what this is ?

http://www.wingate.com/downloads/WinGat ... 39-USE.EXE

It shows it is a wingate 6.2.3 Version, but the offical download page today, shows version 6.2.2 as current.

So is this version for the public? And if yes can you please post the fix list or update the offical download page?

Thank's

Frank

[logan]

Hi Frank,

We are going to release another version of the WinGate 6.x tree that resolves a few known issues (like that of recursive DNS lookups). The link I provided in my earlier post is a pre-release build of this. I'm not sure of managements intentions for when to release it publicly, but it should be soon. If build 1139 has any fixes that you require, you can start using it now.


Build 1139
Released 24 April 2008
----------------------

1. Fixed recursion depth issue in DNS resolver which would fail DNS requests returning alias chains longer than 5 levels of indirection (affected download.microsoft.com).

2. Fixed issue with NTLM login in various WinGate services due to token length issues, occasionally seen on ADs with Vista and 2003 server.

3. Changed type for DHCP time offset option from unsigned to signed integer to allow for negative time offsets.

4. Fixed an issue with persistence of websites (was not removing deleted host headers).

5. Fixed an issue in the DHCP server that was causing lease information to be incorrectly stored. This caused clients to be forced to obtain new IP addresses if the WinGate server was rebooted.

6. Added watchdog thread support for further diagnostics.

7. Fixed issue where system message on startup could create deadlock when starting up with large NT User database.

[frputz]

Hello logan,

absolutly we have some problems similar to this.. and i am very happy to see your post, because we have some complains from our user due to the wingate problems we have..
I installed the version from your post and i am very surprised because i got the report that the problem we have seems to be solved :-)

I have still the new Wingate Version in my Bugdet and this is what i like to see till the new version is released because i had to defend my position to invest money in a new licence of Wingate and waiting so long for it makes some people nervous here :-)...

So today i am very satisfied...

Thank you and best regards