Thanks for the feedback. I am sure it will help. Sorry if it was not clear. You are correct, your router should point to the internet router on your LAN.

Josh

ie. ip route 0.0.0.0 0.0.0.0 192.168.1.1

This allowed my virtual machines to get to the Internet.

Thanks for the videos, they’re a huge help.

This tutorial is not really what you are looking for. This one helps you build a lab on your PC.

You probably want to take a look at these tutorials:

http://www.blindhog.net/cisco-how-to-configure-an-ipsec-vpn/

http://www.blindhog.net/cisco-how-to-configure-nat-for-an-ipsec-vpn/

http://www.blindhog.net/how-to-configure-a-greipsec-vpn-part-1/
http://www.blindhog.net/how-to-configure-a-greipsec-vpn-part-2/

Josh

If so, this is great. I’d like to get my satellite offices tied directly into our home office, but didn’t feel like buying all those Terminal Server CALs (they add up quickly). As a result, remote computers have to VPN into the home office. I’d rather just have all employees logged directly into the domain.

In effect, I can have my routers at remote locations talk to each other as if they were on the same network? Would they also be able to access the internet through their own local ISP connection? Or would they access the internet using the home office’s connection as a proxy?

Please let me know if I’m interpreting all of this correctly.

Great tutorial.

Thanks – Al

Try right clicking on the .bat file and run it as administrator.

Josh