Cisco ASA 5510 VPN Tunnel

I have a Cisco ASA 5510 ASA Firmware 8(x).  It is my firewall/perimeter device for the network.  Inside the firewall on the internal LAN, I have a terminal server box.

I want to allow users with the Cisco VPN client to connect via VPN and ONLY be allowed to connect to the specific IP address (a specific port on that IP would be even better) of the terminal server to log in using RDP.  

I have 250 VPN user license and 2 webvpn licenses.  The terminal server is a windows 2008 Standard server.  I have no funds to buy any additional equipment, licenses or software.  I am not able to set up a DMZ or change the IP address of the terminal server.

All suggestions are appreciated.  Thanks in advance.
LVL 2
scottbortisAsked:
Who is Participating?
 
yuriskConnect With a Mentor Commented:
There are 2 ways to do it:
1) Old way , applicable to any PIX/ASA versions - in ACl specifiying traffic to encrypt from LAN to VPn clients ip pool , for the LAN part you set the Terminal server IP only , i.e. to encrypt traffic only
from TErminal Server IP to VPN REmote access pool. It doesnt give you option to filter on ports though.
Nowdays CIsco are recommending against this practice, nevertheless it works

2) New way, ASA 7.x and later only - in the group-policy <name> attributes that later you apply to VPN Remote access tunnel group use vpn-filter value <name_of_ACL> , where
name_of_ACL is regular ACL allowing access to specific port of Terminal Server.
Example and further details are here:
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00808c9a87.shtml 
0
 
Andres PeralesCommented:
use the VPN wizard on the ASA when you connect via the ASDM from your web browser.  It will ask you what kind of vpn, a site to site or to accept client request, when running throgh the wizard will ask you what network to protect, insert the ip address information for just the host that you want to allow connectivity to through the vpn client.
When you clients vpn then they should be able to only connect to that server.
if you do not want to use vpn then create an access rule to allow connection to that terminal server.
Is this terminal server for administration only? If not then you will need terminal server licenses as well.
0
 
scottbortisAuthor Commented:
It seems like it is a problem with the tunnelling group ACL filter.  

I cannot seem to get the filter to only allow traffic from my VPN subnet to just this specific IP.

VPN subnet = 10.3.0.0/24
IP trying to connect is 10.0.0.60

The wizard didn't work.  
0
 
scottbortisAuthor Commented:
Yeah, it seems that I was having issues with the VPN Filter.  I took portions of the document that you linked yurisk and was able to complete my configuration.  Thank you both for your help.
0
 
scottbortisAuthor Commented:
Thanks for your help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.