Switch to full style
Forum for all technical support and trouble shooting of the WinGate VPN.
Post a reply

VPN published routes: ignored / in conflict

Nov 09 04 1:42 pm

Following my other post, I now have the "ignored / in conflict" msg in the VPN routes. I have read the help file and posts on this issue though they don't directly help me to solve the problem.

1. Remote Networks (VPN):

Published routes:
* ignored / local conflict 255.255.255.0 / 192.168.0.0
* in conflict 255.255.255.255 / 192.168.0.1


2. "ipconfig" on my local PC gives:

Ethernet adapter LAN:

IP address : 192.168.0.2
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.0.1

I assume that I need to change my LAN to 192.168.1.* ? If so, which should I change, the IP address or the Default Gateway? Should both be the same number?

Would appreciate your feedback. Thanks.

Nov 09 04 2:33 pm

Both networks are on the same subnet. That will definately cause conflicts between the routes, as the VPN cannot decide which end of the VPN owns "192.168.0.1" when both networks are "192.168.0.x"

The easiest to do is to change the joiner (As those are often restricted to one computer / laptop) by shifting it to a different subnet. This involves changing the ip address of that machine as well as others on the same local area network so they can still see eachother. Depending on how you connect out you might need to adjust the private (LAN Side) IP of your router, in which case you would need to adjust the default gateway of the computers as well.

For example, my network at home is 192.168.13.x. My main machine is 192.168.13.2, my wife's is 192.168.13.3, my laptop is 192.168.13.4.
The Internal IP of my ADSL router is 192.168.13.1 and this is the default gateway for my home network.

If I were to change my network to "192.168.1.x" I'd change the IP Address on my router. Then, I'd set their default gateways to the router and change their IPs to the new subnet.

Normally, this type of change is easily accomplished if you're using DHCP.

Nov 09 04 2:39 pm

You typed the in-conflict routes as:

* ignored / local conflict 255.255.255.0 / 192.168.0.0
* in conflict 255.255.255.255 / 192.168.0.1

Is it shown that way in GateKeeper? (I.e. is the mask/ip address reversed like that?)

If that is the case:

* Which Operating System + Service Pack do you have installed?
* Do you use a different language version of Windows? (One that might support right-to-left reading, etc.?)
* Are you using the same version of WinGate VPN on both ends?

Nov 10 04 12:25 am

Here are answers to your second post today:

Is it shown that way in GateKeeper? (I.e. is the mask/ip address reversed like that?)
Yes, exactly like that. I double-checked.

* Which Operating System + Service Pack do you have installed?
Win XP Professional, English, with SP2. DEP switched off.

* Do you use a different language version of Windows? (One that might support right-to-left reading, etc.?)
It's the English version but enabled for East-Asian languages, as I am in Japan. Not enabled for right-to-left script, nor is it the multi-language language version of Windows.

* Are you using the same version of WinGate VPN on both ends?
No. The company GateKeeper is on v6.0.0 and I am on 6.0.3 or 2.0.3. I get the following msg when clicking Help-Click Version in GK:

"You are not running the current version of WinGate VPN.
Thank you for choosing to use our products. Your system reports that you are running version 6.0.3. However the current version is WinGate VPN 2.0.3"

Whatever the case, I installed using file called VPNOnly2.0.3-1005-USE. The install log text file also shows 2.0.3.

I should add that RIP2 is enabled for my home VPN; don't know about the company VPN.

Over to you...

Nov 10 04 8:45 am

den04 wrote:Which Operating System + Service Pack do you have installed?
Win XP Professional, English, with SP2. DEP switched off.


We'd just gotten here because it was a DEP problem. I must have been having a mad day to have asked that again :)

Anyway, thanks for the headsup on the installation. We've seen the display appear like that once before but haven't been able to work out why; which is why I was so curious. Will investigate now with East-Asian language support installed.

Did you manage to get the routes in conflict problem resolved?

Nov 10 04 12:19 pm

I messed about with the routes a bit but lost connection completely. The posts on the forum often answer the 'why' but I need the precise 'how to' as I am not good at networking technology.

"Depending on how you connect out you might need to adjust the private (LAN Side) IP of your router, in which case you would need to adjust the default gateway of the computers as well."
At home I have single machine and connection is a WAN miniport (PPPeE) via a fibre connection. Not ASDL.

"joiner" - not familiar with this terminology.

Question:
Should I change the properties of the Internet Protocol of my LAN connection? The default gateway which you mention is there. Right now I obtain the IP and DNS server addresses automatically. If that's the right dialog box, please let me know the 5 numbers I should enter.

Nov 10 04 12:38 pm

The "Joiner" is the machine that will be connecting IN to the VPN; most likely your home computer in this case.

I assume you are at your home machine now, the one that has:

den04 wrote:IP address : 192.168.0.2
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.0.1


as it's settings? If that is the case; do you have the ability to change the ip address of your default gateway? (On the device itself?) Can you change that from 192.168.0.1 to 192.168.1.1?

NOTE: That's not the entry for a default gateway on your local computer; it's on the physical method/device you use to connect to the Internet.

(I'll monitor this post - otherwise, if you are online now, we could move this to email and simply post results back here - might be faster - my email is pascalv at qbik . com )
Post a reply