08-04-2007 12:09 PM - edited 02-21-2020 03:12 PM
I have an ASA 5510 that is an endpoint for two site to site VPN tunnels.
It is in our corporate office and I need to VPN to the ASA and be able to RDP to some servers. I can connect L2TP to ASA 5510 with Microsoft client on Windows XP workstation SP2. I cannot RDP to any servers though.And I can't ping any servers other than the GW [the inside interface of the ASA] Any help would be appreciated.
08-04-2007 01:14 PM
Hi, try to change your vpn pool to something that is not being used, for example:
ip local pool VPNpool 192.168.17.10-192.168.17.20 mask 255.255.255.255
And add it to the nonat access list:
access-list nonat extended permit ip 192.168.0.0 255.255.240.0 192.168.17.0 255.255.255.0
08-04-2007 01:39 PM
Thanks, it didn't work.
I still can't RDP or ping any servers once I'm connected.
08-04-2007 03:09 PM
Ok, it should probably work either way.
Can you show some info about the tunnel:
show vpn-sessiondb detail remote filter protocol L2TPOverIPSec
08-04-2007 03:26 PM
Here it is. I just connected from my WS with the VPN I setup and here is what I got:
FW2# show vpn-sessiondb detail remote filter protocol L2TPOverIPSec
INFO: There are presently no active sessions of the type specified
How can this be?
Thanks for you assistance.
08-04-2007 03:32 PM
What about show crypto ipsec sa and show crypto isakmp sa?
You can also run debug crypto ipsec 7 and debug crypto isakmp 7 to get more information.
08-04-2007 03:56 PM
08-04-2007 04:07 PM
It looks like nat-t is used.
Try this: show vpn-sessiondb detail remote filter protocol L2TPOverIPSecOverNAtT
08-04-2007 04:30 PM
08-05-2007 12:39 AM
It looks ok.
Check the logfile during a test, to see what happens with the return packets. Do your servers know how to reach the 192.168.3.0 network?
TX and RX counters are incrementing, but that is when you ping the firewall itself?
Check for dropped packet from internal servers in the logfile. If they get sent out to the tunnel without NAT applied, it should be a client side problem.
08-05-2007 02:57 AM
What can I add on the ASA to allow the .2 subnet to access the .3 subnet?
Thanks
08-05-2007 03:07 AM
If your clients have the ASA as default gateway, it should be ok already.
08-05-2007 12:52 PM
The sales folks are connecting from all over. In the Microsoft client, there is no place to add a gateway.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: