Remote Desktop connections

Unanswered Question

Hello,


There is a big problem here.


I have customer who want all the users to do remote desktop connection on to their local pcs on their LAN from home. The customer has only one public IP adress which has been used to make remote connection to the terminal server.


I have configured the following following.


8089 route to 172.16.1.158

8189 route to 172.16.1.157

8289 route to 172.16.1.156

8389 route to 172.16.1.155

8489 route to 172.16.1.151

8589 route to 172.16.1.152

8689 route to 172.16.1.153

8789 route to 172.16.1.154



I have already configured the following on the router as folows. when I tried to make the connection it did not work


ip nat inside source static tcp 172.16.1.250 3389 81.x.x.x 3389 terminal server

ip nat inside source static tcp 172.16.1.160 8088 81.x.x.x 8088

ip nat inside source static tcp 172.16.1.158 8089 81.x.x.x 8089

ip nat inside source static tcp 172.16.1.161 8188 81.x.x.x 8188

ip nat inside source static tcp 172.16.1.157 8189 81.x.x.x 8189

ip nat inside source static tcp 172.16.1.162 8288 81.x.x.x 8288

ip nat inside source static tcp 172.16.1.156 8289 81.x.x.x 8289

ip nat inside source static tcp 172.16.1.163 8388 81.x.x.x 8388

ip nat inside source static tcp 172.16.1.155 8389 81.x.x.x 8389

ip nat inside source static tcp 172.16.1.151 8489 81.x.x.x 8489

ip nat inside source static tcp 172.16.1.152 8589 81.x.x.x 8589

ip nat inside source static tcp 172.16.1.153 8689 81.x.x.x 8689

ip nat inside source static tcp 172.16.1.154 8789 81.x.x.x 8789


I would be very grateful if somebody can help me to troubleshoot.


Tahnks



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Danilo Dy Mon, 03/03/2008 - 06:02
User Badges:
  • Blue, 1500 points or more

Hi,


Let us try two of your customer users local PC 172.16.1.151 and 172.16.1.152.


First, change the Terminal Services listening port.

- Here is the link for Windows 2000 http://support.microsoft.com/kb/187623

- Change local PC 172.16.1.151 listening port from TCP3389 to TCP8489

- Change local PC 172.16.1.152 listening port from TCP3389 to TCP8589


Second, use the following NAT expression

ip nat inside source static tcp 172.16.1.151 8489 81.x.x.x 8489 extendable

ip nat inside source static tcp 172.16.1.152 8589 81.x.x.x 8589 extendable


Regards,

Dandy

Hi Dandy,


I have been able to resolve the problem with the following command lines


ip nat inside source static tcp 172.16.1.154 3389 interface Dialer0 8789

ip nat inside source static tcp 172.16.1.153 3389 interface Dialer0 8689

ip nat inside source static tcp 172.16.1.152 3389 interface Dialer0 8589

ip nat inside source static tcp 172.16.1.151 3389 interface Dialer0 8489

ip nat inside source static tcp 172.16.1.155 3389 interface Dialer0 8389

ip nat inside source static tcp 172.16.1.163 3389 interface Dialer0 8388

ip nat inside source static tcp 172.16.1.156 3389 interface Dialer0 8289

ip nat inside source static tcp 172.16.1.162 3389 interface Dialer0 8288

ip nat inside source static tcp 172.16.1.157 3389 interface Dialer0 8189

ip nat inside source static tcp 172.16.1.161 3389 interface Dialer0 8188

ip nat inside source static tcp 172.16.1.158 3389 interface Dialer0 8089

ip nat inside source static tcp 172.16.1.160 3389 interface Dialer0 8088

ip nat inside source static tcp 172.16.1.250 3389 x.x.x.x 3389


Thanks for your concern.


Actions

This Discussion