none
Remote Access: What ports do I need to forward from my broadband router/firewall to my home server for remote access?

    Question

  • In order to get remote access to work, I assume I need to forward some ports from my broadband router/firewall to my home server - what ports do I need to forward?
    Friday, February 09, 2007 6:49 PM

Answers

  • You can use the Router Configuration Wizard from the Console under the Settings ->Remote Access tab.  This will create your FREE Windows Live Domain, automatically configure your router to port forward the correct ports, and update Windows Live Domain with your IP address.

     

    If you need to manually configfure your router, you will need to forward these ports on your router: 

    • 443 TCP
    • 4125  TCP
    • 80 TCP (optional, you can use https://<ip or domain name>/remote instead of http://<ip or domain name>/remote)

    Using HTTPS:// will bring you to the log on screen instead of http:// which will bring you to the home page.  This can be a work around for port 80 being blocked.

    Friday, February 09, 2007 7:15 PM
    Moderator

All replies

  • You can use the Router Configuration Wizard from the Console under the Settings ->Remote Access tab.  This will create your FREE Windows Live Domain, automatically configure your router to port forward the correct ports, and update Windows Live Domain with your IP address.

     

    If you need to manually configfure your router, you will need to forward these ports on your router: 

    • 443 TCP
    • 4125  TCP
    • 80 TCP (optional, you can use https://<ip or domain name>/remote instead of http://<ip or domain name>/remote)

    Using HTTPS:// will bring you to the log on screen instead of http:// which will bring you to the home page.  This can be a work around for port 80 being blocked.

    Friday, February 09, 2007 7:15 PM
    Moderator
  • Joel, what happens next? I have opened my ports, I am able to remote access in, but I am unable to connect using http:// or Https://

    What else would I look for?

    Thanks

    Bill Dow

     

     

    Monday, February 12, 2007 10:10 PM
  • Seeing that WHS does not include Exchange 2003 feature, and I have SBS 2003 R2 at home which has RDP setup already. What is your best recommendation to co-exist WHS with SBS 2003 in terms of RDP to both servers.
    Tuesday, February 13, 2007 10:34 AM
  • Will standard 3389 RDP work as well?  Also, In Windows XP, this can be changed via the registry in order to allow router port forwarding to point you to every machine in your house (e.g. 3389, 3390, 3391), and then connecting to myrouter:3390, myrouter:3391.  Would this be allowed (not necessarily supported - just allowed) for WHS?

    -Janssen


    Wednesday, February 14, 2007 12:29 PM
  •  Joel Burt wrote:

    You will need to forward these ports on your router: 

    • 443 TCP
    • 4125  TCP
    • 80 TCP (optional, you can use https://<ip or domain name>/remote instead of http://<ip or domain name>/remote)

    Using HTTPS:// will bring you to the log on screen instead of http:// which will bring you to the home page.  This can be a work around for port 80 being blocked.

     

    Thanks, Joel, very helpful information.

    Jan :)

    Tuesday, February 20, 2007 5:23 PM
  • Would there be a way to change the ports?  My ISP blocks 443 at the cable modem.

     

    Saturday, February 24, 2007 8:20 PM
  • Does this mean that I can keep my old webserver (linux/apache) running on port 80 and still be able to use remote access?

    (I have not installed home server yet)

    Friday, March 02, 2007 12:34 PM
  • My ISP blocks Port 80/443 incomming to my home

    Can I change the port numbers to any custom number ?

    Monday, March 05, 2007 6:31 PM
  • Are, or can, any of these ports be user-configurable on either the server or the client?

    I have a secure website running from home already on a different server. I realize this is counter to the target audience; one server in the household. However, given that many of the first adopters are going to be geeks and may of those people will already have other servers including (but certainly not limited to) Exchange, for instance, since WHS doesn't do an equivalent, it would be nice to have configurable ports.
    To be clear, the 4125 is not the problem, just the 443.


    I tried changing the SSL port used in IIS to 1443 but when I try browsing to https://whs:1443/remote I get nothing...

    What can I do?
    Wednesday, March 07, 2007 11:32 PM
  • ok, i have done this to the letter on my WAG54G V.2 but the only page i can ever view outside my home network is the https://<ext ip>/home. i can try and click on the log in button in an attempt to get to https://<ext ip>/remote/ but the page never loads when accessing it from an external site.

    it works fine all day long from within my home network, even from my ext IP but not from another site. =/

    am i over looking something simple? is it my modem/router or is there a real issue here?

    cheers.
    ac
    Tuesday, March 13, 2007 1:54 PM
  • ok, i have done this to the letter on my WAG54G V.2 but the only page i can ever view outside my home network is the https://<ext ip>/home. i can try and click on the log in button in an attempt to get to https://<ext ip>/remote/ but the page never loads when accessing it from an external site.

    it works fine all day long from within my home network, even from my ext IP but not from another site. =/

    am i over looking something simple? is it my modem/router or is there a real issue here?

    cheers.
    ac
    Tuesday, March 13, 2007 2:06 PM
  • I know that I do not have the typical home setup, but I already have a W2K3 Exchange HTTPS server and a Mac web server, so is there any way to change the ports on Windows Home Server, like in IIS?
    Wednesday, March 14, 2007 11:01 PM
  • I tried that and it did not work. I can RDC into WHS from the LAN but not from WAN. Anything else I should be trying? Thanks
    Thursday, March 15, 2007 4:53 PM