Thank You soo much,
That sounds like a very reasonable route to take!
I'm going to buy a replacement asa-5505 to play with as I don't like the idea of playing on production hardware, at least that way I can always swap out the original ASA without worrying about messing anything up.
I will put...
Even IF this is a "route based" VPN connection that can only be reached from the office's public static IP address -- the ability to move the VPN configuration from the ASA-5505 to the individual machines & configure reach individual desktop to connect to the VPN and remove the VPN/Cisco router...
We have no ability to serve anything to the public world/wan/internet or reach any of our machines that live behind this ASA from outside of the office because of the way that this is all set-up, and we need to do so, we plan on serving a few public resources from this location in the very near...
I understand what you mean, that if it's route based it's looking for a particular peer -- as in, it's only going to accept a connection from the public ip address at the office even if I have the pre-shared key.
If this is the case -- the cisco asa-5505 has a VPN "client" configured to connect...
Hello!
So I'm not daft here, but I'm not a "cisco guy". I've been hired on by a small business to help them out a bit.
They have a pretty particular network setup that involves a Cisco ASA-5505 acting as a router that establishes an IPSec/L2L VPN tunnel to a data center. From what I can see...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.