1

I have created a VPN connection in Windows using the New Network Connection wizard that comes with Windows.

It works without problems in most places, but there is one concrete place where, despite the connection to the remote public IP works fine, it is not able to validate the login/password and establish the VPN connection.

In this place, the network is 10.0.0.x (the same I use in other places where I am able to connect). The remote network is 192.168.x.x, so I suspect there is some kind of IP collision, because before connecting, a traceroute to i.e. 192.168.0.40 does not fail.

  1     4 ms     1 ms     1 ms  LINKSYS [10.0.0.1]
  2     5 ms     1 ms     1 ms  172.26.27.1
  3     4 ms     5 ms     3 ms  192.168.1.100
  ... (more)

I can't modify the local network further than the first router (10.0.0.1).

That is the only different I've found so far. Any idea about how to solve it? Thank you.

3
  • You've got a bunch of private address spaces listed there - how about telling us all of the ipaddresses? What's the source local ip-address, what public (fully routeable, unlike the ranges you list above) addresses (if any) connect these private networks. Sounds like you have multiple sub-networks with duplicate addresses too, do you?
    – Helvick
    Feb 15, 2010 at 19:54
  • Reminds of my apartment's free wi-fi. Linksys in each apartment (10.0.0.x), then a Netgear that those are all connected to (172.26.x.x), and then the ISP router those are connected to (192.168.1.100). Triple NAT!
    – Bert
    Apr 2, 2014 at 13:51
  • What error would appear when it tried to authenticate? The error code might be a clue. Jun 5, 2014 at 6:34

2 Answers 2

1

Not doable. Simple like that. You can not route the same IP-Addresses. Fundamental issue - that should have been coordinated. This is why IPV6 has a new mechanism for determining your private address space to use.

In IPV4 private means private - the moment you couple multiple company networks it is not private anymore. If a colission occurs, you can:

  • Ignore it (the local space is not reachable by remote, but that may not be relevant, depending on what machines are there).
  • Coordinate (one must change) or
  • not use private addresses as they obviously are not in private use.

There is nothing else you CAN do.

0

I don't know what an IP collision is, but I suspect that the router at the network that doesn't work is blocking the VPN connection. Does the router have a VPN passthrough option? If so, is it enabled?

5
  • By IP collision I mean that the remote network is using the same 192.168.x.x addresses that also exist in the local network. The first router that is what I can control is a Linksys WRT54G with DD-WRT, I'll try to find that VPN passthrough option, thanks.
    – Guido
    Feb 16, 2010 at 8:06
  • That's what I thought you meant, but your post said that one network is 10.0.0x and the other is 192.168.x.x, so there's no "collision". This is a pretty common problem when both networks are using the same subnet, but in your case they aren't.
    – joeqwerty
    Feb 16, 2010 at 12:38
  • Yes, but if you see the traceroute, there is an "underlying" 192.168.x.x network before trying to establish the VPN connection... Thank you for your answer.
    – Guido
    Feb 16, 2010 at 21:01
  • Yes, but that is part of your ISP's network and is not visible to the VPN client. If that were causing the problem, then half of the VPN connections in the world wouldn't work. The networks that the VPN connection transits have no bearing on the VPN connection itself. the VPN only knows about the local and remote networks and nothing about those networks in between.
    – joeqwerty
    Feb 16, 2010 at 21:29
  • VPN passthrough is enabled, I've installed ddwrt-vpn and enabled that option, with no success.
    – Guido
    Mar 26, 2010 at 19:17

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .