Mark, I've been reading that Verizon blocks port 80 also, thanks for the tip
I've never had an issue connecting to port 80 with my service, could be a regional thing? It could also be something that they do on a per-case basis, for people that abuse the system or are constantly transferring data?
yeshuas wrote:I'm pretty much a newbie when it comes to fooling around with the router settings like port forwding etc. is this the page that I would do that on and a little (a lot) of guidance would be appreciated
That would be the page you want. External port would be the port that you would be accessing from the web browser. So, something like http://example.homeserver.com:800
, you'd put 800 in the external port. Internal port would be 80 if you want to forward it to standard HTTP, if you want to use HTTPS, forward it to 443. The To IP Address would be the ip address of your homeserver system. The final check box will enable/disable the rule. If it's enabled, going to the homeserver URL followed by port number will redirect you to the address, disabled and it will just ignore things. You could also setup 2 rules, one for HTTP, one for HTTPS if you wanted as well. For port numbers, I'd suggest something in the range of 49152–65535 as they are not associated with any other service and would be less likely to be blocked. If you want a lower number, anything over 1024 should be safe as well, as it doesn't look like anything is a major service running on those. You can see Wikipedia
for port numbers.