Windows Terminal Services Port Forwarding

Unanswered Question
Jan 11th, 2008

I have a brand new ASA5505 with ASA803-K8 for it's OS. I'm trying to set up clientless VPN access so that users can then start the Windows Remote Desktop Connection and use port forwarding to access our terminal server.

So far, I have LDAP authentication working and users are able to log in to VPN. I have local port 20101 mapped to my internal server port 3389. Yet, when the Application runs from my browser it says the local port is 127.0.0.1:20101 and remote is <remote server>:3389. When I try to connect, the client says it can't find the machine.

Do I need to configure any ACL's or DNS entries, etc? I attached the port forwarder to the group policy fine as it loads what I'm telling it to, the port forwarding just doesn't work. Any ideas?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion