• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Remote Desktop Help

N

NJLOAD

Senior member
Two computers same OS, XP Pro and they are set up the same in my Dlink Router but I can only access one from work. I get an error message can't connect to remote computer it may be busy or something like that. The weird thing is i can access both computers from my other home computer.

Any help is appreciated.
 
Your router uses Network Address Translation to direct traffic to/from the Internet to more than one PC. Because of this, you have to use a non-standard TCP Port for Remote Desktop to at least one of the two computers. If they BOTH use the standard TCP Port 3389, then the router won't know which PC to send the incoming connection to.

Configuring XP Remote Desktop to a non-standard port:
http://support.microsoft.com/kb/304304

After you've set at least one of the PCs to a non-standard RDP port, you can program your router for Port Forward the new port to the PC that's been changed from the default TCP Port 3389. So inbound RDP connections on TCP Port 3389 will be sent to the "untouched" PC and inbound RDP connections on the non-standard port will be sent to the other PC that you modified.
 
yup - change the rdp port on one and punch a hole in firewall or install a windows 2008 RDP gateway server (serious overkill)
 
You do not have to change the computer configurations at all if your router does port forwarding. Just have the router forward port 3390 to computer_2_ip:3389
 
I have a Dlink Dir 655 and it does have port forwarding, but I am still struggling with the setting, I'll keep trying and hopefully get it.

thanks for all the help so far.
 
word to the wise: change the rdp port - makes haxors less likely to figure out whats going on. 3389 is all too obvious.
 
NJLOAD said:
I have a Dlink Dir 655 and it does have port forwarding, but I am still struggling with the setting, I'll keep trying and hopefully get it.
Click to expand...
How are you testing it? You have to test it from an outside network, not from inside your own network.

Also, as noted (and as I always forget), be sure any PC firewalls are open for inbound connections on the RDP TCP port of your choosing.

As suggested, test RDP locally (using local network addresses) to see if RDP is listening and if your target PC's firewall isn't blocking the port.
 
Last edited:
RebateMonger said:
Your router uses Network Address Translation to direct traffic to/from the Internet to more than one PC. Because of this, you have to use a non-standard TCP Port for Remote Desktop to at least one of the two computers. If they BOTH use the standard TCP Port 3389, then the router won't know which PC to send the incoming connection to.

Configuring XP Remote Desktop to a non-standard port:
http://support.microsoft.com/kb/304304

After you've set at least one of the PCs to a non-standard RDP port, you can program your router for Port Forward the new port to the PC that's been changed from the default TCP Port 3389. So inbound RDP connections on TCP Port 3389 will be sent to the "untouched" PC and inbound RDP connections on the non-standard port will be sent to the other PC that you modified.
Click to expand...

Verbatim
 
RebateMonger said:
Your router uses Network Address Translation to direct traffic to/from the Internet to more than one PC. Because of this, you have to use a non-standard TCP Port for Remote Desktop to at least one of the two computers. If they BOTH use the standard TCP Port 3389, then the router won't know which PC to send the incoming connection to.

Configuring XP Remote Desktop to a non-standard port:
http://support.microsoft.com/kb/304304

After you've set at least one of the PCs to a non-standard RDP port, you can program your router for Port Forward the new port to the PC that's been changed from the default TCP Port 3389. So inbound RDP connections on TCP Port 3389 will be sent to the "untouched" PC and inbound RDP connections on the non-standard port will be sent to the other PC that you modified.
Click to expand...

Dido this ^
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top