Windows NT server/5.22 NAT problem

[snake]

Hello,

Summary: NAT fails completely after upgrade from 5.0.1 to 5.2.2. After uninstalling and restoring 5.0.1 with original registry settings applied (wisely exported beforehand), everything returns to normal. More concise details follow:

This system is the main gateway for a WISP in the Middle East:

NT 4.0 server, SP6, running Wingate 5.0.1 Enterprise edition, with Wingate HTTP, FTP, and SOCKS proxies, DHCP and remote control services. Extended networking enabled for NAT (firewall disabled). All other services disabled.

Running Microsoft DNS, Imail server, Apache web server, and Guild FTP server. (Wingate's HTTP proxy is on port 8080 and the FTP proxy is on port 22).

Server configuration: Celeron 700MHz, 128MB RAM, single Realtek network adapter, with 3 IP addresses (1 public, 2 private, 10.1.1.1 & 10.2.2.1)

Clients on the wired LAN use DHCP with MAC address reservations, while clients on the wireless WAN use fixed IP addresses in the 10.* range on their NAT routers.

Using Wingate 5.0.1, everything works perfectly, except for a few niggling details. They are:

- Wingate fails to do DNS reverse lookups for NAT requests, and hence policies can't be enforced for NAT.

- When we implemented NAT we had to dramatically increase the NT server's virtual memory size to avoid frequent crashes.


HOWEVER, when we installed Wingate 5.2.2, NAT ceased to function. Everything else functioned normally, but NAT was broken, both for the fixed IPs and DHCP clients. We did as much fiddling as we had time for before customer complaints forced us to uninstall and restore the old configuration (which is functioning normally as before).

What gives? Possible compatibility problem with NT?

Regards,

[adrien]

Hi

From what we have been seeing from a couple of other people with similar problems, it seems to have something to do with how you connect to the Internet - particularly on PPPoE or satellite connections.

What sort of Internet connection are you using?

Adrien

[snake]

Hello,

The NT server has a public IP address which points to a Cisco 1601 router, which connects by serial port to an g.HDSL modem, connecting us via leased line to our provider.

Regards,