A Digital Age Deserves A Digital Leader

Windows Home Server code name "Vail" Public Prev, RC & RTM

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby imnuts » Sun May 09, 2010 12:37 am

shreader wrote: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.
Image
PRO SUPREME
User avatar
Posts: 7457
Joined: Wed Mar 24, 2004 5:19 am
Location: Boothwyn, Pennsylvania
Real Name: Mark

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby yeshuas » Sun May 09, 2010 12:55 am

what about this page, anything jump out at you as being incorrect?

Image
Game Over!!!!!!!!
Image
ASUS Maximus V Gene MB
Windows 8 X64; Windows 7 X64; Windows 7 X86
Intel I5-3570K
16GB Corsair Vengeance Ram
eVGA GeForce GTX 550 TI
Corsair GS700 PS
1TB Seagate SATA 6.0Gb HD
Thermaltake Case
Software Development
User avatar
Posts: 5075
Joined: Wed Jan 17, 2007 3:29 pm
Location: Chicago, IL
Real Name: Daniel Schmidt

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby yeshuas » Sun May 09, 2010 1:02 am

HTTPS is listed here on this page,

Image

but on the single port forwarding page it isn't among the choices
Game Over!!!!!!!!
Image
ASUS Maximus V Gene MB
Windows 8 X64; Windows 7 X64; Windows 7 X86
Intel I5-3570K
16GB Corsair Vengeance Ram
eVGA GeForce GTX 550 TI
Corsair GS700 PS
1TB Seagate SATA 6.0Gb HD
Thermaltake Case
Software Development
User avatar
Posts: 5075
Joined: Wed Jan 17, 2007 3:29 pm
Location: Chicago, IL
Real Name: Daniel Schmidt

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby imnuts » Sun May 09, 2010 12:23 pm

Those two are ok, but the first pic you posted is the page that you want to set it up.
Image
PRO SUPREME
User avatar
Posts: 7457
Joined: Wed Mar 24, 2004 5:19 am
Location: Boothwyn, Pennsylvania
Real Name: Mark

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby yeshuas » Sun May 09, 2010 1:29 pm

imnuts wrote:Those two are ok, but the first pic you posted is the page that you want to set it up.


How does this change or setup look

Image
Last edited by yeshuas on Sun May 09, 2010 3:16 pm, edited 1 time in total.
Game Over!!!!!!!!
Image
ASUS Maximus V Gene MB
Windows 8 X64; Windows 7 X64; Windows 7 X86
Intel I5-3570K
16GB Corsair Vengeance Ram
eVGA GeForce GTX 550 TI
Corsair GS700 PS
1TB Seagate SATA 6.0Gb HD
Thermaltake Case
Software Development
User avatar
Posts: 5075
Joined: Wed Jan 17, 2007 3:29 pm
Location: Chicago, IL
Real Name: Daniel Schmidt

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby shreader » Sun May 09, 2010 3:08 pm

imnuts wrote:
shreader wrote: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?

>snip<


Do you have a commercial account?
After reading several posts across the net about people complaining about Verizon (residential service) blocking port 80 (mostly DSL though), I figured that must be my problem too.

This AM in the MS WHS/Vail forum a mod said:
That said, to the best of my knowledge Verizon blocks access to ports 80 and 443 for residential customers. Vail doesn't really let you move to different ports; for one thing the TS gateway is currently wired down to 443, so a Verizon FiOS internet connection really precludes the use of remote desktop or the dashboard via the Remote Access web site (even if you do change the ports in IIS).



Last night I filed a bug report on this problem @ Connect, hopefully it will be resolved in a future version/build.

*Edit: The WHS mod was WRONG!
Software Director
User avatar
Posts: 6538
Joined: Mon Aug 12, 2002 2:25 am
Location: Huntington Beach, CA

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby yeshuas » Sun May 09, 2010 3:19 pm

Is it or are you saying that no matter what one does, the issue will remain with remote access of the webwsite?
Game Over!!!!!!!!
Image
ASUS Maximus V Gene MB
Windows 8 X64; Windows 7 X64; Windows 7 X86
Intel I5-3570K
16GB Corsair Vengeance Ram
eVGA GeForce GTX 550 TI
Corsair GS700 PS
1TB Seagate SATA 6.0Gb HD
Thermaltake Case
Software Development
User avatar
Posts: 5075
Joined: Wed Jan 17, 2007 3:29 pm
Location: Chicago, IL
Real Name: Daniel Schmidt

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby shreader » Sun May 09, 2010 3:23 pm

I don't know, I'm going to try using Mark's tips on getting around the blocked port(s?) too, if they actually are.

Hopefully that will work for me also.
Software Director
User avatar
Posts: 6538
Joined: Mon Aug 12, 2002 2:25 am
Location: Huntington Beach, CA

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby yeshuas » Sun May 09, 2010 3:26 pm

shreader wrote:I don't know, I'm going to try using Mark's tips on getting around the blocked port(s?) too, if they actually are.

Hopefully that will work for me also.

So we shouldn't use the ports 443 and 80 for either the external or internal port?
Game Over!!!!!!!!
Image
ASUS Maximus V Gene MB
Windows 8 X64; Windows 7 X64; Windows 7 X86
Intel I5-3570K
16GB Corsair Vengeance Ram
eVGA GeForce GTX 550 TI
Corsair GS700 PS
1TB Seagate SATA 6.0Gb HD
Thermaltake Case
Software Development
User avatar
Posts: 5075
Joined: Wed Jan 17, 2007 3:29 pm
Location: Chicago, IL
Real Name: Daniel Schmidt

Re: Windows Home Server code name "Vail" Public Preview is now a

Postby shreader » Sun May 09, 2010 3:36 pm

I think he's only talking about Verizon FIOS residential lines.

The way he (the Mod) says it, it may not be totally confirmed either.

I'll give it a shot shortly.
Software Director
User avatar
Posts: 6538
Joined: Mon Aug 12, 2002 2:25 am
Location: Huntington Beach, CA

PreviousNext

Return to Alpha / Beta Software

Who is online

Users browsing this forum: No registered users and 0 guests