I've been trying to fix this problem for a month....I am able to access the web site locally by typing in the IP address of my WHS. When I try to access it locally using the home server domain name: xxxxxxx.homeserver.com, I get a message in IE saying that name did not match any documents. When I do type in the IP address of the WHS I get the Microsoft Windows Home Server web site. When I click on logon, I get a page that says "There is a problem with this website's security certificate." I click on "continue to use this website (not recommended)" and can then logon. Cox is my ISP. I have a Netgear WNDR3700 router and use PhonePower for telephone service. I did contact PhonePower to see if there was a problem. Their phone router is a Grandstream HT502. They had me go into the basic settings of the Grandstream and change the port from 80 to 4200 because, they said, both WHS and the Grandstream were using the same port. The connection is as follows: The ethernet cable from the cable modem (Cox: Motorola Surfboard cable modem) goes into the WAN port of the Grandstream. An ethernet cable goes from the LAN port of the Grandstream to the "internet" (WAN, I assume) port of the Netgear router. Two ethernet cables go from 2 "ethernet" (LAN, I assume) ports of the Netgear router to the ethernet ports on the desktop computer and the WHS. My WHS is just my old desktop computer that I installed an OEM version of WHS on. When I go to settings/remote access from the WHS console on my desktop, I get a message that Remote Access is not available. When I click on "repair", I get green check marks on the first 2 items and a red "X" on Verifying that your remote Web site is available from the internet. On the Netgear router settings, under Attached Devices, my desktop computer and the WHS are shown with their IP addresses. On the LAN setup under address reservation, I added the WHS with a fixed IP address. Under Port Forwarding/Port Triggering, I added a "custom service" with the WHS as the custom service. This particular router asks for a starting point and an ending point so I used 4125 as the starting point and 80 as the ending point and the server IP address.
Yes indeed, if it seems I have made up some of this stuff I've done that's because I have. So what do I have messed up here? Everything I've done has been based on something I've read, but it's quite possible that the combination of things has screwed up the works. Maybe someone can tell me that the solution is really simple! I've just about reached the limits of my networking/computer knowledge, so please don't get too techie with me! Thanks very much, Ron
