Jump to content
RESET Forums (homeservershow.com)

Router won't UPnP for WHS 2011 Remote Web Access


Recommended Posts

Would love to see how you managed that. All the docs I've seen seems to point to the server as the one who does the redirecting.

 

I'd like to close port 80, but if possible, retain auto-redirect capability.

Link to post
Share on other sites
  • Replies 143
  • Created
  • Last Reply

Top Posters In This Topic

  • g725s

    46

  • ikon

    45

  • jmwills

    28

  • oj88

    13

Top Posters In This Topic

Popular Posts

4125 isn't needed .... despite what people may say.   As for port 80, I have Cox as well. They DEFINITELY block port 80 by default. You can get around this by buying the business package...... And

Yes, WPA2 Personal + AES -> that's the ticket.   And, yes, use https://. It's more secure. Gradually, web sites are migrating to https anyway. Http is just too vulnerable.

My feeling is that, today, everyone should use https everywhere they can.

I just removed Port 80 being forwarded to the server.

Didn't work. With port 80 not forwarded but allowed in the firewall, I get a "This page can't be displayed".

 

Ah well. I'll just go straight to https.

Link to post
Share on other sites

I still only use https is what I'm saying.  Never did use http so the term "redirect" on my part was really incorrect.  I think the real term is "Alternate Access Mapping".

Link to post
Share on other sites
Drashna Jaelre

I still only use https is what I'm saying.  Never did use http so the term "redirect" on my part was really incorrect.  I think the real term is "Alternate Access Mapping".

You only need to use HTTPS. In fact, the /remote site REQUIRES HTTPS, so there is no reason to use anything else.

 

As long as as the https:// site works, then you're fine. Regardless of what the server says. 

 

If it really does bug you ... then you can spend 2-4x what your'e paying now to get lower downstream but higher upstream, no data caps and no blocked ports, and go with Cox Business. It's worth calling to see what the pricing is.

Link to post
Share on other sites
Drashna Jaelre

My feeling is that, today, everyone should use https everywhere they can.

Absolutely.

 

Is why my website forcibly redirects to HTTPS. :)

Link to post
Share on other sites

Absolutely.

 

Is why my website forcibly redirects to HTTPS. :)

Exactly the point I was making. For automatic redirect to work, it seems necessary to have port 80 open and forwarding just enough for the server to respond and redirect (forcibly) the requesting client to the https page.
Link to post
Share on other sites

Exactly the point I was making. For automatic redirect to work, it seems necessary to have port 80 open and forwarding just enough for the server to respond and redirect (forcibly) the requesting client to the https page.

 

I would expect you could set this up in the router, as long as your ISP doesn't block port 80. You could simply have all port 80 requests forwarded in the router to your server's IP, but on port 443. I realise not every router offers this capability, but I think most do these days.

Link to post
Share on other sites

I would expect you could set this up in the router, as long as your ISP doesn't block port 80. You could simply have all port 80 requests forwarded in the router to your server's IP, but on port 443. I realise not every router offers this capability, but I think most do these days.

Thank you. It's clear now. :)

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

×
×
  • Create New...