Here are a couple of bugs we have encountered in the wingate NAT.
We are using Wingate 6.0.4 on Windows XP Pro with an ADSL connection to the internet. The wingate PC has two NIC’s, one for the LAN and one for the ADSL router. The Network Connections in wingate have been set up correctly with the LAN NIC set to internal usage and the WAN NIC set to external usage.
We have no problems accessing most sites but we have encountered a few exceptions. Both of the bugs here have been reproduced on multiple client machines. I also tried installing a new server machine with a fresh install of Windows and wingate, but the problems still occurred.
1) Using NAT transparent redirect to the WWW/FTP services causes downloads to stall and fail from some sites.
We have found that when downloading reasonably large files (>20M) from a few sites that the download will often stall and never complete. This occurs when using NAT with the transparent redirection to the WWW and FTP service.
Disabling the transparent redirection solves the problem. Unfortunately this also disables the virus scanning as well so it is not an acceptable solution. When the problem occurs I notice that the connection disappears from the gatekeeper status screen. The web browser download eventually fails with the error message "connection reset" or something similar.
Disabling virus scanning and caching has no effect, if transparent redirection is enabled then downloads will still stall. Note that this only happens on a few sites, although I have had it happen on download.com and even when using windows update. It is a very random event.
Downloading locally from the wingate machine (bypassing wingate entirely) also solves the problem, the downloads always complete.
Setting the web browser on the client machines to use SOCKS to connect to wingate avoids the bug. The download completes without problem. Note that transparent redirection is enabled on the SOCKS connection as well, but luckily it does not encounter the bug, The bug only manifests on NAT connections to wingate.
This is the solution we are now using as it still allows virus scanning to be performed. It is not convenient to make all client machines use SOCKS however (laptops for example) and some users still experience the problem occasionally.
2) Wingate prevents secure web pages from loading on some sites.
I suspect that this problem is also caused by the wingate NAT being active. We have encountered this problem when using the Inland Revenue (NZ) web site to enter data, after entering data into the page and clicking the save button the next web page fails to load.
The site is https://ir-file.ird.govt.nz
When directly connected to the internet (I connected a laptop to the ADSL router) the pages load without problem.
When I try to access the site from the wingate PC itself, the pages still fail to load. After I shut down the wingate server I can load the pages without problem (browser running on the wingate PC).
This is strange as wingate should have no affect on the browser running on the wingate PC itself! The browser does not have any proxy settings, it goes directly out through the ADSL router. Yet the wingate server is interfering with the traffic.
I have found no way to work around this problem and so the site cannot be used from our LAN. This is an important issue as it pertains to the running of the company. For now I have arranged alternative internet access (without wingate) for the affected user.
I would appreciate any feedback you have on the status of these bugs, are they known problems? Please note that I have spent a lot of time isolating and confirming these problems, even so far as installing a second machine with a fresh wingate and windows installation.
Thanks for any help