ver 6.0.3 socket error : out of buffers

[sputnik]

Hello,

I have the latest ver of Wingate proxy(6.0.3) on a fresh build of windows 2000 server(sp4, all patches), and run into an error after about 30-60 minutes of operation: socket error : out of buffers.
I saw some postings on this, but no resolutions, might have to dig deeper. Any one hip to this?

[labull]

Have you tried the instructions below?

Larry

[LFrank]

I did - coming from the other thread mentioned by labull - no remedy.
Switched off the handshake stuff of my Intel/Pro+ - no cure ...

But I seem to be lucky having at least a consistent 36h of operation and not only minutes.

I will verify again and report in exactly 38 hours ;)

Lutz

[sputnik]

I tried the delete history files in Wingate directory. No effect for me.

[adrien]

Hi

It's been a while since we saw this problem.

If you check from the command-line with "netstat -an" and see if you have a lot of sockets open, there could be some network activity from your LAN causing problems. For instance if a LAN machine has a virus, this sometimes happens.

Adrien

[LFrank]

Hi Adrien,

that's leading to a follow-up issue of the socket-error. If it happens, I able to check the number of connections to Wingate from Taskmanager - but not to issue any nbtstat or netstat command. My system seems to have burried all network commands/activity in this 'state'.

Wasn't there a debug switch in Wingate which might help to narrow down the issue?

Regards,

Lutz

[adrien]

there is a program called process explorer, available from

http://www.sysinternals.com/ntw2k/freeware/procexp.shtml

Which will allow you to see all processes, and what resources they are using.

If wingate.exe's use of sockets is growing (indicating a leak) or any type of handle, then you should be able to see it as it is happening with this tool.

Regards

Adrien

[LFrank]

Up for 40h now ...

what I did - I found still having McAfee Firewall installed but disabled to start (having switched to Wingates NAT/Firewall). I uninstalled it now and suddenly have the server running for 40h now.

Current Time: Friday, 01-Oct-2004 10:30:07 W. Europe Daylight Time
Restart Time: Wednesday, 29-Sep-2004 18:08:29 W. Europe Daylight Time
Parent Server Generation: 0
Server uptime: 1 day 16 hours 21 minutes 38 seconds
Total accesses: 25 - Total Traffic: 30 kB

Keep fingers crossed.


Btw, the Process Explorer is a great tool - I was looking for something like this for long. Thanks for the hint. With two machines accessing via Wingate I found having now in peak times 1100 handles open but no stalled connections listed - looks pretty clean.

Best regards,

Lutz

[adrien]

OK, that's interesting. We will have a closer look at the McAffee firewall.

It is possible that the interaction between the two kernel drivers may be causes a buffer leak in the kernel, which will have this effect (out of buffers). The way to tell is to keep an eye on kernel memory in task manager.

Adrien

[LFrank]

Adrien,

definitly - I'm now up for nearly four days in a row without any issues or performance degradation. It was definitly the McAfee part interacting.

CU & Thanks for a great program

Lutz

[mufasir]

Dear Adrien

We don't have mcafee firewall.. but still we are having this client error and some times socket error problem at 50 times a day.. We have the latest version of wingate 6.0.3 (1005). Please help.

[adrien]

Hi

Do you run any other sort of firewall software? Even ZoneAlarm (some versions) can cause problems, even if it is disabled, since its network driver is still loaded.

What OS are you running this on?

Adrien