I installed Wingate VPN on another laptop, trial license. This one has Windows Firewall running (the other systems I had installed on used NIS and experienced no problem with it).
The VPN connection works fine IF Windows Firewall is disabled, but then Windows firewall complains and wants to be turned back on. There are two (?) Wingate related entries in the Windows Firewall exception program list, one of which is checked and one not. Both of these entries point to a (different) path in the C:\Documents and Settings\Username\... tree. It looks to me as if the VPN installation somehow tried to set up an exception in Windows Firewall but got it wrong. The installation was run off the internet directly, i.e. the download of the VPN installer went into the user's temp folder and ran from there, and this is where one of the paths for the exception points. So, perhaps there is a problem with installing this way (that's for you to figure out if you want):>
Back to the immediate problem; I have two questions:
1) Is there a way for Windows Firewall to be "aware" of the Wingate firewall instance and thus be set not to "complain" that it (Windows Firewall) is not active? (As NIS will do)
or
2) What are the correct settings for the exception entry (I assume there should be just one) for Wingate VPN? Shouldn't the path be c:\program files\wingate\wingate.exe ? And, are there any additional changes to either the scope of the program exception, for specific ports, or for the network connection? If I would guess, I would open port 809 for incoming UDP packets.
Thanks again for your assistance,
DJ