Another Wingate crash here.

[Farleytron]

Hi. Thanks for checking out my problem!

I am using Wingate 5.1 as a NAT/Firewall only. No other special features of Wingate are in use.

DHCP - Disabled
Winsock Redirector - Disabled
GDP Service - Disabled
DNS Service - Enabled
Remote Control Service - Enabled
POP3 Service - Disabled
SMTP Service - Disabled
Caching - Disabled
Dialer - Disabled

All logging on all services has been disabled.

The system is an old Compaq K6-2 350 running WinXP SP1 with 128MB of RAM, a built-in Intel 21143 10Mbit adapter, a AN983 10/100 Generic adapter, and an RTL8180 Wireless 11Mbit wireless adapter.

My cable modem connects to the AN983, the Intel 21143 connects to a generic 10/100 switch, three wired clients connect to the switch, and one wireless client (laptop) connects to the RTL8180 via a pcmcia card.

IP's:
67.8.xxx.xxx : AN983 10/100 on Cable modem
192.168.100.1 : Intel 21143
192.168.200.1 : RTL8180 Wireless

It works wonderfully 90% of the time, until I try to use my Emule Plus 1i client to download stuff. I like to leave it running overnight, and usually sometime during the night Wingate crashes. I leave the "server" logged off when not in use. When I wake up in the morning, all internet connectivity is gone for the clients and the "server" has only a cursor on the screen and nothing else. I can't log into the server nor can I ctrl-alt-del. I can only reboot the system.

I tried reducing the number of connections used by the Emule client from 3000 to 500. I also tried other tweaks to no avail.

The only reason I switched from ICS to Wingate was because ICS refused to work properly with my wireless card.

Any ideas?

Here is my configuration report:

1.01 WINGATE CONFIGURATION REPORT
1.02 Saturday, January 10, 2004, 21:34
1.03
1.04 ---------------------------------------------
1.05 WinGate Engine
1.06 ---------------------------------------------
1.07 WinGate 5.1.0 (Build 867)
1.08 Operating System: Windows 2000 (NT 5.1)
1.09 Language: enu
1.10
4.01 ---------------------------------------------
4.02 Dialer information
4.03 ---------------------------------------------
4.04 Dialer is disabled
4.05
5.01 ---------------------------------------------
5.02 Network Interfaces
5.03 ---------------------------------------------
5.04 127.0.0.1 (LOOPBACK) [Internal] [Secure]
5.05 192.168.100.1 (LAN) [Internal] [Secure]
5.06 67.8.xxx.xxx (LAN) [External] [Unsecure]
5.07 192.168.200.1 (LAN) [Internal] [Secure]
5.08
6.01 ---------------------------------------------
6.02 Services
6.03 ---------------------------------------------
6.04
6.05 System Policies
6.06 ---------------------------------------------
6.07 Default System Access Rights:
6.08 Everyone - Unrestricted rights
6.09 Default Start/Stop Rights:
6.10 Administrators - Unrestricted rights
6.11 Default Edit Rights:
6.12 Administrators - Unrestricted rights
6.13
6.14 POP3 Proxy server (POP3 Proxy server)
6.15 ---------------------------------------------
6.16 Session Timeout: 120
6.17 Port: 110
6.18 Startup: Disabled
6.19 Binding 1: 127.0.0.1
6.20 Binding 2: 192.168.100.1
6.21 Binding 3: 192.168.200.1
6.22 Access Rights: Defaults: may be used instead
6.23 Start/Stop Rights: Defaults: may be used instead
6.24 Edit Rights: Defaults: may be used instead
6.25
6.26 DHCP Service (DHCP Service)
6.27 ---------------------------------------------
6.28 Session Timeout: 60
6.29 Port: 67
6.30 Startup: Disabled
6.31 Binding 1: 192.168.100.1
6.32 Binding 2: 192.168.200.1
6.33 Access Rights: Defaults: are ignored
6.34 Everyone - Unrestricted rights
6.35 Start/Stop Rights: Defaults: may be used instead
6.36 Edit Rights: Defaults: may be used instead
6.37
6.38 Winsock Redirector Service (Winsock Redirector Service)
6.39 ---------------------------------------------
6.40 Session Timeout: 20
6.41 Port: 2080
6.42 Startup: Automatic start/stop
6.43 Binding 1: 127.0.0.1
6.44 Binding 2: 192.168.100.1
6.45 Binding 3: 192.168.200.1
6.46 Access Rights: Defaults: may be used instead
6.47 Start/Stop Rights: Defaults: may be used instead
6.48 Edit Rights: Defaults: may be used instead
6.49
6.50 POP3 Server (POP3 Server)
6.51 ---------------------------------------------
6.52 Session Timeout: 120
6.53 Port: 110
6.54 Startup: Manual start/stop
6.55 Binding 1: 127.0.0.1
6.56 Binding 2: 192.168.100.1
6.57 Binding 3: 192.168.200.1
6.58 Access Rights: Defaults: may be used instead
6.59 Start/Stop Rights: Defaults: may be used instead
6.60 Edit Rights: Defaults: may be used instead
6.61
6.62 SMTP Server (SMTP Server)
6.63 ---------------------------------------------
6.64 Session Timeout: 300
6.65 Port: 25
6.66 Startup: Manual start/stop
6.67 Binding 1: 127.0.0.1
6.68 Binding 2: 192.168.100.1
6.69 Binding 3: 192.168.200.1
6.70 Access Rights: Defaults: may be used instead
6.71 Start/Stop Rights: Defaults: may be used instead
6.72 Edit Rights: Defaults: may be used instead
6.73
6.74 GDP Service (GDP Service)
6.75 ---------------------------------------------
6.76 Session Timeout: 60
6.77 Port: 368
6.78 Startup: Disabled
6.79 Binding 1: 127.0.0.1
6.80 Binding 2: 192.168.100.1
6.81 Binding 3: 192.168.200.1
6.82 Access Rights: Defaults: may be used instead
6.83 Start/Stop Rights: Defaults: may be used instead
6.84 Edit Rights: Defaults: may be used instead
6.85
6.86 DNS Service (DNS Service)
6.87 ---------------------------------------------
6.88 Session Timeout: 60
6.89 Port: 53
6.90 Startup: Automatic start/stop
6.91 Binding 1: 192.168.100.1
6.92 Binding 2: 192.168.200.1
6.93 Access Rights: Defaults: may be used instead
6.94 Start/Stop Rights: Defaults: may be used instead
6.95 Edit Rights: Defaults: may be used instead
6.96
6.97 WWW Server for viewing log files (Logfile Server)
6.98 ---------------------------------------------
6.99 Session Timeout: 60
6.100 Port: 8010
6.101 Startup: Automatic start/stop
6.102 Binding 1: 127.0.0.1
6.103 Binding 2: 192.168.100.1
6.104 Binding 3: 192.168.200.1
6.105 Access Rights: Defaults: may be used instead
6.106 Start/Stop Rights: Defaults: may be used instead
6.107 Edit Rights: Defaults: may be used instead
6.108
6.109 Remote Control Service (Remote Control Service)
6.110 ---------------------------------------------
6.111 Session Timeout: 60
6.112 Port: 808
6.113 Startup: Automatic start/stop
6.114 Binding 1: 127.0.0.1
6.115 Binding 2: 192.168.100.1
6.116 Access Rights: Defaults: may be used instead
6.117 Start/Stop Rights: Defaults: may be used instead
6.118 Edit Rights: Defaults: may be used instead
6.119
7.01 ---------------------------------------------
7.02 System Route Table
7.03 ---------------------------------------------
7.04 Current Route Table:
7.05 ---------------------------------------------
7.06 Network Mask Gateway Interface Metric
7.07 0.0.0.0 0.0.0.0 67.8.128.1 67.8.135.208 20
7.08 67.8.128.0 255.255.248.0 67.8.135.208 67.8.135.208 20
7.09 67.8.135.208 255.255.255.255 127.0.0.1 127.0.0.1 20
7.10 67.255.255.255 255.255.255.255 67.8.135.208 67.8.135.208 20
7.11 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
7.12 192.168.100.0 255.255.255.0 192.168.100.1 192.168.100.1 30
7.13 192.168.100.1 255.255.255.255 127.0.0.1 127.0.0.1 30
7.14 192.168.100.255 255.255.255.255 192.168.100.1 192.168.100.1 30
7.15 192.168.200.0 255.255.255.0 192.168.200.1 192.168.200.1 30
7.16 192.168.200.1 255.255.255.255 127.0.0.1 127.0.0.1 30
7.17 192.168.200.255 255.255.255.255 192.168.200.1 192.168.200.1 30
7.18 224.0.0.0 240.0.0.0 67.8.135.208 67.8.135.208 20
7.19 224.0.0.0 240.0.0.0 192.168.100.1 192.168.100.1 30
7.20 224.0.0.0 240.0.0.0 192.168.200.1 192.168.200.1 30
7.21 255.255.255.255 255.255.255.255 67.8.135.208 67.8.135.208 1
7.22 255.255.255.255 255.255.255.255 192.168.100.1 192.168.100.1 1
7.23 255.255.255.255 255.255.255.255 192.168.200.1 192.168.200.1 1
7.24
8.01 ---------------------------------------------
8.02 Enhanced Network Support
8.03 ---------------------------------------------
8.04 Enhanced Network Support: 5.10 Syz - Installed and active
8.05 Driver: Enabled
8.06 NAT: Enabled
8.07 Router: Enabled
8.08 Firewall level: Custom
8.09
8.10 Firewall
8.11 ---------------------------------------------
8.12 Disable network name broadcasts to the Internet: Enabled
8.13 Allow users to ping this machine locally: Enabled
8.14 Allow users to ping this machine from the Internet: Disabled
8.15 Discard spoofed packets: Enabled
8.16
8.17 Routing
8.18 ---------------------------------------------
8.19 Multiple default routes: Enabled
8.20 Relay UDP broadcast packets: Enabled
8.100
8.101 Port Security
8.102 ---------------------------------------------
8.103
8.104 Security for: External TCP
8.105 Action: Redirect Port: 4662 -
8.106 Action: Redirect Port: 4711 -
8.107
8.108 Security for: External UDP
8.109 Action: Redirect Port: 4672 -
8.110
8.111 Security for: Internal TCP
8.112
8.113 Security for: Internal UDP
8.114
8.115 Security for: NAT TCP
8.116 Action: Allow Port: 4662 -
8.117
8.118 Security for: NAT UDP
8.119 Action: Allow Port: 4672 -
8.500
9.01 ---------------------------------------------
9.02 END OF CONFIGURATION REPORT

[Pascal]

I am using Wingate 5.1 as a NAT/Firewall only. No other special features of Wingate are in use.

There has been a few fixes since 5.1 that might affect you. (Some listed below). The first thing I'd try would be to upgrade to 5.2.2.

=======================
5.2:
"Out Of Buffers" error fixed. This was due to a leak in the ENS of kernel memory, resulting in the OS running out of memory for new socket connections, with the error "out of buffers" being reported.

Fixed an issue where the 'Relay UDP broadcasts' option was not being adhered to correctly.


5.2.2
Fixed relaying/NAT of fragmented UDP packets in the driver.

=======================

[genie]

Hi,

Will you be able to install the test driver? We have nailed a bit of a problem in the driver related to Realtek cards, so this new driver might help solve this problem. Let me know and I'll post this new driver to you.

[Farleytron]

Let me try 5.2.2 first and see if my issue is resolved. If not, then maybe the beta driver would be a viable option....

I also noticed that WinXP Pro has a limit of 10 simultaneous inbound connections. I wonder if that could be the problem. Many people on the board have tried Win 2003 Server, which has a higher limit (or not limit?), with greater success after experiencing similar issues.

I have also heard that Win98 has no such limit either...although I shudder at the thought of using Win98 as my gateway/firewall!

I'll keep you guys posted on my situation once I make the change to 5.2.2

Thanks!

[genie]

What kind of limit is that? Ddid you refer to Wingate-specific limitation or was it a system-related limit (like a number of listening sockets)?

[Mendoza]

Interesting.I also use Win Xp Pro for my server ( In know not a good ideea).Is there a limit in how many simultaneous connexions can be?