Socket Error 10049 {Thd 1216} [socket #183C, IP:2094 to :0]

[sbaloch]

Hi!...

For about 2 week ago we're having strange problem with our wingate proxy server that we've started receiving following

Socket Error 10049 {Thd 1216} [socket #183C, External IP Address:2094 to :0] - terminating

on the microsoft download site.

The browsing otherwise is OK and seems no problems with othersites but as soon as we try to download anything from microsoft download web site we receive the above error. Interestingly without using proxy the site works perfectly fine.


Can anyone please help what may be the cause of this and how to fix it?


Saqib,
Islamabad, Pakistan

[adrien]

10049 is 99.9999% certain some DNS issue.

Have you checked the ability to resolve the name of the server you're trying to connect to? e.g. try pinging it by name from behind WinGate.

Regards

Adrien

[sbaloch]

Yes the DNS is working perfectly fine and I can nslookup the site and also ping it without using wingate proxy.

but every other thing is working fine but I can't seem to download anything from download.microsoft.com

this error message comes only when I try to go to the above using wingate proxy other wise without proxy it is working fine.


Saqib

here is the result of pingPinging download.micoroft.com [82.98.86.175] with 32 bytes of data:



Reply from 82.98.86.175: bytes=32 time=328ms TTL=44

Reply from 82.98.86.175: bytes=32 time=256ms TTL=44

Reply from 82.98.86.175: bytes=32 time=195ms TTL=44

Reply from 82.98.86.175: bytes=32 time=189ms TTL=44



Ping statistics for 82.98.86.175:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 189ms, Maximum = 328ms, Average = 242ms

[adrien]

Hi

we just found (a couple of nights ago) a problem with the DNS resolver in WinGate specific to that site (download.microsoft.com).

It's related to the length of the chain of CNAME aliases in the response. for that hostname, the alias chain is 6 aliases deep before you get to an IP address (crazy!!!).

For obvious reasons we have to prevent CNAME loop attacks so we restrict the length of the alias chain we will follow... unfortunately we picked too low a number. I've increased it in code here. We are planning an incremental release of 6.x to address this an a couple of other smaller issues.

Regards

Adrien

[sbaloch]

Thanks a lot ...

How long we'll have to wait for an update for wingate to resolve this issue?

Saqib

[adrien]

quickest way to resolve the problem in the interim is to

a) edit the hosts file on the WinGate machine.

windows\system32\drivers\etc\hosts

add an entry for download.microsoft.com for its IP. you'll need to use nslookup or ping or something to get this IP.

That should prevent WinGate from doing the DNS lookup - it'll just use the hosts file.