We all know one of the major features of WHS is the ability to get to your files, pictures, video … remotely. The down side is that the ports used are ports most ISPs block by default.
As a Microsoft WHS beta tester this was a feature I was unable to test since my ISP blocks ports 80 and 443. Port 4125 is open.
Since most ISPs block ports 80 and 443 I can only speculate that a lot of households only buy a home server just to share video and pictures with loved ones across the country and overseas just to discover they purchased WHS and can only use the server for sharing files, photos and backup their systems.
As described, my ISP does block port 80 and 443 and I called my ISP for additional information. I was told that I can switch from their private consumer section to their business section and will have all ports open and a static IP for roughly $96 a month .. auch - compared to my current 5down/512 up for $36…
Anyway, I would like the WHS team to consider implementing an update or Add-in download for the console which will enable changing the ports. I am sure the WHS server will be marketed as “Remote access your files, photos, video and more …” and it may backfire since most of us have ISPs blocking these ports. Having an update or add-in to change the ports would greatly help and ensure the Home server lives up to its name.
Thanks Microsoft / WHS Team for the Home Server and a great product. I hope you will consider this posting/request.
You should go to Microsoft Connect and register this as a suggestion. You should also copy this post to the Suggestions sub forum as well.
Also, and Im sure someone will correct me if I am wrong, but I think there is a way around you problem. Have you done a search on the forum as I am sure there has been something posted before.....
See Philip Churchill's blog post on changing the ports 80 and 443.
Thanks Tom and Adrew, I will take a look at the link.
In the meantime I searched the forum and found the following links, I will test this out in the next few days and will get back to you and post my story :-D
I appriciate the quick response ...
The links I found which looks to fit the issue are:
I will start with the good news, that it now works and my issue has been resolved though I am still a bit concerned when other less tech people buy a server and their ISP blocks the ports. At least we know how to change it if friends and family buys one.
I have a small adjustment to the link:
The article describe using port 8008 for HTTP and port 600 for SSL….For whom that reads this post, remember port 600 is still a fairly low port number and will more than likely be blocked too ISPs normally block ports below 1200. I my situation I used port 8008 for HTTP and 8009 for SSL, this is simple and easy to remember. Also, remember to stop and start your IIS services after you make the changes.
You can access your server by https://Servername.homeServer.com:8009/remote
I still need to review the issues mentioned elsewhere where the connector software will not install on a new system after the changes…..
Again, Thanks for your posts, I hope others will discover our thread and start using this feature …