I have been using Wingate since Wingate 3.x and have been able to resolve all my issues without help, until lately. It has taken many hours to track down this problem.
The Wingate Server is running on a Windows 98SE with two NIC’s and is connected to the Internet through DSL using a CISCO 675 router from one of the NIC’s.
Everything has worked correctly through 5.0.7, but starting with 5.0.8 and up through 5.1 I have a problem where it changes the outgoing NIC IP address to one of it’s choosing after about 10 to 15 minutes of use. When this happens there is no outbound traffic to the Internet because it cannot find the gateway.
When Wingate is started I have the following IP addresses on my interfaces and looking in the Advanced Options Network tab in Wingate with the following network interface setting:
10.0.0.2 (defined by the CISCO router using Nat) public yes – trusted no
127.0.0.1 (Loop Back) public no – trusted yes
192.168.0.1 (Static IP address for network reasons) public no – trusted yes
169.254.160.132 (Assigned by Wingate???) public yes – trusted no
When the Extended Network Drivers are enabled and after about 10 to 15 minutes all Internet access is lost. The interface 10.0.0.2 has changed to 169.254.xxx.xxx. Stopping and restarting the Wingate engine does not resolve this issue. It requires a total re-boot of the computer to reset the IP address back to 10.0.0.2 and everything will work correctly for a short time.
This problem is occurring from either an upgrade of Wingate to the next version or a clean install.
I would really like to be able to use ENS for the firewall capability, but at the moment this is not possible because of this problem.
Got any ideas?