Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
What port is listening for MSTSC Connections RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I want to configure the correct port on my router so that I can TS into my Home Server from anywhere I have an Internet connection.  Normally, the default port for this would be 3389 but Home Server does not appear to be listening on this port.  Which port is Home Server using?
    Sunday, March 29, 2009 3:38 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I want to configure the correct port on my router so that I can TS into my Home Server from anywhere I have an Internet connection.  Normally, the default port for this would be 3389 but Home Server does not appear to be listening on this port.  Which port is Home Server using?
    RDC is port 3389.  You probably need to change the server firewall to allow connections from anywhere on that port.  However, adding that ability also decreases the security of your server (and it's not supported).  I would not recommend it.  If you need desktop access, the best method is to connect to a client PC in your LAN, then to the server desktop from there or change the rdpload.aspx file to display the server desktop instead of the Console through the Remote Access website.  (Both of those are also unsupported, but at least you don't decrease your server's security.)
    Sunday, March 29, 2009 5:54 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I want to configure the correct port on my router so that I can TS into my Home Server from anywhere I have an Internet connection.  Normally, the default port for this would be 3389 but Home Server does not appear to be listening on this port.  Which port is Home Server using?
    RDC is port 3389.  You probably need to change the server firewall to allow connections from anywhere on that port.  However, adding that ability also decreases the security of your server (and it's not supported).  I would not recommend it.  If you need desktop access, the best method is to connect to a client PC in your LAN, then to the server desktop from there or change the rdpload.aspx file to display the server desktop instead of the Console through the Remote Access website.  (Both of those are also unsupported, but at least you don't decrease your server's security.)
    Sunday, March 29, 2009 5:54 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I will be NAT'ing into it through my router so I should not have to change anything on the firewall.  And, I would actually change the port number to something that is not well known.  What has me scratching my head a little is when I am on my local LAN and RDP into the server using MSTSC and then do a netstat -a, I do not see it listening on port 3389.  And when I try to RDP in from the Internet, I cannot connect (I already have the NAT setup for forwarding to 3389).  I had 3 other Windows 2003 servers that I used to do this with all the time that i have since replaced with the single Home Server.
    Sunday, March 29, 2009 8:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you change the scope on the Windows Home Servers Windows Firewall applet (in Start/Control Panel) on the Exceptions tab for the Remote Desktop exception to allow connections from any computer?
    Also be aware, that this is not a supported usage scenario of Windows Home Server.
    Best greetings from Germany
    Olaf
    Monday, March 30, 2009 9:51 AM
    Moderator