Wingate, Windows XP SP2 and default gateway problems
Jun 08 07 9:51 am
HI.
I am a user of Wingate 6.2.5 and now running the software on Windows XP SP2. Before running it on XP SP2 the program was running on Windows 2000, during this period the program was running fine. I am currently running the program on XP SP2 and I am having a default gateway problem. Since the change my sever has been issuing a default gateway 192.168.0.2 however when it was installed on 2000 SP4 the gateway was 192.168.0.1, the users on my LAN's services are configured to the gateway 192.168.0.1 and occassionally Wingate changes the gateway to 192.168.0.2, therefore hosts on my network are frequently faced with problems pertaining to browsing and network connections. Wingate is set to issue the IP addresses because we have set it as our DHCP server.
I would like to know why I am faced with this problem, and how can I correct it.
reply is URGENT....thanks
KurKem
I am a user of Wingate 6.2.5 and now running the software on Windows XP SP2. Before running it on XP SP2 the program was running on Windows 2000, during this period the program was running fine. I am currently running the program on XP SP2 and I am having a default gateway problem. Since the change my sever has been issuing a default gateway 192.168.0.2 however when it was installed on 2000 SP4 the gateway was 192.168.0.1, the users on my LAN's services are configured to the gateway 192.168.0.1 and occassionally Wingate changes the gateway to 192.168.0.2, therefore hosts on my network are frequently faced with problems pertaining to browsing and network connections. Wingate is set to issue the IP addresses because we have set it as our DHCP server.
I would like to know why I am faced with this problem, and how can I correct it.
reply is URGENT....thanks
KurKem
Jun 11 07 10:56 pm
Also logged a support ticket at a similar time - Current Status:
Thanks for the details. I was hoping to also see a client ipconfig/all and an explanation of what 192.168.0.2 is. But this is what I can see at the moment.
1. Definitely no 192.168.0.2 configured in the WinGate servers ipconfig/all or route print - hence DHCP should not automatically allocate that gateway.
2. ipconfig/all and Internal/External markings in WinGate good.
What to do from here:
a) Investigate your settings in the WinGate DHCP Server. In particular take note of the Router option. e.g. GateKeeper --> DHCP Server --> DHCP Settings --> Your Scope --> Options --> Router.
b) If the VPN option is visible in WinGate, then please try disabling the RIP2 Listener; it may be automatically picking up a route from a misconfigured device on the network. The location is shown in the image attached.
c) On a computer that gets the 192.168.0.2 gateway, do an ipconfig/all and see what the ip address of the DHCP server is; it may be someone has installed a DHCP Server on 192.168.0.2.
d) As a temporary solution, you could make sure no device/computer is using the 192.168.0.2 address, and then add it onto the WinGate servers internal adapter - hence when a computer get the .0.2 gateway, it will not disturb network operations while investigating this problem.
If you need more assistance I will need the following info:
i) ipconfig/all from a LAN Client.
ii) What device/computer has the address 192.168.0.2
iii) The WinGate registry.
GateKeeper --> Options menu --> Save Registry Settings.
Thanks for the details. I was hoping to also see a client ipconfig/all and an explanation of what 192.168.0.2 is. But this is what I can see at the moment.
1. Definitely no 192.168.0.2 configured in the WinGate servers ipconfig/all or route print - hence DHCP should not automatically allocate that gateway.
2. ipconfig/all and Internal/External markings in WinGate good.
What to do from here:
a) Investigate your settings in the WinGate DHCP Server. In particular take note of the Router option. e.g. GateKeeper --> DHCP Server --> DHCP Settings --> Your Scope --> Options --> Router.
b) If the VPN option is visible in WinGate, then please try disabling the RIP2 Listener; it may be automatically picking up a route from a misconfigured device on the network. The location is shown in the image attached.
c) On a computer that gets the 192.168.0.2 gateway, do an ipconfig/all and see what the ip address of the DHCP server is; it may be someone has installed a DHCP Server on 192.168.0.2.
d) As a temporary solution, you could make sure no device/computer is using the 192.168.0.2 address, and then add it onto the WinGate servers internal adapter - hence when a computer get the .0.2 gateway, it will not disturb network operations while investigating this problem.
If you need more assistance I will need the following info:
i) ipconfig/all from a LAN Client.
ii) What device/computer has the address 192.168.0.2
iii) The WinGate registry.
GateKeeper --> Options menu --> Save Registry Settings.
Jun 11 07 10:58 pm
*Attached
