Post WinGate 6.6.4 upgrade NAT issue

[geoffmgreen]

Hi.

After downloading and upgrading to WinGate 6.6.4 (Build 1338) on W2k3 server, every morning NAT ceases to work; the explict proxy in IE LAN settings will push traffic out dual NIC server no problem (but very few clients use that method).

If I start and stop the Wingate services (engine) voila NAT (I imagine ENS faeture) works fine for next day.

Any ideas appreciated.

Internal NIC: 10.10.10.4
DNS: 10.10.10.4

All clients XP Pro

External NIC: 192.168.168.2

No other issues reported.

Enabled NAT, WWW proxy logging.

By the way is there a Wingate service i can start /stop via a command line script so I do not have to wake up early and stop/ start engine manually.

Nothing special running I can see.

Thanks.

[genie]

Does the NAT functionality restores itself when you restart engine only without rebooting the machine?

[geoffmgreen]

Definitely by NOT rebooting server and just stopping/ starting WG engine.

Not 100% if NAT/ ENS starts working just by reboot but pretty sure does judging from NAT log.

Other twist: if I remote in using registry edited port 3390 for RDP stopping WG service now kills all network connectivity on LAN and public?

Thanks.

[genie]

A couple of questions to understand your setup properly:

Is this ENS traffic redirected to your WWW proxy (TR)?
When the problem happens do you still see those NAT sessions in Gatekeeper?
What kind of memory usage (VM size) does Wingate experience when the problem happens?

[Nev]

Other twist: if I remote in using registry edited port 3390 for RDP stopping WG service now kills all network connectivity on LAN and public?

Thanks.

Yes that is normal for RDP because either Wingate is handling the session via NAT or 'Protect my server at boot' is in play.

Other VPN's are not similarly effected.