RDP doesn;t work

[mtx]

I have two computers at home that I want to RDP to. One with default port 3389 works. I just tried setting up the second one with port 3400 (via XP registry), set up the port forwarding for 3400 in my router page, reset my router, restart my computer, but the RDP won't work. Can't connect to x.x.x.x:3400.

Any ideas why?? It should be very simple.

 

[aphasia]

I have two computers at home that I want to RDP to. One with default port 3389 works. I just tried setting up the second one with port 3400 (via XP registry), set up the port forwarding for 3400 in my router page, reset my router, restart my computer, but the RDP won't work. Can't connect to x.x.x.x:3400.

Any ideas why?? It should be very simple.

i had a similar problem a few years ago when i tried to RDP from work to a couple of different machines on my home LAN. i didn't do anything elegant or roll up my sleeves by digging into the registry. think i just shared the folders from the 2nd PC to the 1st with RDP access. think i also setup a couple of VMs on the machine with RDP access as well.

can also check this link ('Exposing Multiple Computers via Remote Desktop over a Single IP Address')...
http://devlicio.us/blogs/billy_mcca...-remote-desktop-over-a-single-ip-address.aspx

a guy replied to this article with this solution...

Well, you could make it a whole lot easier on yourself and just setup port forwarding on your home router like this:

external port -> internal IP -> local port

3889 -> 192.168.0.50 -> 3889

4889 -> 192.168.0.51 -> 3889

5889 -> 192.168.0.52 -> 3889

In this case, you now have one pass-thru and two redirected ports. This means you don't need to modify anything on each host, only the network configuration changes. Note you can reach each rdp session remotely using your public IP address and one of the external ports. Say your public IP is 1.2.3.4, then you do this:

1.2.3.4:3889 takes you to host 1 (192.168.0.50)

1.2.3.4:4889 takes you to host 2 (192.168.0.51)

1.2.3.4:5889 takes you to host 3 (192.168.0.52)

 

[Netwerkz101]

I have two computers at home that I want to RDP to. One with default port 3389 works. I just tried setting up the second one with port 3400 (via XP registry), set up the port forwarding for 3400 in my router page, reset my router, restart my computer, but the RDP won't work. Can't connect to x.x.x.x:3400.

Any ideas why?? It should be very simple.

XP Firewall not set to allow port 3400 in ????

 

[Demon10000]

Test it locally on your lan before you even bother testing through your router. If you can't connect locally, it'll make things much easier to troubleshoot.

 

[mtx]

i had a similar problem a few years ago when i tried to RDP from work to a couple of different machines on my home LAN. i didn't do anything elegant or roll up my sleeves by digging into the registry. think i just shared the folders from the 2nd PC to the 1st with RDP access. think i also setup a couple of VMs on the machine with RDP access as well.

can also check this link ('Exposing Multiple Computers via Remote Desktop over a Single IP Address')...
http://devlicio.us/blogs/billy_mcca...-remote-desktop-over-a-single-ip-address.aspx

a guy replied to this article with this solution...

RE the solution to this article - I believe I've done exactly that. Changed port for 2nd PC, port-forwarded new port for the local static IP. I have Windows Firewall disabled. And the PCs can see each other on the network and RDP locally. I don't understand. Faulty Windows or faulty router?!?

 

[Snowknight26]

Neither. Are you sure you're forwarding the ports correctly and using the WAN IP to connect externally?

 

[Exavior]

Test it locally on your lan before you even bother testing through your router. If you can't connect locally, it'll make things much easier to troubleshoot.

This, does it work on your network if you try from one machine to the other?

 

[Demon10000]

RE the solution to this article - I believe I've done exactly that. Changed port for 2nd PC, port-forwarded new port for the local static IP. I have Windows Firewall disabled. And the PCs can see each other on the network and RDP locally. I don't understand. Faulty Windows or faulty router?!?

What you appear to have done is slightly different. The clip your copied is actually translating ports instead of forwarding them.

Forwarding means that any data coming in on port x is forward to machine x. So port 3389 can only really be assigned to one machine without exposing your computer to the world.

If you translate the port, you can pick any random port, without changing it on your "server" (your xp box via the reg hack) and have your router forward all requests coming into your router for a specific port to a certain machine, on a specific port.

Here's the difference (as I know it isn't always clear):

Your method:

1. Internet machine talks to your router on 3400
2. Router forwards request to your machine which should be listening on 3400

The other method:
1. Internet machine talks to your router on 3400
2. Router translates 3400 to mean your remote desktop machine and translate all 3400 traffic to 3389.

This way, you don't have to do reg hacks on the XP machine to get remote desktop to listen to some odd port, and you can still have multiple machine...




regardless -- I wouldn't even bother troubleshooting this until you get it working on your LAN. If it won't work there, there is no way it's going to work across your router.

 

[Snowknight26]

regardless -- I wouldn't even bother troubleshooting this until you get it working on your LAN. If it won't work there, there is no way it's going to work across your router.

This, does it work on your network if you try from one machine to the other?

Let's not miss this gem like a few of you already have:

And the PCs can see each other on the network and RDP locally.