I'm having a strange situation. I have a LAN where I have a Windows Server 2008 R2 server and a few other machines (Win 7, Vista). I have configured port forwarding on my router to forward port 4444 to port 3389 on the Server 2008 machine so that I can access it remotely through the router's public IP. I have also set up everything for remote access in the Server 2008 machine (firewall, allow remote assistance, etc).

Now, when I try to remote desktop, I'm able to connect only if I'm on the local subnet (If I'm connected to the router, and I try the public IP:4444, I can RDC). If I try through a different network, the RDC fails. Any idea why this is happening?

link|improve this question
Why wouldn't you just forward port 3389 to port 3389? – joeqwerty Jan 20 '11 at 21:39
the different netowrks = different local subnets? – redknight May 12 '11 at 6:00
feedback

3 Answers

What kind've router/firewall is this?

It sounds like it either: a)has been limited to internal forwarding only, or b)something else is screwy.

Also, what kind of client do you have connecting? XP, 7 Vista? Is your RDP Client up-to-date?

link|improve this answer
feedback

If you use the Windows firewall : Among the "Advanced" tab In the firewall Inbound rules, you have an option "Edge Traversal" : is it set to "Block Edge Traversal" ?

link|improve this answer
feedback

I would take a closer look at the router, if you are able to connect to it at all, and the inbound rules on the firewall.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.