How do I fix the ENS problem in WinGate 5.2.3

[DeltaWolf7]

I am running Windows 2003 Server Standard edition and WinGate 5.2.3.

I have a problem where if ENS is loaded no internet works, they all just seem dead. If I unload the driver and restart the computer everything works great again.

Please can someone help me with a solution to this problem?

Thank you, DW

[sietze]

I have the same problem.

All logs are clean but the NAT log (debugging on) where I see:

03/25/04 12:27:23 Debug: NAT error message code FFE0B40B, context 1412 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=762, InTcp=88
03/25/04 12:27:23 Debug: NAT error message code FFE0B40B, context 1420 OutICMP=3, InICMP=18, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
03/25/04 12:27:23 Debug: NAT error message code FFE0B40D, context 1426 Total locked memory in use is 190500
03/25/04 12:27:23 Debug: NAT error message code FFE0B40E, context 1433 Unknown Frames = 0, Status Queue Size = 128
03/25/04 12:27:26 Debug: NAT error message code FFE0B407, context 55 TCP checksum failed
03/25/04 12:27:28 Debug: NAT error message code FFE0B40B, context 1412 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=762, InTcp=88
03/25/04 12:27:28 Debug: NAT error message code FFE0B40B, context 1420 OutICMP=2, InICMP=18, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
03/25/04 12:27:28 Debug: NAT error message code FFE0B40D, context 1426 Total locked memory in use is 190500
03/25/04 12:27:28 Debug: NAT error message code FFE0B40E, context 1433 Unknown Frames = 0, Status Queue Size = 128
03/25/04 12:27:29 Debug: NAT error message code FFE0B406, context 102 UDP checksum failed

[DeltaWolf7]

Is this a bug in the code or something we can fix by reconfiguring something?

[sietze]

Do you see the same entries in the NAT log?

In another thread Adrien states that they are not really errors.
Checksum errors are bad news. Not having checksums errors but logging them anyway is not good eiher.

[DeltaWolf7]

Yes i do see that sort of thing.

Is there a work around?

[ingeltra]

Yes i do see that sort of thing.

Is there a work around?

windows server 2003 really stinks i remember when i installed wingate on it i had to disable services like dns server and clinet and dhcp so that wingate works. in addition i couldn't find the conflict between wingate socks and windows socks server so i change the port to 1081 instead of 1080 but as far as ens i didn't have any problem and msn connects (nat to 1863) with no problems.

[DeltaWolf7]

Do you really think Windows 2003 sucks?
To be honest with you it been great apart from WinGate.
I havent had any conflicts with dns or dhcp servers.

It all works very very well apart from when ens is enabled then no internet connection works.

[sietze]

It is not a W2003 issue. It is about port conflicts. Any Windows version with DNS would require some planning when you want to install other software that comes with DNS.

Of course these observations are off theme.
The important thing is: how do we get ENS to work!

[Pascal]

03/25/04 12:27:23 Debug: NAT error message code FFE0B40B, context 1412 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=762, InTcp=88
03/25/04 12:27:23 Debug: NAT error message code FFE0B40B, context 1420 OutICMP=3, InICMP=18, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
03/25/04 12:27:23 Debug: NAT error message code FFE0B40D, context 1426 Total locked memory in use is 190500
03/25/04 12:27:23 Debug: NAT error message code FFE0B40E, context 1433 Unknown Frames = 0, Status Queue Size = 128

Those entries are not errors. They are simply debug / informational messages, but because ENS uses the same logging mechanism to report errors, WinGate indicates them as errors.

The checksum however, is not so good. That is an error.

Few questions:

(a) How do you connect to the Internet ?
(b) Is it possible to post a route table with your internet connection active ? (route print from a cmd prompt, copy and paste)

[sietze]

I have been able to download the install set for WG 5.2.2 from somewhere. I have this running now. No probs with ENS anymore.
No checksum errors in the NAT log anymore either. (See attached log at bottom of this post)

I understand that part of the information in the log is just a dump. But the checksum thing does seem to indicate a real problem, and it is fairly probable that it is related to the ENS problem. Reasons why I think so:

- when downgrading both things disappear. No other changes but deinstalling 5.2.3 and installing 5.2.2 were made in between.

- solicited traffic that has ben sent out is handled correctly by the router, and replies to the requests are sent back to the WG box. Looking at the router and sniffing the external hub confirms this. Only when th return packets have made it to the external interface of the WG box are they dropped. WG does not say it drops anything in any log. But the checksum errors are appearing at this point. Might be coincidental. Though bad checksums generally are a good reason for dropping whatever.

I will pass you the routing table in the next post. However, the routing table seems to be OK. When stopping WG things start working again, like being able to do nslookups to outside nameservers. And when installing other firewall software on the very same box things work fine as well.

Soemwhere I have mentioned the hypothesis that this ENS prob might be related to NAT behind NAT. But that are just my 2 cents.

The NAT log with debugging for 5.2.2:

03/26/04 11:18:16 Debug: NAT error message code FFE0B40B, context 1417 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
03/26/04 11:18:16 Debug: NAT error message code FFE0B40B, context 1425 OutICMP=2, InICMP=3, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
03/26/04 11:18:16 Debug: NAT error message code FFE0B40D, context 1431 Total locked memory in use is 190338
03/26/04 11:18:16 Debug: NAT error message code FFE0B40E, context 1438 Unknown Frames = 0, Status Queue Size = 128
03/26/04 11:18:21 Debug: NAT error message code FFE0B40B, context 1417 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
03/26/04 11:18:21 Debug: NAT error message code FFE0B40B, context 1425 OutICMP=2, InICMP=3, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
03/26/04 11:18:21 Debug: NAT error message code FFE0B40D, context 1431 Total locked memory in use is 190338
03/26/04 11:18:21 Debug: NAT error message code FFE0B40E, context 1438 Unknown Frames = 0, Status Queue Size = 128

[sietze]

Please find the routing table below.
Table was identical for both WG 5.2.3 and now for 5.2.2

C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 20 18 2d 4b b4 ...... Realtek RTL8029(AS) Ethernet Adapt
0x1000004 ...00 0c 6e a8 24 4c ...... SiS NIC SISNIC
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.33.1 10.0.33.18 1
10.0.33.0 255.255.255.0 10.0.33.18 10.0.33.18 1
10.0.33.18 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.0.33.18 10.0.33.18 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.33.0 255.255.255.0 192.168.33.18 192.168.33.18 1
192.168.33.18 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.33.255 255.255.255.255 192.168.33.18 192.168.33.18 1
224.0.0.0 224.0.0.0 10.0.33.18 10.0.33.18 1
224.0.0.0 224.0.0.0 192.168.33.18 192.168.33.18 1
255.255.255.255 255.255.255.255 10.0.33.18 10.0.33.18 1
Default Gateway: 10.0.33.1
===========================================================================
Persistent Routes:
None


(Wow, this layout is hard to read wrapped around in this small window. Let me know if you have a problem so that I can mail this off list)

[sietze]

> a) How do you connect to the Internet ?

Sorry I missed this one. At present the connection is through a Cisco 2600 router that is connected to a permanent ISDN circuit.

Once the system is installed at the customer's location it will access the Internet through a 3Com ADSL router. IP address ranges and other settings hoewever will be identical.

[adrien]

Those checksum errors occur whenever WinGate ENS receives a packet from the network with a bad checksum.

we then drop the packet.

That means something on your LAN (or network) is sending packets with bad checksums..

[adrien]

hmmm, so therefore most odd that you get this only with 5.2.3 and not 5.2.2. We are looking into a couple of issues with the 5.2.3 driver, and hope to get another one out soon, in the meantime, you are actually able to run the 5.2.2 driver with WinGate 5.2.3 as well.

Adrien

[sietze]

Well, I given you people something to think about ;-)
It really seems to be between 5.2.2 and 5.2.3 You know what changes were made to the code between those 2 versions.

All the other software I throw at these returned packets doesn't see anything wrong with them either. No complaints about checksums.

Also, when I go through the forums I get the impression that there might be more people seeing the same prob. But not everybody seems to be running debugging logs. At least they don't report them.

Apart from setting this up for a customer I will have a test box running a similar setup. I would be glad to install beta versions.

[javila]

"...in the meantime, you are actually able to run the 5.2.2 driver with WinGate 5.2.3 as well."

Adrien

Hi, how is that possible? installing 5.2.2 and upgrading to 5.2.3?
Thanks.

Javier A.

[javila]

"...in the meantime, you are actually able to run the 5.2.2 driver with WinGate 5.2.3 as well."

Adrien

Hi, how is that possible? installing 5.2.2 and upgrading to 5.2.3?
Thanks.

Javier A.

[Pascal]

You can run the install with a /X option specified. This allows you to extract files, and you should then be able to extract the driver. If that does not work, install 5.2.2 and copy the driver to another folder, then upgrade to 5.2.3 and replace the driver it upgraded with the one you copied out.

Depending on your operating system, you might be using a different driver.

95 - qbikhk95.vxd
98 - qbikhk98.vxd
me - qbikhkme.vxd
nt - qbikhknt.sys
2k - qbikhk2k.sys
xp - qbikhkxp.sys
2003 - qbikhkxp.sys

[sietze]

FYI:

According to your release notes: "Fixed a BSOD in the driver that could be triggered by some versions of Realtek network cards".

The external card on this box has a Realtek 8029 AS chip. But WG 5.2.2 works for me. WG 5.2.3 doesn't. But perhaps this prob regarding NAT checksum errors is related to this modification in the driver?

[javila]

I am using 2 realtek cards:
pc-to-adsl-router (the router feateure it is disabeled) rtl 8029 A type
pc-to-intranet rtl 8039D type
Hope this could help to solve anything.

Javier A.

[sietze]

Hope this helps:

I've changed the configuration so the Realtek 2029AS now is the internal NIC. WG 5.2.2 still working without probs, no BSOD nor anything.

WG 5.2.3 now communicates without probs with the Internet. eg nslookup talks to external name servers. But now the probs are at the internal interface. And it is not only ENS. The worksation on the inside is unable to talk DHCP to WG. And the checksum errors are there again in the NAT log. As soon as I unload WG everything is working fine again.

I've downloaded the most recent driver from Realtek (july 2003) to use it instead of the default Microsoft driver. Same probs.

I looked into this Realtek issue because at least one other post mentioned Realtek. There definetely is a compatibility issue between the WG 5.2.3. driver and Realtek. it would be interesting to now how many of the probs in this forum are Realtek related.

Realtek is used widely and has proven to be reliable so imho it is worth sorting out this incompatibility.

[sietze]

No probs with Realtek RTL8139(A), so the incompatibility might be limited to the older Realtek 80-series.

Of course those old 10 mbps cards we have lying about are very nice for converting all those old laid of PC's in firewalls.

[aggarwal_ravi]

i have window 2000 profeesional. but when i load wingate 5.0 and restart
machine, it will show blue screen with error qbikhk2k.sys?

please help me. what can i do?

thankx

[aggarwal_ravi]

You can run the install with a /X option specified. This allows you to extract files, and you should then be able to extract the driver. If that does not work, install 5.2.2 and copy the driver to another folder, then upgrade to 5.2.3 and replace the driver it upgraded with the one you copied out.

Depending on your operating system, you might be using a different driver.

95 - qbikhk95.vxd
98 - qbikhk98.vxd
me - qbikhkme.vxd
nt - qbikhknt.sys
2k - qbikhk2k.sys
xp - qbikhkxp.sys
2003 - qbikhkxp.sys

[Nev]

i have window 2000 profeesional. but when i load wingate 5.0 and restart
machine, it will show blue screen with error qbikhk2k.sys?

please help me. what can i do?

thankx

Try installing the latest version, Wingate 6.2.1

http://www.wingate.com/download.php

With these amazing improvements to the version you are using;

http://forums.qbik.com/viewtopic.php?t=4215