11-18-2005 11:15 AM - edited 02-21-2020 02:06 PM
I am new to vpn configuration and have set up a small vpn test network. I have a small "corporate" netork that my PC's can log into with no problems and then I have an internal protected network that I vpn into to access sensitive data. My VPN connects without a problem but I cannot route/connect to anything on the backside of the VPN router. I have used the sample configs provided in the Cisco documents relating to VPN Client to Cisco Router connections. I am using VPN client 4.7, aaa local authentication, and pre-shared keys. My client will grab an address from the VPN router no problem. I have attachted a diagram of my network and my router configs.
11-18-2005 04:05 PM
just a quick comment.
the vpn client pool should not be overlapped with the private net or any net connected.
11-18-2005 08:51 PM
Can you change the default route to the public side instead of pvt side. You can add Specfic routes to the Pvt segment if needed
ip route 0.0.0.0 0.0.0.0 192.168.40.1
11-21-2005 01:41 PM
I rebuilt the network using the 10.0.0.0 space for my network and using 192.168.0.0 space for the VPN pools and it works like a charm.
Thanks all
11-21-2005 06:39 PM
it's good to learn that your issue has been resolved.
according to cisco:
Why should I rate posts?
If you see a post that you think deserves recognition, please take a moment to rate it.
You'll be helping yourself and others to quickly identify useful content -- as determined by members. And you'll be ensuring that people who generously share their expertise are properly acknowledged. As posts are rated, the value of those ratings are accumulated as "points" and summarized on the Member Profile page and on each member's Preferences page.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide