Sign in to follow this  
Followers 0
g725s

Router won't UPnP for WHS 2011 Remote Web Access

144 posts in this topic

OK, that's good, so far. I'm not sure port 4125 is tested by the default ShieldsUP! probe. You may have to use the Use Specified Custom Port feature. You enter 4125 into the box just above the button, then click the Use Specified Custom Port button.

Share this post


Link to post
Share on other sites

OK, that's good, so far. I'm not sure port 4125 is tested by the default ShieldsUP! probe. You may have to use the Use Specified Custom Port feature. You enter 4125 into the box just above the button, then click the Use Specified Custom Port button.

 

Probe port 4125:

 

Port |Status | Protocol and Application

4125 | Stealth | Unknown Protocol for this port

 

Probe of port 443:

 

Port | Status | Protocol and Application

443 | OPEN! | https

 

Probe of port 80:

 

Port | Status | Protocol and Application

80 | Stealth | http

 

What would be the work around since my ISP (cox.net) blocks inbound on port 80?

Edited by g725s

Share this post


Link to post
Share on other sites

Is there a reason you really need to use port 80? If not, you can access your server from outside your LAN by using https:// instead of http://.

 

Remember, it's very likely you cannot do this from a computer on your LAN. It has to be from the Internet.

Share this post


Link to post
Share on other sites

The Site uses 443 so try and see without forwarding 80

Share this post


Link to post
Share on other sites

The Site uses 443 so try and see without forwarding 80

 

What is the purpose of port 80 then?

 

I can access the https:// signin page from my phone at this point.  I have intermittent data coverage from my home and was not able to check this earlier.  But I'm unable to signin from my phone.  It is saying username or password incorrect.  I have never tired accessing this page from my phone before.

Edited by g725s

Share this post


Link to post
Share on other sites

Port 80 is just the default, unprotected web page port. In reality, it's much better if you use HTTPS (port 443), because it's encrypted using SSL.

 

If you can't sign in, it may be because you haven't set the username you're trying to use to allow remote access. Use the DashBoard to check the User's permissions. Right-click on the Username, select View The Account Properties, then click on the Remote Web Access tab in the window that pops up. If nothing is checked there, you can't access.

Share this post


Link to post
Share on other sites

Port 80 is just the default, unprotected web page port. In reality, it's much better if you use HTTPS (port 443), because it's encrypted using SSL.

 

If you can't sign in, it may be because you haven't set the username you're trying to use to allow remote access. Use the DashBoard to check the User's permissions. Right-click on the Username, select View The Account Properties, then click on the Remote Web Access tab in the window that pops up. If nothing is checked there, you can't access.

 

It has been a while since I used this I forgot and was using my Windows Live account name and password to access the page.  If I use the client computer name I get to the page.  Thanks

Share this post


Link to post
Share on other sites

Ah. That would do it :)

 

It sounds like you're good to go then...

Share this post


Link to post
Share on other sites

Ah. That would do it :)

 

It sounds like you're good to go then...

 

Is there a workaround to access it from inside my LAN?

Share this post


Link to post
Share on other sites

Nope.  That's your router doing that.  Just RDP into the server, or go into the Site from IIS.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0