Comments on: Problems accessing WHS Web Interface. Ports 80 and 443 Blocked? http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/ A server for the people !!! Sat, 21 Nov 2009 16:10:29 +0000 http://wordpress.com/ hourly 1 By: Victor Moreira http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-16130 Victor Moreira Fri, 17 Apr 2009 01:14:33 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-16130 My problem is : I have a external equipement connected to my network and it have the 443 port used to connect with HTTPS. What i need to do on WHS to change the port to access with https ? My problem is :
I have a external equipement connected to my network and it have the 443 port used to connect with HTTPS.

What i need to do on WHS to change the port to access with https ?

]]> By: Scott http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-15567 Scott Thu, 12 Mar 2009 13:15:24 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-15567 Verizon FIOS service seems to have a new router replacing the ActionTec they'd been using - a Westell 9100em. Although I'm no networking expert, I usually get by but finally could not get manual port forwarding to work. Neither could my colleague, who is quite adept at networking. Finally we stumbled on a solution - the router has some canned forwarding selections for gaming. Alien vs Predator contained what I needed to get out on port 8000. That's right - manually configuring so wouldn't work but doing so via the canned rule would. Verizon FIOS service seems to have a new router replacing the ActionTec they’d been using – a Westell 9100em. Although I’m no networking expert, I usually get by but finally could not get manual port forwarding to work. Neither could my colleague, who is quite adept at networking. Finally we stumbled on a solution – the router has some canned forwarding selections for gaming. Alien vs Predator contained what I needed to get out on port 8000. That’s right – manually configuring so wouldn’t work but doing so via the canned rule would.

]]> By: KathyN http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-15547 KathyN Wed, 11 Mar 2009 03:27:49 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-15547 I've been able to successfully set up the https port to 8009, however for the http port, i've tried multiple different ports (8008, 8010, and even 2301 - i have 2300 set up for a camera and that works). However for Home Server HTTP I get the initial login screen for Home Server, but when I click on the login button, I get IE cannot display webpage (running IE7). Any ideas why? I’ve been able to successfully set up the https port to 8009, however for the http port, i’ve tried multiple different ports (8008, 8010, and even 2301 – i have 2300 set up for a camera and that works). However for Home Server HTTP I get the initial login screen for Home Server, but when I click on the login button, I get IE cannot display webpage (running IE7). Any ideas why?

]]> By: NickM http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-14519 NickM Fri, 16 Jan 2009 22:28:52 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-14519 I've successfully installed SharePoint Services 3.0 on my WHS. I can access my SharePoint site from within my home network using http://myservername:PortNum but I cannot access it from that same address via internet. More importantly, I own a domain name which I want to be my homepage address for the SharePoint site I am building. However, my domainname takes me to the canned HP Mediasmart Home Server landing page. How can I fix this? I suspect it has something to do with IIS settings, but am ignorant of these. Regards, NickM I’ve successfully installed SharePoint Services 3.0 on my WHS. I can access my SharePoint site from within my home network using http://myservername:PortNum but I cannot access it from that same address via internet.

More importantly, I own a domain name which I want to be my homepage address for the SharePoint site I am building. However, my domainname takes me to the canned HP Mediasmart Home Server landing page.

How can I fix this? I suspect it has something to do with IIS settings, but am ignorant of these.

Regards, NickM

]]> By: BrettH http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-12222 BrettH Sat, 27 Sep 2008 18:49:38 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-12222 Hey, By doing this I cannot log in to the windows home server console from other computers on the network. Is there a way to fix this or did I do something wrong? Hey,
By doing this I cannot log in to the windows home server console from other computers on the network. Is there a way to fix this or did I do something wrong?

]]> By: Eric http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-7215 Eric Wed, 13 Feb 2008 19:58:43 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-7215 For those of you that are changing ports and have a mediasmart server from HP, check out the tutorial over at http://myhomeserver.com on changing ports. There is a default.htm file you need to add or the main page will "break" unless you specify /home or /remote. For those of you that are changing ports and have a mediasmart server from HP, check out the tutorial over at http://myhomeserver.com on changing ports. There is a default.htm file you need to add or the main page will
“break” unless you specify /home or /remote.

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-7089 Philip Churchill Mon, 04 Feb 2008 12:25:58 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-7089 Thanks for the tip Andrew. Thanks for the tip Andrew.

]]> By: Andrew http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-7054 Andrew Sun, 03 Feb 2008 05:00:10 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-7054 Here's an odd one that hopefully might help some people who are still stuck trying to resolve this port issue (from a 'non-techie'): - my DSL ISP uses a Netopia modem that blocked me from opening up any ports on my LAN - I had to get the admin username and password to log into the DSL modem itself and enable 'bridging connections' to allow my D-Link DIR-655 router to be configured properly for port forwarding Once I enabled briding connections, all was good... extreamely painful to find this out by trial and error and calling back the DSL company after trying everything everywhere and not being successful, but now all is good. Here’s an odd one that hopefully might help some people who are still stuck trying to resolve this port issue (from a ‘non-techie’):
- my DSL ISP uses a Netopia modem that blocked me from opening up any ports on my LAN
- I had to get the admin username and password to log into the DSL modem itself and enable ‘bridging connections’ to allow my D-Link DIR-655 router to be configured properly for port forwarding

Once I enabled briding connections, all was good… extreamely painful to find this out by trial and error and calling back the DSL company after trying everything everywhere and not being successful, but now all is good.

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-6292 Philip Churchill Sun, 13 Jan 2008 13:43:52 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-6292 Thanks Jason Brunner. Thanks Jason Brunner.

]]> By: Jason Brunner http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-6143 Jason Brunner Fri, 11 Jan 2008 06:44:31 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-6143 Another way around this without having to change the settings on your server is if your router/firewall allows you to set public and private ports when making rules. When I forward the traffic to my server the public port is 8009, but that is mapped to the private (internal) port of 443. Hope that made sense. Another way around this without having to change the settings on your server is if your router/firewall allows you to set public and private ports when making rules. When I forward the traffic to my server the public port is 8009, but that is mapped to the private (internal) port of 443. Hope that made sense.

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-5484 Philip Churchill Sun, 30 Dec 2007 08:47:57 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-5484 Hi Michael, To remote decktop into the server: 1.Click on Start 2. Click on Run 3. Type mstsc and then press enter 4. Type the name of your server and then press enter 5. FOR VISTA ONLY: A dialog asking for credentials will appear, you need to type this exactly as shown (w/o quotes) "yourservername\Administrator" and type the password that you use when you login to the WHS console. 6. FOR XP: you will see the Windows Home Server Logon Screen, type Administrator for the username and then the password you use with the WHS console 7. Press enter and then you are logged in to your WHS admin desktop The WHS console is NOT used in this operation. Hi Michael,

To remote decktop into the server:

1.Click on Start
2. Click on Run
3. Type mstsc and then press enter
4. Type the name of your server and then press enter
5. FOR VISTA ONLY: A dialog asking for credentials will appear, you need to type this exactly as shown (w/o quotes) “yourservername\Administrator” and type the password that you use when you login to the WHS console.
6. FOR XP: you will see the Windows Home Server Logon Screen, type Administrator for the username and then the password you use with the WHS console
7. Press enter and then you are logged in to your WHS admin desktop

The WHS console is NOT used in this operation.

]]> By: Michael http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-5400 Michael Fri, 28 Dec 2007 18:57:08 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-5400 Hello, First, thanks for the great resource! Second, I am using an HP Media Server with WHS installed and do not know how to get to IIS. I can do this on my other regular Vista and XP clients using Remote Desktop but not the WHS control panel. Thanks for the help! Hello,
First, thanks for the great resource! Second, I am using an HP Media Server with WHS installed and do not know how to get to IIS. I can do this on my other regular Vista and XP clients using Remote Desktop but not the WHS control panel. Thanks for the help!

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-5117 Philip Churchill Mon, 24 Dec 2007 09:25:59 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-5117 Hi Matt TLC, Thanks for your comment. It certainly is a sad state of affairs. We should demand that unlimited means unlimited! Hi Matt TLC,
Thanks for your comment. It certainly is a sad state of affairs. We should demand that unlimited means unlimited!

]]> By: Matt TLC http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-5037 Matt TLC Sat, 22 Dec 2007 21:39:35 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-5037 ISP only concern themselves over profits. That's why they want to limit WHS, because of bandwidth/throughput. Funny how ISP customers sign up for unlimited use, and then get slapped in the face by limits of use. Blocking ports, filtering, monitoring and censoring by your ISP's and governments will grow. Think of Iran, North Korea and China where active measures are taken to limit the flow of information. WHS doesn't sell you any rights, it only grants you rights to have in possession a license of use from Microsoft under the EULA terms. You still need to connect to the Internet, via your ISP, which has and enforces it's own set of policies. Already Peer 2 Peer is filtered, blocked and regulated. That's in addition to Media Sentry, MPAA, RIAA, SafeNet, actively spying and snooping on Internet traffic, just as the NSA, FBI, CIA, government agencies and others (corporations) are doing. That's in addition to ISP's shaping Internet traffic. Why isn't there the ability in WHS to host it's own SSL encrypted website by end users in a simple method over the Internet? Why no SFTP? No TLS Email Server? Why NO AES 256 bit, or a method to allow communication like Mesh Networking? Reason One: subscription service insures dependency upon the provider for online services (IP domains) and software applications (online only)! Reason Two: Provider controls distribution of content. Reason Three: Insuring the above keeps you a monopoly! Conclusion: $M wants to become a content distribution channel, just like an ISP for the Internet. When this happens we all suffer, with more DRM technologies, removing our fair use rights, in exchange for limited innovation to insure Microsoft remains a monopoly. If you really want to open port 443 and port 80, change the rule of laws that grant you these rights so corporations like SBC, Comcast, Earthlink, AT&T cannot take them away from you. If you don't care those controlling your access will charge more ahead to allow the use of a WHS later, and still monitor and filter and censor what you transmit for their benefit (gov regulated) for ever more profits to be made at your development. Support open source code, for public review and most of all to allow the benefit to all in society rather than a few only. ISP only concern themselves over profits. That’s why they want to limit WHS, because of bandwidth/throughput. Funny how ISP customers sign up for unlimited use, and then get slapped in the face by limits of use.

Blocking ports, filtering, monitoring and censoring by your ISP’s and governments will grow. Think of Iran, North Korea and China where active measures are taken to limit the flow of information.

WHS doesn’t sell you any rights, it only grants you rights to have in possession a license of use from Microsoft under the EULA terms.

You still need to connect to the Internet, via your ISP, which has and enforces it’s own set of policies. Already Peer 2 Peer is filtered, blocked and regulated. That’s in addition to Media Sentry, MPAA, RIAA, SafeNet, actively spying and snooping on Internet traffic, just as the NSA, FBI, CIA, government agencies and others (corporations) are doing. That’s in addition to ISP’s shaping Internet traffic.

Why isn’t there the ability in WHS to host it’s own SSL encrypted website by end users in a simple method over the Internet? Why no SFTP? No TLS Email Server? Why NO AES 256 bit, or a method to allow communication like Mesh Networking?

Reason One: subscription service insures dependency upon the provider for online services (IP domains) and software applications (online only)!

Reason Two: Provider controls distribution of content.
Reason Three: Insuring the above keeps you a monopoly!

Conclusion: $M wants to become a content distribution channel, just like an ISP for the Internet. When this happens we all suffer, with more DRM technologies, removing our fair use rights, in exchange for limited innovation to insure Microsoft remains a monopoly.

If you really want to open port 443 and port 80, change the rule of laws that grant you these rights so corporations like SBC, Comcast, Earthlink, AT&T cannot take them away from you.

If you don’t care those controlling your access will charge more ahead to allow the use of a WHS later, and still monitor and filter and censor what you transmit for their benefit (gov regulated) for ever more profits to be made at your development.

Support open source code, for public review and most of all to allow the benefit to all in society rather than a few only.

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-4449 Philip Churchill Thu, 13 Dec 2007 15:58:41 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-4449 Hi Clodagh, You need to do this on the server itself. If you have WHS installed then there will be a IIS section within the windows that opens. Hi Clodagh,
You need to do this on the server itself. If you have WHS installed then there will be a IIS section within the windows that opens.

]]> By: Clodagh http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-4446 Clodagh Thu, 13 Dec 2007 14:55:27 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-4446 My computer management doesn't have an IIS section any ideas as to how i can get to the default web site properties another way...head's wrecked with this blocked port business! My computer management doesn’t have an IIS section any ideas as to how i can get to the default web site properties another way…head’s wrecked with this blocked port business!

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-1276 Philip Churchill Mon, 17 Sep 2007 19:56:39 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-1276 Hi EmRoD, In RC1 of WHS port 4125 was hard coded and could not be changed. For the RTM version things might have changed. Check the following two Microsoft KB Articles that may help you. <a href="http://support.microsoft.com/kb/886209" rel="nofollow">KB886209</a> and <a href="http://support.microsoft.com/kb/306759/" rel="nofollow">KB306759</a>. Hi EmRoD,
In RC1 of WHS port 4125 was hard coded and could not be changed. For the RTM version things might have changed. Check the following two Microsoft KB Articles that may help you.
KB886209 and KB306759.

]]> By: EmRoD http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-1263 EmRoD Mon, 17 Sep 2007 06:12:38 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-1263 Hi, just a question, how do you change the remote desktop port (TCP 4125) ? At work 80 and 443 are open, but 4125 is blocked i can't find any solution about that issue Hi,

just a question, how do you change the remote desktop port (TCP 4125) ?

At work 80 and 443 are open, but 4125 is blocked i can’t find any solution about that issue

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-1007 Philip Churchill Thu, 06 Sep 2007 20:22:03 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-1007 Thanks for the info Keith Thomas, luckerly most routers remote management ports can be changed within the routers web interface. "Using a Macintosh OS 9 you cannot get to the web page at all." - Any Mac users? Thanks for the info Keith Thomas, luckerly most routers remote management ports can be changed within the routers web interface.
“Using a Macintosh OS 9 you cannot get to the web page at all.” – Any Mac users?

]]> By: Keith Thomas http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-824 Keith Thomas Thu, 30 Aug 2007 22:40:45 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-824 I had a issue where I was unable to get the Windows Home Server to work correctly from the internet, I was either getting a error 404 from the http://hostname.livenode.com from any internet connected PC and a logon prompt which was my routers home page, after troubleshooting the issue for 1-2 nights, I found out that the broadband router that I have was using ports 80 and 443 for remote management of the router, which was a factory default setting. I have found out that using a Macintosh OS 9 you cannot get to the web page at all. I had a issue where I was unable to get the Windows Home Server to work correctly from the internet, I was either getting a error 404 from the http://hostname.livenode.com from any internet connected PC and a logon prompt which was my routers home page, after troubleshooting the issue for 1-2 nights, I found out that the broadband router that I have was using ports 80 and 443 for remote management of the router, which was a factory default setting.

I have found out that using a Macintosh OS 9 you cannot get to the web page at all.

]]> By: GeorgeP3 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-133 GeorgeP3 Sat, 30 Jun 2007 22:35:43 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-133 OOPs, of course I ment 443 not 442. Im on RC1 and I tryed this even though I didn't need to and found unlike others above it worked untill I did an IISReset which set the ports back to 80 and 443. Did I miss something? OOPs, of course I ment 443 not 442. Im on RC1 and I tryed this even though I didn’t need to and found unlike others above it worked untill I did an IISReset which set the ports back to 80 and 443. Did I miss something?

]]> By: GeorgeP3 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-132 GeorgeP3 Sat, 30 Jun 2007 22:27:27 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-132 On the AUP issue, I agree you should check with your ISP. I use Earthlink Broadband and they didn't have me blocked from port 80 or 442. I checked with them any way and was told WHS doesn't violate my AUP. On the AUP issue, I agree you should check with your ISP. I use Earthlink Broadband and they didn’t have me blocked from port 80 or 442. I checked with them any way and was told WHS doesn’t violate my AUP.

]]> By: Colin Walker http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-78 Colin Walker Tue, 26 Jun 2007 06:04:27 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-78 SME - that's actually a very good point. I've always been lucky that my ISP doesn't block anything. I know that a number of them block port 25 to prevent you having your own mail server but I've not come across many that do block 80 and 443. Definitely best to check though. While they may not allow a normal web server they may take a different approach to a home server but best not to take the risk without asking them. SME – that’s actually a very good point. I’ve always been lucky that my ISP doesn’t block anything. I know that a number of them block port 25 to prevent you having your own mail server but I’ve not come across many that do block 80 and 443.

Definitely best to check though. While they may not allow a normal web server they may take a different approach to a home server but best not to take the risk without asking them.

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-71 Philip Churchill Mon, 25 Jun 2007 21:25:09 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-71 Colin Walker has stated over on his blog http://randomelements.me.uk/Lists/Posts/Post.aspx?ID=366 that he has not needed to add “/home” to the end of the URL in order for the site to work. And his works fine via IP, livenode.com address or normal domain address. Although he does find that he needs to run IISRESET after changing the port. (More information on the IISRESET command is available in the Microsoft Knowledge Base http://support.microsoft.com/kb/202013/en-us) Why I have had to add /home to the end of the URL for mine to work I have no idea. Anyone? Colin Walker has stated over on his blog http://randomelements.me.uk/Lists/Posts/Post.aspx?ID=366 that he has not needed to add “/home” to the end of the URL in order for the site to work. And his works fine via IP, livenode.com address or normal domain address.
Although he does find that he needs to run IISRESET after changing the port. (More information on the IISRESET command is available in the Microsoft Knowledge Base http://support.microsoft.com/kb/202013/en-us)
Why I have had to add /home to the end of the URL for mine to work I have no idea. Anyone?

]]> By: Mark http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-69 Mark Mon, 25 Jun 2007 21:03:36 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-69 Is there a way to get this to work without needing the "/home" at the end of the URL? For example, to be able to use "http://xxx.xxx.xxx.xxx:8008/" Instead of "http://xxx.xxx.xxx.xxx:8008/home" Is there a way to get this to work without needing the “/home” at the end of the URL?
For example, to be able to use “http://xxx.xxx.xxx.xxx:8008/”
Instead of “http://xxx.xxx.xxx.xxx:8008/home”

]]> By: SME http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-62 SME Sun, 24 Jun 2007 20:42:15 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-62 Why don't you warn them that they can lose their accounts for evading the AUP? If their ISP blocks the posts, they don't want you to run servers and you agreed to follow their rules. More ISPs block ports because users can't be trusted to follow the rules that they agreed to. Why don’t you warn them that they can lose their accounts for evading the AUP? If their ISP blocks the posts, they don’t want you to run servers and you agreed to follow their rules. More ISPs block ports because users can’t be trusted to follow the rules that they agreed to.

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-49 Philip Churchill Fri, 22 Jun 2007 21:00:50 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-49 A discussion has also been opened on on Microsoft WHS forums regarding this article, which may also help you. http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=1770542&SiteID=50 A discussion has also been opened on on Microsoft WHS forums regarding this article, which may also help you.
http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=1770542&SiteID=50

]]> By: Philip Churchill http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-48 Philip Churchill Fri, 22 Jun 2007 20:54:31 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-48 I am not sure about why you are getting this error. You are trying via the web interface e.g. "https://example.livenode.com" ? I am not sure about why you are getting this error. You are trying via the web interface e.g. “https://example.livenode.com” ?

]]> By: Darren http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-47 Darren Fri, 22 Jun 2007 14:59:57 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-47 When I follow the directions, it tells me I cannot login to the Admin account remotely from my laptop. It gives me some instructions but that remote install doesnt give me s start menu to open control panel and IIS... What am I missing? What is the workaround? When I follow the directions, it tells me I cannot login to the Admin account remotely from my laptop. It gives me some instructions but that remote install doesnt give me s start menu to open control panel and IIS…

What am I missing? What is the workaround?

]]> By: Jon http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-40 Jon Thu, 21 Jun 2007 16:06:00 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-40 What about adding new computers via connector install? What about adding new computers via connector install?

]]> By: Colin Walker http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-39 Colin Walker Thu, 21 Jun 2007 15:46:47 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-39 Not at all. It's purely affecting remote connection via the web. Not at all. It’s purely affecting remote connection via the web.

]]> By: Jon http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-37 Jon Thu, 21 Jun 2007 13:33:35 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-37 Will this effect the connectors from within the home network (i.e. this won't cause any 'network health' problems or effect backups)? Will this effect the connectors from within the home network (i.e. this won’t cause any ‘network health’ problems or effect backups)?

]]> By: Colin Walker http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-35 Colin Walker Thu, 21 Jun 2007 08:44:20 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-35 I always redirect mine to 563 for HTTPS as I'm already using 80 and 443 for my blog and Exchange Server. I find that I have to do an IISRESET for the change to take effect properly but I don't have any problem with not including the /home part. I can connect via IP address or livenode address without an issue. I always redirect mine to 563 for HTTPS as I’m already using 80 and 443 for my blog and Exchange Server.

I find that I have to do an IISRESET for the change to take effect properly but I don’t have any problem with not including the /home part.

I can connect via IP address or livenode address without an issue.

]]> By: How To... Access Your Home Server Remotely When Your ISP Is Blocking You | We Got Served http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-34 How To... Access Your Home Server Remotely When Your ISP Is Blocking You | We Got Served Thu, 21 Jun 2007 07:41:19 +0000 http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/#comment-34 [...] great guide from Phillip Churchill! Check it out. Share this post at: These icons link to social bookmarking sites where readers can share and [...] [...] great guide from Phillip Churchill! Check it out. Share this post at: These icons link to social bookmarking sites where readers can share and [...]

]]>