Discussion Locked

VPN-same subnet local & remote networks

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Our office uses a Cisco PIX for firewall/VPN. Local subnet is 10.0.0.0/24. Director just got a wireless card for his laptop, but is having problems accessing the network through the VPN at some hotspots. I just took the laptop out today to test, and found that the wireless network is assigning an IP of 10.0.0.26/24. Other than re-doing our entire network IP scheme, anyone know any tricks that would allow access to systems on our local 10.0.0.X network in this situation?

3 replies

by kevin.square

are you sure the remote network is assigning the address. If you internally use dhcp and have a long lease time the machine may not be asking for an address on the remote network. So ipconfig /release and ipconfig /renew might be worth a try.

2nd, don't know if you can do this on PIX but on Cisco VPN Concentrator there is an option for Split Tunnelling. eg. whether all traffic goes through tunnel or just some stuff.
On the concentrator I'd set to disallow split tunnelling which forces all traffic through the vpn when the tunnel is active. Then maybe the 10. stuff would have not choice but to go through the tunnel.

by grbeckmeyer

No, we don't even have a WAP, so it's not getting anything from here, and I know it's connected OK at the location because browser is initially redirected to a page for the location. Split Tunnelling is not turned on. Not sure if something at our office side would help anyway, as the when the laptop at the remote network tries to connect to 10.0.0.x, the gateway on the remote network is going to think that request is local and doesn't need to go out. Maybe if the PIX could assign a different subnet for the VPN connection and provide the route to connect that to our local 10.0.0.x

This discussion is closed to new replies.