Wingate Update to 7.2.10.3486 has broken NAT

[andyv12]

After this update, the Wingate NAT has stopped working. My local Macintosh and Windows clients can't connect to the internet via NAT any longer. The only thing that works is to force them through a Proxy Service. But that's no good because there is no Proxy for some protocols we use, such as SFTP. I checked the Wingate NAT log, but there has been no log created since the day the update went into use. Can you help me please?

[andyv12]

Note that I am running Wingate on a dual-homed Windows Server 2008 R2 and the Windows Firewall is turned off on both Network interfaces (one NIC is connected to my trusted Internal network and the other to the public un-trusted External Internet - and configured as such in Wingate).

[adrien]

Hi Andy

please check in your network adapter properties to see if the WinGAte network driver is showing up there.

If not, click install, choose service, and you should see it. You'll need to reboot after this.

If WinGate Network driver is already showing (and enabled), or install fails, please get back to us.

Adrien

[andyv12]

Does the Wingate Network Driver get installed on both adapters (External network and Internal network)? Or only on the Internal Network adapter?

[adrien]

Hi

it needs to be on both adapters

Regards

Adrien

[andyv12]

Thanks Adrien! Great support! FYI, when I installed it on the Internal Adapter, it also installed on the External Adapter. After a reboot, NAT now appears to be allowing traffic to be bridged between Internal and External adapters as it should. What would have caused the Wingate Network Driver to fall off the Adapters?

[adrien]

Hi Andy

you're welcome.

unfortunately the only supported way to update LWF NDIS drivers (Light-Weight Filter - which is what our driver is), requires uninstalling it then reinstalling it.

Sometimes for some reason, the re-install doesn't complete properly.

It happens in only a small proportion of installs on Win7 / 2k8 sites so we have a hard time reproducing the problem let alone fixing it.

Regards

Adrien

[andyv12]

Gotcha. Thanks Adrien. Guess there's no good way of alerting users of this possibility given that the system uses Autoupdate to install patches. Back in the day, we'd install patches manually and there would be release notes that accompanied them warning of such a possibility, the symptoms, and quick fixes. I appreciate your responsiveness!