locked
Remote Access/Port Forwarding Issues RRS feed

  • Question

  • I have just recently begun messing with the WHS platform. I found out that I needed to do some port forwarding to get the remote access to work so I begun by forwarding ports 80 and 443 from my router. I then went to canyouseeme.org to check if those ports where open. I found out that my ISP--Cox Communications--blocks port 80. I did a bit of googling and found out that if I head to the IIS manager, then sites, then default website, I would be able to change the ports the remote access web-page uses. I ended up changing "browse (http)" to 8090, "Browse (http) [the second one]" to 55025, "Browse https" to 56025, and left "Browse (HTTPS) [the second one]" at 443. I forwarded all 4 ports just incase only to realize that they were still blocked! I remembered that I might have to add access to them from the Windows Firewall. I ended up creating the permissions and I am now able to see those ports! I am however, having a problem. I cannot access the remote webpage unless I change http://xyxy.homeserver.com to httpS://xyxy.homeserver.com. I believe that because of this, my launchpad is not connecting either! I did so much messing around before I was able to gain access to the remote access web page that I really don't even remember every step I took. I have no idea what I could have done wrong as I am able to see every port that is forwarded? 


    Tuesday, January 4, 2011 6:20 AM

All replies

  • It would have been a lot easier to handle the port forwarding rules in the router. I have my router setup to route external port 8080 to internal port 80 on 192.168.1.2 and external port 8443 to internal port 443 192.168.1.2. This way the Windows Firewall rules and IIS port assignments remain the same.
     
    "alihashemi2002" wrote in message news:a2906efb-3ab5-4126-852e-b4e469ad1df1...

    I have just recently begun messing with the WHS platform. I found out that I needed to do some port forwarding to get the remote access to work so I begun by forwarding ports 80 and 443 from my router. I then went to canyouseeme.org to check if those ports where open. I found out that my ISP--Cox Communications--blocks port 80. I did a bit of googling and found out that if I head to the IIS manager, then sites, then default website, I would be able to change the ports the remote access web-page uses. I ended up changing "browse (http)" to 8090, "Browse (http) [the second one]" to 55025, "Browse https" to 56025, and left "Browse (HTTPS) [the second one]" at 443. I forwarded all 4 ports just incase only to realize that they were still blocked! I remembered that I might have to add access to them from the Windows Firewall. I ended up creating the permissions and I am now able to see those ports! I am however, having a problem. I cannot access the remote webpage unless I change http://xyxy.homeserver.com to httpS://xyxy.homeserver.com. I believe that because of this, my launchpad is not connecting either! I did so much messing around before I was able to gain access to the remote access web page that I really don't even remember every step I took. I have no idea what I could have done wrong as I am able to see every port that is forwarded?

     
    Tuesday, January 4, 2011 11:24 PM