ENS/NAT quit working w/ cable modem

[winstonk]

Help!

Today, I upgraded to 5.2.3 from 5.2.2; but now the ENS/NAT doesn't seem to function properly with my cable modem. In addition, as soon as I start Wingate, even internet connections from the wingate server macihine no longer work with the cable interface, so the problem seems to occur before the NAT port translation step. However, as soon as I stop wingate, the cable modem connection starts working again on the wingate server. If I make a PPP/Modem connection to the internet, then everything works fine--both on my client machines and the wingate server. The symptom using the cable interface is that I can send to the internet but can't receive. The activity and history screens show successful DNS searches and connections to remote machines, but no response is ever received and the connection finally times-out. I can ping Time Warner's cable gateway and DNS servers that show with IPCONFIG /ALL. The routing tables look normal to me, with the cable modem's DHCP-set addresses all being added to the routing table as expected. The Wingate DHCP server is disabled as well as all of the proxy servers (as before). The Ethernet adapter used with the cable modem is set-up for DHCP, and the adapter used for connection to the LAN uses a fixed IP address--as do all of the client machines. It was all working great until the upgrade, so "something" seems to have gone awry. As you can imagine, going back to 56KB from 2MB is pretty distressful, so hopefully there is a simple solution that I'm overlooking. I've spent about 8 hours so far troubleshooting this without any results, so any suggestions/comments will be appreciated!

Thanks,

Winston Kriger

[sietze]

Me have same problem.

Logs are clean but the NAT log:

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

[winstonk]

Following-up on my original post, after spending another day trying everything I could imagine to resolve the 5.2.3 ENS/NAT problem, I back-dated to release 5.2.2, with the same settings as that used in my last attempt to get 5.2.3 working (did not do "uninstall). As a result, I'm back in business with my cable-modem adapter (whew!). Some of the dialer fixes in 5.2.3 looked like they might solve some long-standing issues in that area; but if I can't use my "broadband" adapter, then I'll just have to wait for the next update to gain those and other benefits. Luckily, I still had the "wgsetup.exe" file for 5.2.2 on a backup tape. Otherwise, I'd have been up the proverbial "s@#t creek without a paddle".

A suggestion for Qbik support: Please keep previous releases available for download and publish how to access the "archives". I tried logging-in to "www334.pair.com" using ftp "anonymous" login, but the home directory there had only a welcome message and no files in the "pub" subdirectory. Security prevented any further "hunting" by user "anonymous". Presumabably Qbik has a download directory somewhere on that machine--since that's where 5.2.3 came from. Anyway, I was greatly relieved to find 5.2.2 on the backup media...

Cheerio,

Winston Kriger

[sietze]

The request for keeping previous releases available is seconded by me.
Some other companies do.

I know that before upgrading a backup should be made and that the original install sets should be lying next to the server. But I am new to WinGate. I only joined the WinGate effort 2 weeks ago. No local archive yet.

It doesn't happen to often that one has to downgrade, but when it happens it is urgent. As an authorized reseller I asked the reseller department to provide me with WG 5.2.2 (after reading in these forums that some people had sorted out their problem this way), but to no avail. Instead I had to get it elsewhere.

I do not think that it is in Qbik's interest that we have to wander down the winding paths of the dark Russian woods were wolves and hackers lurk.

[winstonk]

Has this (apparantly) DNS related problem introduced in 5.2.3 been identified/fixed in the 6.X release. I can't afford the time and misery of going through another "upgrade" if this hasn't been positively fixed. There were numerous other users who experienced the same problem, but I can't find anything in the forum that documents a solution. I had to revert to 5.2.2 as did many others who encountered this "glitch".

Thanks,

Winston Kriger
-------------------------------------------------------------------------------

Help!

Today, I upgraded to 5.2.3 from 5.2.2; but now the ENS/NAT doesn't seem to function properly with my cable modem. In addition, as soon as I start Wingate, even internet connections from the wingate server macihine no longer work with the cable interface, so the problem seems to occur before the NAT port translation step. However, as soon as I stop wingate, the cable modem connection starts working again on the wingate server. If I make a PPP/Modem connection to the internet, then everything works fine--both on my client machines and the wingate server. The symptom using the cable interface is that I can send to the internet but can't receive. The activity and history screens show successful DNS searches and connections to remote machines, but no response is ever received and the connection finally times-out. I can ping Time Warner's cable gateway and DNS servers that show with IPCONFIG /ALL. The routing tables look normal to me, with the cable modem's DHCP-set addresses all being added to the routing table as expected. The Wingate DHCP server is disabled as well as all of the proxy servers (as before). The Ethernet adapter used with the cable modem is set-up for DHCP, and the adapter used for connection to the LAN uses a fixed IP address--as do all of the client machines. It was all working great until the upgrade, so "something" seems to have gone awry. As you can imagine, going back to 56KB from 2MB is pretty distressful, so hopefully there is a simple solution that I'm overlooking. I've spent about 8 hours so far troubleshooting this without any results, so any suggestions/comments will be appreciated!

Thanks,

Winston Kriger

[adrien]

Hi

The archive of old versions is available at

http://www334.pair.com/qbiknz/archive

Because of security issues with the licensing system for this version (i.e. crack generators abound), we don't publish this link prominently.

On the second issue, without exactly identifying the problem that you had in WinGate 5.2.3 when you upgraded, it is difficult to guarantee that there would be no problems in WinGate 6.0.3, however this forum has been suspiciously silent on any DNS issues for a while now, so we believe we have fixed them all.

Adrien