Socket Error 10049 / Wingate Stop working after several days

[tdorsch]

Hi everybody

I have checked the forum but didn’t have found anything that solves my problem.

I have wingate running on our company’s proxy for several years.
(win 2000 Server, 2MBits ISP connection)

All in all without major problems.

But since the last 4 month there is some strange malfunction.

After some days (sometimes after weeks) of working fine, wingate stops working.
Request on the network are answered by this message:

Socket Error 10049 {Thd 3332} [socket #C30, <LOCAL-IP OF A CLIENT>:3012 to :0]

It seems that wingate tries to lookup itself or something like this…
But “0” isn’t a valid IP at all… strange….

I usually restart the service and everything is fine again.. but after some days or some weeks I have the same problem again.

I never have to restart the server itself or other services running on the server…
I do restart wingate only… That’s why I guess that is a problem with wingate.

Any idea?

Windows 2000 Server current Wingate Version 6.2.1
(but hat the same problem with older version)




Karl

[adrien]

Hi

This is a classic symptom of DNS issues.

WinGate keeps track of responsiveness of all the DNS servers it knows about. Sometimes it seems to pick a bad server to start using.

the way to fix it is to

a) manually enter a known good DNS servers's IP into the DNS resolver configuration in GateKeeper and
b) if the machine WinGate is running on has any DNS servers configured in its adapters that WinGate shouldn't be using, enter these into the DNS servers exclusion list in the WinGate advanced option application (Start->Programs->WinGate->advanced options) and restart WinGate.

Let me know if that doesn't help

Regards

Adrien

[tdorsch]

Hi adrien,

Thank you for that idea.

My first intention also was to check DNS.
All in all DNS is working fine, also when wingate stops to work.
"ping whatever" works fine on the wingate-server.

But it may be a good idea to exclude some DNS servers, because we do operate an own domain DNS.

I found out that the domain DNS won’t redirect all DNS inquiries to the ISP DNS.
Maybe that was the reason for wingate to stop working.

But isn’t it strange that wingate won’t try the old DNS again.
Maybe this could be done better in new release.

It may be possible that the ISP DNS was not available (during IP change) and that’s why wingate decided to use the DNS service of the domain server.

Now I excluded the domain DNS as you suggested in point b).
Let’s see if this error will happened again.

[deftech]

Read my most recent post for my fix with this kind of problem. Kind of odd that this problem is happening to you as it is exactly what happened to me...is there something we don't know about going on? Is it aliens? Perhaps a bubonic plague virus?

:)

I had to change the www proxy server gateway to point to my wan adaptor. Hope this helps.

[tdorsch]

Hmm .. Thank you for that idea..

Wingate only shows the WAN interface to select, so it was set to the right one before.
But the IP setting for using with the wan interface may also be a point of failure.
Because we use 2 different Sub-network mask (for WAN and LAN network) wingate should never use any other IP than defend on this WAN interface.
Better to change "any" to the "wan ip" value.
Because this happens randomly… we should avoid any setting containing the words “any” or “wingate select the right one” ,o)