Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I've got a new 5505, and I've run through two wizards: one to start up, one to add client VPN. As a result, I can now connect from a client, the client gets the right info (ip adress, dns, gateway), but it cannot connect to any of the servers on...
Before the client connects:Result of the command: "show crypto ipsec sa"There are no ipsec sasAfter the client connects:Result of the command: "show crypto ipsec sa"The command has been sent to the device(and no further output)Contact me off the mail...
Yes they are connected the network on the "inside" interface - and they can reach each other, so firewalls aren't an issue there. They can also reach the asa, and the asa can reach them.
I did that through the cli, saw no difference in client behaviour.The weird thing is that if I compare the running-config after that cli command with the asaconfig3.txt file linked earlier, there's no difference at all.
Just did all three things in the cli, as can be seen at http://www.dubbele.com/asaconfig3.txt.No change - the client gets 10.0.0.10, default gateway 10.0.0.1 (which it cannot ping), and it fails to reach 192.168.6.x(oh, and by the way: thank you for ...
Here's what I did: I gave the outbound interface the ip address it is going to get when I move it to the datacenter, and gave a laptop an address in the same class C for testing. I removed one of the policies (rotterdam) and moved haarlem to 10.0.0.0...
