Is there a work-around for blocked TCP port 80? RRS feed

  • Question

  • If you have Windows Home Server, and if your ISP (Cox) blocks TCP port 80, is there any kind of work-around to configure your Home Server for remote access?

    Tuesday, December 7, 2010 10:31 AM

All replies

  • If they block only port 80 but not 443, then you can just connect to your home server using HTTPS instead of HTTP. Your server will show an error, but remote access should still work.

    If they block both 80 and 443, it's possible (but unsupported) to change some of the ports being used by your server (if your ISP blocks port 4125, used for remote desktop and console access, you won't be able to change that one). It may not be such a good idea, however; your ISP probably blocks these ports because running servers on your residential connection is against their terms of service.

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, December 7, 2010 10:57 AM
  • I'm a Cox subscriber and access my server remotely. They block port 80, but not 443 or 4125. You can connect by https:. Make sure port forwarding is set on your router.
    Friday, December 10, 2010 4:26 AM