Hi,
i have a problem with Wingate 6 (current version) that drives me crazy ...
Wingate server is NT4.0 SP6, just one client (W2K SP4). Internetaccess is via dialup (AVM ISDN). Had Wingate 4 running on this server for a few years now (via proxy access) with no further problems. Just upgraded to Wingate 6 (wanting to use NAT), removed all proxy settings for the browser on server and client but internet access stopped working. Nameresolution is working fine, i can ping hosts by name on the internet without any problems. IE comes up, says "website found, connecting ..." and times out (page not found). Same with OE: can resolve the hostname but no access via pop.
This is what i tried so far:
- Upgrade of Wingate 4 to Wingate 6
- Complete uninstall and fresh install of Wingate 6
- Tried to use the proxies
- Tried to use WIC
- Left the firewall at it-s default values, put it on "medium", switched it off.
- Played with the advanced options (Recalculate TCP ... etc)
No success. The nat connection is shown in the activity pane, the firewall log only shows some blocked access from the outside on netbios borts (138, 445). There-s an option to keep Wingate-firewall running when wingate engine is shut down. If this option is UNchecked and i shut down wingate and fire up the connection manually IE works again on the server. If this option is checked and wingate is shut down IE shows the same problems: "website found ..." and times out. So it looks as if the firewall SHOULD have something to do with it ... Or maybe a low-level driver it loads.
Any ideas on this are really appreciated
Dirk