First, it may be helpful to know whether the problems you are expereincing is due to ISP port blocking. There is a good forum on that discussion at: http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=1849610&Si... Second, even if your ISP blocks port 80, you can still have a good remote access expereince using the TZO DNS service as it only requires port 443. MS WHS and MS Live DNS defaults to port 80 and this can lead to "misleading" messages under those curcomstances where port 80 is blocked and port 443 is open. Can you show a screen shot here of your port forwarding menu on your router? Maybe someone can help see where the port forwarding is not correct. Lastly, HP support can also guide you through some of this.

John A

All comments here are my own and do not necessarily reflect the opinions of Hewlett-Packard or the HP MediaSmart Server development team.

With 443 can you open the web site?

https://your-server-name.com

You must use the https:// (notice the s for secure)

That should get you in to the Web site.. You will need to open 4125 for remote access. (Remote Desktop).

Also the 4th line down where that "Auto-test" checks your website, it will always check port 80, so you will get an error there, which is ok if you just use 443 assuming we get that working.

Jonesr22,

Any luck? Also I re-read your post, and you may need to use the port-forwarding? Since I'm not sure how your virtual server thingy works but I'll give you my best guess. There could be someplace else you need to enable a virtual server? Which may come in handy if you can figure it out, as you may be able to assign a few ports to one server, and with the click of a mouse button open and close your server for external network traffic. My experience with virtual servers is limited, and with Apache web server, a virtual server had a unique name, so I'll apply that here http://www.your-server.com/Gallery uses one set of IP & ports, while http://www.your-server.com/Forum uses another set. your router hands off the traffic depending on the site name opened. And your-server.com is the external name/IP of your router. In the screen shot above where it says server name, you might try to remove spaces from the name to make it easier to access. That's just my guess, I could be 100% wrong.

Well that is the log in window for your router. Did you try my suggestions of changing your virtual server names to those without spaces, and trying to access your server with a directory name? ie www.yourservername.com/virtualservername/ try with and without the trailing "/"

But it looks like port 80 is being used by your router, if the above virtual server stuff doesn't work, you'll have to use port forwarding. And since the router is not using 443, you might simply be able to forward 443 to your MSS for web access, and 4125 if you also want to use remote access. All web access would then need to be secure https:// which is what you want any way.

Just because 443 is blocked, doesn't mean you can't forward an external port of say 4433 to an internal 4433. So when you open a url it would look like:

https://www.yoursite.com:4433/

You will also have to change the port the IIS web service listens to. (just a few mouse clicks) You could leave it at 443 and have the router forward those ports, but make life simple and just keep them the same. 

 But no need to give up because your ISP blocks 443. 

 You can even change what ports remote desktop service listens to, use "the google" It requires hacking the registry, or using a program to do it for you.