Socket Error For Users

[tpateman]

Hi,

I have had a continued problem with WinGate and users getting socket errors. I have spoken to Deerfield who have advised me to submit a topic here. To try and fix the issuse I have upgraded to the latest version 5.0.7 and now tried deleting and recreating the WWW Proxy Service but no luck. Users are still getting the following socket error :

Socket Error
Connection to Remote Host timed out

Sometimes users also get this error:

Client error
Host name lookup for 'www.deerfield.com' failed

It is mainly the socket error which keeps coming up.
SOCKS is not configured on any of our clients PC's. Please advise.


Thanks,

Timothy.

[adrien]

Is it only for connections to the same destination, or randomly?

It is possibly nothing wrong with WinGate or your setup, but frequently problems on links to the remote site you are trying to connect to can cause this.

Are you using dialup?

Adrien

[tpateman]

There isnt any pattern to any of the sites which you get socket or client error on, just happens randomly.

It is happening far too often and to too many different site even main sites like deerfield, microsoft, google etc which to me would suggest something wrong our end.

We are using ADSL.

Thanks,

Timothy.

[asciipixel]

Did you guys figure out what was wrong here I am having the same issue with wingate 4.5.2 ...

[Nev]

Did you guys figure out what was wrong here I am having the same issue with wingate 4.5.2 ...

Looks like a DNS problem, is it the same on the server machine or just the clients [to isolate the culprit]?

Nev.

[DBeard]

I'm getting these socket errors as well.

[alejandroc]

I keep getting the same Socket or Client Errors. We're using ISDN and Win XP Pro SP1. In our case, though, it happens after quite some time of being connected or after the connection has been idle for some time. I'll be checking for updates on this subject. Thanks.

[tpateman]

Im still getting these error more often, Please can you advise and thoughts on how to work around this?

[Pascal]

Im still getting these error more often, Please can you advise and thoughts on how to work around this?

Are you still running version 5.0.7 ? If not, the first suggestion would be to upgrade to that.

Secondly, once these socket errors occur, do they keep on happening until you initiate some action - such as stop/starting the WG Server or restarting the actual PC ?

How are your client PCs connected, through WGIC, proxies or using NAT ? Also, as Nev asked, is it only from the clients or from the clients and the server ?

[tpateman]

Hi,

Yes we are still running version 5.0.7, our license key is only for version 4 can we upgrade? Is it just a reinstall over the top?

When we get Socket and Client look up errors you need to click refresh often about 5 times to get the page to come up. It takes some time.

All clients are connected direct to wingate which acts as a proxy for us. As far as I'm aware this does happen on the servers as well.

Thanks in advance and I hope to hear from you soon.
Regards,
Timothy.

[DBeard]

This problem exist under current version as well, as I have been posting here for months on.

[hunt1]

Did you use a dhcp server on your network to let client pc's get
ip addresse or you define a static ip for each pc ?

[tpateman]

Did you use a dhcp server on your network to let client pc's get
ip addresse or you define a static ip for each pc ?

We use DNS and DHCP, Some users do have asigned static ip address's but this is happening with everyone.

Internet Explorer is configured to go stright to the proxy server which is wingate.

Any Ideas?

[kalvos]

I may have a little more info, as this DNS issue has crossed many threads.

Here, I have seen it most often happen after a soft reboot of the client. In fact, transfers in general are a little slower and less reliable unless I do a power down of the client.

If I just go through a Windows restart, however, the unknown-host issue is prevalent on any newly visited site.

I am using 3com 3C905's in the WinGate server (cable modem), and a variety of cards in the clients (3com, Linksys, etc.). All clients work much more reliably after a power-down restart.

Back to waiting,
Dennis

[Pascal]

Yes we are still running version 5.0.7, our license key is only for version 4 can we upgrade? Is it just a reinstall over the top?

Yes, you can and yes, it's just a re-install over the top.

[tpateman]

Have done the upgrade but the problem is still happening. Please can you advise some more. Where do you think the problem is?

Thanks in advance. Timothy.

[Pascal]

Have done the upgrade but the problem is still happening. Please can you advise some more. Where do you think the problem is?

Would you run a debug kit for me, please ? It's a version of WG that logs internal debugging information to a file - that might help us pinpoint his problem.

Thanks,

[tpateman]

Would you run a debug kit for me, please ? It's a version of WG that logs internal debugging information to a file - that might help us pinpoint his problem.

Thanks,

Yes I can do that, Please just tell me how I carry this out. Thanks, Timothy.

[ignition]

I had the same problem when NATtting 2 users .....
after i created a www proxy with the option transparent redirection selected. (deleting the service solved the problem)

But after reinstalling my Windows XP everything went fine .... no more errors

[tpateman]

Hello,

Pascal any news on the debug logging software for wingate to try and find out what is causing the socket and client look up errors? Thanks. Timothy.

[Pascal]

Hello,

Pascal any news on the debug logging software for wingate to try and find out what is causing the socket and client look up errors? Thanks. Timothy.

Emailed. If you don't receive it in a reasonable timeframe, post back to me again please, I seem to have problems getting to some domains. Thanks,

[tpateman]

Thanks, I have got the debugger and have now emailed you back the log file. It is about 4/5 mb in size so let me know if you dont get it.

Thanks in advance, Timothy.

[Pascal]

Thanks, I have got the debugger and have now emailed you back the log file. It is about 4/5 mb in size so let me know if you dont get it.Thanks in advance, Timothy.

Got it, looking through it now and I've sent it to the dev-list here. Will let you know when something comes up, but in the meantime, you can revert back to the released version (So as to not clutter up your hard-drive with that log file)

[tpateman]

Got it, looking through it now and I've sent it to the dev-list here. Will let you know when something comes up, but in the meantime, you can revert back to the released version (So as to not clutter up your hard-drive with that log file)

Hi Pascal, Any news yet form the dev-list? Or any updates from yourself?
Thanks, Timothy.

[Pascal]

We're currently investigating DNS issues, which we believe might be related. The current theory holds that it is a load related problem, so how heavily loaded is your system ?

[dannyd]

I have the same problem. Try changing the WWW Proxy Server port to 8080. The "Socket error" dissapeared since then.

[tpateman]

We're currently investigating DNS issues, which we believe might be related. The current theory holds that it is a load related problem, so how heavily loaded is your system ?

For WinGate, we have 50 user licenses and we have less staff than 50. Our emails connections from users go direct to the mail server and not through WinGate. WinGate is mainly only used for Internet browser connections. WinGate never seems to be heavily loaded.
Thanks, Timothy.

[tpateman]

Hi,

Is there any news from the Dev list to what this is? Thanks and look forward to the update.

Regards,

Timothy.

[pecos]

I was having a similar problem, and it seems to have been fixed by removing Microsoft Office from the Startup folder.

It's something to try, anyway.

--Tom

[tpateman]

Any News Please?