• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3718
  • Last Modified:

Port Redirect, Windows 7 Firewall and Remote Desktop problems

So I have mutliple computers on my network (workgroup).  I am trying to set up the abiltiy to remote into them from an outside source.  I have a DynDNS host service configured with my router and its working perfectly.

I have my ports forwarded to the ip addresses of the respective computers on my network (I'm using DD-WRT firmware).  Computer1 port 3389 (default) Computer2 port 3390

I'm running into problems with the windows firewall and now my remote desktop is not working for either (including default port).  Last night I was able to remote in to the default port (on both computers when I switched the forwarding for the ip addresses) so remote desktop is enabled on both machines.  

For the Computer2 with the redirected (or changed) RDP port I have modified the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\portnumber to decimal 3390.  There is a Key entry of EH-Tcp which also has a portnumber string that is the same as RDP-Tcp 3389 (so they are originally the same value).

What is this EH-Tcp?  Do I need to change both (I tried but at least I know whether I need to)?

Once I changed the RDP-Tcp port I restarted the Remote Desktop Services.  However, in the windows firewall there is a rule that has exception Remote Desktop TCP-In Port 3389.  The firewall exception port has not changed even though I changed it in the registry.  Is there a way I can change this port in the firewall?  Or do I add an additonal rule?

Now even with the firewall turned off I am unable to remote in.  Both computers have passwords and I was able to remote in before.  Perhaps if I can get the correct configuration the default port computer will work with the firewall off.

Any suggestions?  

JOe K.
  • 2
1 Solution
If you do want to run RDP on computer 2 on port 3390, start out by testing within the LAN, connecting to it on port 3390.  Connect from computer 1 to computer 2 so you can be sure the port forwarding isn't causing a problem.  You will need to create a new port rule in the firewall allowing incoming traffic on TCP 3390.

However, another approach which I would take, would be to put remote desktop on computer 2 back to 3389, leaving the default firewall exception in place.  Then configure your router to forward 3389 to 3389 on computer 1 but to forward 3390 to 3389 on computer 2.  Then when you connect to computer 2 within the LAN everything is just as it has always been on 3389 on both computers.  Only when connecting remotely to computer 2 will you need to specify port 3390, your firewall will take care of the port modification to 3390 for you and you should be able to connect remotely.
Imran SaeedIT Technical DirectorCommented:
have you tried Team Viewer, check the link below. Its very simple to setup and free for personal use and no need to forward any ports etc.

ClaudeWalkerAuthor Commented:
So I tried again from work.  I have been able to remote both ways from my LAN and I also have been able to login using an IP address from a computer on the LAN.

Computer1 <----> Computer2 via LAN

Computer1 -- (made up ip:port)---> Computer2 (vice versa)

WorkComputer -- (made up ip:port)---> Computer1(2) does not work

I have added TCP exceptions to those ports in the windows firewall.  Those ports are forwarded correctly in my router. I have been able to remotely administer the router therefore the ip address is correct.  The problem is either the port forwarding (which doesn't make sense) or something in the firewall).  Perhaps I have the security permissions messed up in the software firewall or the remote security is set to high or I have no idea what I'm talking about :)

Any ideas on why this computer outside my network is unable to connect via IP:Port and computers inside my network can connect via IP:Port?

JOe K.

ClaudeWalkerAuthor Commented:
Nevermind, I was adding my computer name with my login name which works within the domain however when connecting from outside the domain it only wants a user name and not a computer name

Computer\Username  did not work

Username worked!

Thanks for getting me in the right direction.

JOe K.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now