ENS memory problem

[SuperJ]

Hi,
Using,
- Wingate 6.0.4.b1025(No services, no dhcp, no winsock, no gdp, no pop3, no smtp, only ens with NAT and DNS service, logging turned off on all services)
- Windows 2000, service pack 4
- Celeron 300Mhz
- 256 MB RAM
- Bandwidth Controller 1.07
- USB ADSL Modem
- 1 External NIC

The above mentioned stand-alone system has been running wingate for 2 days and 10 hours. Up to this minute it is still up and running , however I've received this error three times during this up time.

Object: ENS
Time: 12-Jul-2006 23:10:32
Message ID: 0705
Description: Undefined ENS memory problem - possible cause: memory exhaustion. Statistics: Kernel mem: 0, Frag mem: 0

What is the cause of this error?
Should I ignore it?
Regards,
supaJ

[genie]

This memory problem might be a result of Bandwidth Controller conflict - have you tried upgrading to the latest Wingate? We have introduced some changes in the driver that help easing some of the conflicting problems.

[SuperJ]

This memory problem might be a result of Bandwidth Controller conflict - have you tried upgrading to the latest Wingate? We have introduced some changes in the driver that help easing some of the conflicting problems.

Thank you Genie. I will try that but for the moment I just want to let the system run to see if ever stops in a blue screen of death(why is windows the only OS with such a feature? It is so fustrating sometimes). I previously had that problem with wingate 5.2 and BC 0.31.

Thanks again.

Regards,
SupaJ.

[genie]

Aye, unfortuneately many of the network-related software packages are conflicting, because of the way their drivers hook into the system.

[alemos]

Aye, unfortuneately many of the network-related software packages are conflicting, because of the way their drivers hook into the system.

I have the latest version installed on a Windows 2003 server with only the application server (IIS + Com+ + Component Services) and wingate on that machine and I still get memory problems. I deactived bandwidth control and the problem stopped.

Any news on this front?

Thank you

[genie]

Aye - you can get away by increasing the number of network buffers through Advanced Options application for Wingate. The default value there is 512 - try increasing it to 1024 or 2048.