My ISP Verizon blocks port 80. I have read several articles on the web about port forwarding and port redirection as related to Windows Home Server and tried all the solutions but still can't get the Netgear WGR614 V6 configured right for accessing files and computers remotely. I really don't want to go the setting up a business account with Verizon. Can someone walk me through it. I would send someone an early Xmas present if it works!

One question: Has an one tried backing up the server drive ( removing it from the HPHS) and setting it up on another PC as a 2nd drive and backing it up to a 3rd drive using Acronis backup software?

Try using https://servername instead of http://servername to see if you get to it through the SSL port 443.

You could try that. The only other option is really nasty. It involves changing the port that IIS listens to. Then changing the port forwarding on your router. And then accessing the page with the port passed in. For example:

http://myserver.homeserver.com:8001

Computerwise, if you're using a TZO DDNS name provided with the MSS, by default that will redirect to using SSL (on port 443) and should be a good workaround for the Webshare and Remote pages. You would access them as Gagtech describes above:

https://yourservername.hpmediasmart.com/Webshare
https://yourservername.hpmediasmart.com/Remote

Changing IIS ports is not for the faint of heart, so we'd prefer to not have you try to do that.

Also, please post your router and ISP results in the router survey thread to help others with your same issues:
http://www.mediasmartserver.net/forums/ ... c.php?t=75

443 is also blocked by Verizon.

Doh! That sucks...

That's what I was afraid of. ISP's really frown on serving web traffic out of your home. In fact, they have it in their terms of service that they can terminate your service if they find you doing it.

I use a different port for my current web server. When I get around to setting up the MSS with the new port forwarding, I'll post instructions.

Also keep in mind that some ISP's are now snooping traffic to/from your home and can identify what type of traffic it is.

I just checked with my small local cable-based ISP as well. First time I called I was told everything was blocked, then on the second call I was told nothing was blocked. Third call I was told that web server ports were blocked, but they wouldn't give me a list.

I've run every online port tester I can find, and they all tell me that every port is blocked. I even went through changing IIS and the ports, but with no lock. Tech supports final answer was to have me switch to a commercial account, which would be an additional $40/month.

Any other ideas?

For the web page access, you may be able to change the default port in IIS. I am not sure what effects that will have with the WHS/MSS software though.

Most routers include a firewall which will block any incoming requests that aren't explicitly set to be forwarded to an internal IP address. That may be why your online port tests fail on all ports. The best way to try this is to go into your router config, set the IP address of your server to be in the DMZ, and then run the speed test. Being in the DMZ allows ALL incoming requests to forward to that system, and should show you which ports are blocked by your ISP.

I hope that helps.
Alex

I agree with Alex, DMZ is a great way to test. Here are a few more suggestions:

1) make sure the MediaSmart can be reached internally, using the INTERNAL IP Address. For example: http://192.168.1.103. To find your internal IP address, log into the Mediasmart using the home server console, open Remote Access, and under DETAIL in the router section you'll find the current IP of the MediaSmart

2) Make sure WEBSITES are turned on under Remote Access!!!

If you can see the MediaSmart website INTERNALLY, this means all is OK inside the network and it's now got to do with port forwarding, port blocking, or firewall issues.

3) Like alex explains, if the router setup from MS isnt working for you you can do this manually. Click UNCONFIGURE in the ROUTER section of remote access. This removes the UPnP forwarding tables. Then log into your router port forward and set the DMZ to the INTERNAL IP address of the Hp MediaSmart as shown in step 1

4) goto http://www.mywanip.com from a system inside the same network that the mediasmart resides...Write down the WAN IP that you see - this is the WAN IP of the network that the mediasmart resides on. This IP should match the WAN IP/Internet IP of your router under the STATUS area.

5) Write down the WAN IP address from step 4 and then either leave the location and jump on another ISP connection and try: (or call a friend that is tech savvy and have them try it) You should never try this from the same location, its NOT a valid test in most cases.

http://WANIP
https://WANIP

(Where WAN IP is the IP Address xxx.xxx.xxx.xxx you wrote down)

6) If this works (you can see the websites), then the port forwarding wasnt set properly or the MS UPnP port tool didnt work properly. Remove DMZ, then forward port 80 TCP and 443 TCP to your LAN IP address of the MediaSmart in step 1.

7) If this DOESNT work, this means either your ISP blocks all ports or you could have a "double NAT" scenario where a DSL or Cable Modem, vonage router or some other router is UPSTREAM in FRONT of your router. Call your ISP and ask, and if you can, have them put your DSL modem in bridge mode if it's not already. This way your router is the only firewall on the system. Repeat your tests...

* If you have a vonage router or some other router in front, you can DMZ the first router in the chain to the second router, then port forward from there....or use DMZ for testing.


Lastly....If anyone has trouble with their MediaSmart server not working remotely due to port issues, router issues, etc, please feel free to PM me (that's Private message for those of you that are wondering)

I've done extensive work and testing with the MediaSmart server and port forwarding, port changes, configuration, etc

I'll try my best to point you in the right direction and make sure you are properly testing and troubleshooting before you give up!

-Eric

_________________
http://www.tzo.com
The Reliable Dynamic DNS service

"Have you tried turning it off and on?" - Roy (IT Crowd)

Seems sometimes you have to turn Web Connectivity off, then back on in some cases for it to work.

I've heard of that happening once or twice, but not experienced it personally. Thanks for adding that as a troubleshooting tip!

I've also heard of the windows firewall somehow blocking it in the server... Had to log into the server using remote desktop and allow it through the windows firewall... Why/how it blocked the http port by default is beyond me.

Until you enable "Web Connectivity", the scope of http and https firewall on the server is set to Subnet Only, then when you enable it it makes those ports wide open. Sometimes that setting seems to stick on subnet only. I've not seen it totally blocked before.