In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
VPN: 2 network with same IP scheme problem
We have a windows 2008 server, running as DC/DNS/DHCP,etc. I setup the VPN on it, i don't have problem establish the connection on the client workstation. But the problem is sometimes I cannot use the \\servername, even I try the \\server_IP. When I ping it replies though.
i noticed that the 2 network use same IP scheme as 192.168.1.x, is this causing the problem? why? if that's the case, then I think it's not practical, as how can we expect the network that client at all use different IP scheme, like in hotel, airport, cafe, etc
i noticed that the 2 network use same IP scheme as 192.168.1.x, is this causing the problem? why? if that's the case, then I think it's not practical, as how can we expect the network that client at all use different IP scheme, like in hotel, airport, cafe, etc
Asked:
3-
3
- +1
1 Solution
I don't have any issue if I am on different subnet. So do you know how can I setup tunnel all in windows 2008? When I first setup vpn client, in tcp/ip setting, by default it is "Use default gateway on remote network"..... this is not tunnel all? as they will pass through the remote network to go to internet though....
Yes, checking that box does mean tunnel all. it means all the resources on the local network are not accessible and traffic is sent through the vpn connection.
my expectation is that if you are on an identical network, then tunnel all should work. if it's not, then changing the IP subnet for your remote clients get is the next option and, quite possibly, your only option.
my expectation is that if you are on an identical network, then tunnel all should work. if it's not, then changing the IP subnet for your remote clients get is the next option and, quite possibly, your only option.
it seems the tunnel all working for me, if i am on different subnet, there is no issue.... there is no other solution?
if tunnel all doesn't work with duplicate subnets, then you need to change the subnet for you remote users. sorry.
if you believe another answer exists, then try clicking the request attention link in your question. request a mod to adjust your zones and send a request for other experts to review your question. either you'll get an answer that you like or one that supports mine. i know i'd want a second opinion.
if you believe another answer exists, then try clicking the request attention link in your question. request a mod to adjust your zones and send a request for other experts to review your question. either you'll get an answer that you like or one that supports mine. i know i'd want a second opinion.
You have to change remote site IP range....
Otherwise, you can route specific ip (or small ip ranges) to remote sites (to access specific servers for example) but after a few sites, it will be unmanageable!
Otherwise, you can route specific ip (or small ip ranges) to remote sites (to access specific servers for example) but after a few sites, it will be unmanageable!
Thank you. as digitap mentioned some vpn server can do tunnel all. windows 2008 vpn server cannot handle that? It seems on the vpn client, by default it direct all traffic, but it doesn't help.
As has been said already - VPNs (of all kind) work only reliable if the subnets are different. Anything else depends on how the VPN client manages traffic. "Tunnel All" can be used only with a few VPN Clients, like Checkpoint, Nortel or Cisco. MS VPN (PPTP) is not able to do that.
With MS VPN and conflicting subnets - and NOT having set "Use default gateway on remote network" - whether you have access to the remote network or the local network is not predictable.
With "Use default gateway" many entries have precedence over the local ones, including DNS and routes. It is not "Tunnel all", which forces all traffic to go thru VPN without exception, though.
The way ampranti described (using more specific routes for the remote network) is working best. E.g. if you need access to only three specific machines, say 192.168.1.3, .5, .7, you can create routes to those. However, it is not easy to do that, and you need to apply the routes on each connect - with a probably changing interface or gateway address, which makes things even more complicated. If you are interested, we can work on that.
With MS VPN and conflicting subnets - and NOT having set "Use default gateway on remote network" - whether you have access to the remote network or the local network is not predictable.
With "Use default gateway" many entries have precedence over the local ones, including DNS and routes. It is not "Tunnel all", which forces all traffic to go thru VPN without exception, though.
The way ampranti described (using more specific routes for the remote network) is working best. E.g. if you need access to only three specific machines, say 192.168.1.3, .5, .7, you can create routes to those. However, it is not easy to do that, and you need to apply the routes on each connect - with a probably changing interface or gateway address, which makes things even more complicated. If you are interested, we can work on that.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
how some company's get around that is to do what's called tunnel all rather than split tunneling. split tunneling says that your remote users has access to resources on the local network AND the remote network. what this usually amounts to is they access the vpn to access intra-network resources and use the local network to get to the internet. if you "tunnel all" then they only have access to resources on the intra-network and that's it. they'd have to disconnect from the vpn to access the internet. there is a way that you can get internet access over the vpn as well, but i'm not familiar with how to do that on a 2008 vpn server...only a sonicwall appliance.
tunnel all would force all the traffic to go over the VPN regardless of the local subnet. this would almost certainly resolve the issue you are seeing, unless it's a DNS issue. do you see the same issue when the subnet is different?
in your case of resolving the server name, it may be more of an issue with DNS. are you passing an internal DNS server to the IP settings of the vpn client? if not, then it's probably not going to resolve the server name. of course, it could be that the subnet is the same and is trying to resolve the name on a local DNS server which wouldn't know anything about your server.