locked
Cannot get WHS to configure router for remote access RRS feed

  • Question

  • I have a new home server and I run a Trendnet tew-432brp router.  I configured the port forwarding on it and ran the HomeServer router setup.  It passes the first 2 tests and fails on the third test to access the homeserver from the internet.  I can get to the homeserver by using the IP address.  When I do I get a warning about the certifigate not being valid for the connecton.  On the HomeServer with the remote access turned on I can not access any web sites.  I also can not get it to log into my windows alive account to create a domain name.  Any one have any Ideas?
    Saturday, April 11, 2009 8:34 PM

Answers

  • I have a new home server and I run a Trendnet tew-432brp router.  I configured the port forwarding on it and ran the HomeServer router setup.

    You should either A) do the port forwarding yourself or B) let WHS do it for you.  Don't do both.

    It passes the first 2 tests and fails on the third test to access the homeserver from the internet.  I can get to the homeserver by using the IP address.

    When you say your IP address, do you mean your internal one (usually starting with 192.168) or your external one (provided by your ISP)?

    When I do I get a warning about the certifigate not being valid for the connecton.  On the HomeServer with the remote access turned on I can not access any web sites.  I also can not get it to log into my windows alive account to create a domain name.  Any one have any Ideas?

    Can you go to Shields Up!, do a scan for ports 80, 443, and 4125, then post the results back here?
    Saturday, April 11, 2009 9:14 PM
    Moderator
  • 80 ; Stealth ; http ; World Wide Web HTTP

    443 ; Stealth ; https ; http protocol over TLS/SSL

    4125 ; Closed ; Unknown Protocol for this port ; Unknown Application for this port
    Having ports 80 and 443 reported as stealth, if you are sure that your router is correctly configured to forward those ports to your server, indicates that something is blocking them. "Something" is almost always your ISP blocking common ports to prevent residential customers from running servers on their network.

    If you are certain you have correctly configured your router to forward the appropriate ports to your server, you should contact your ISP to find out if they do block ports, and if there is any way you can arrange to have them unblocked. (Note that getting those ports opened up may require you to purchase a business internet plan from your ISP.)

    I'm not on the WHS team, I just post a lot. :)
    Sunday, April 12, 2009 1:49 PM
    Moderator

All replies

  • I have a new home server and I run a Trendnet tew-432brp router.  I configured the port forwarding on it and ran the HomeServer router setup.

    You should either A) do the port forwarding yourself or B) let WHS do it for you.  Don't do both.

    It passes the first 2 tests and fails on the third test to access the homeserver from the internet.  I can get to the homeserver by using the IP address.

    When you say your IP address, do you mean your internal one (usually starting with 192.168) or your external one (provided by your ISP)?

    When I do I get a warning about the certifigate not being valid for the connecton.  On the HomeServer with the remote access turned on I can not access any web sites.  I also can not get it to log into my windows alive account to create a domain name.  Any one have any Ideas?

    Can you go to Shields Up!, do a scan for ports 80, 443, and 4125, then post the results back here?
    Saturday, April 11, 2009 9:14 PM
    Moderator
  • Can you go to Shields Up!, do a scan for ports 80, 443, and 4125, then post the results back here?
    Since I'm having the same problem, I hope you don't mind my posting my findings from ShieldsUP! as well... I got the following:
    80 ; Stealth ; http ; World Wide Web HTTP

    443 ; Stealth ; https ; http protocol over TLS/SSL

    4125 ; Closed ; Unknown Protocol for this port ; Unknown Application for this port
    Any aid would be much appreciated!
    Sunday, April 12, 2009 11:08 AM
  • 80 ; Stealth ; http ; World Wide Web HTTP

    443 ; Stealth ; https ; http protocol over TLS/SSL

    4125 ; Closed ; Unknown Protocol for this port ; Unknown Application for this port
    Having ports 80 and 443 reported as stealth, if you are sure that your router is correctly configured to forward those ports to your server, indicates that something is blocking them. "Something" is almost always your ISP blocking common ports to prevent residential customers from running servers on their network.

    If you are certain you have correctly configured your router to forward the appropriate ports to your server, you should contact your ISP to find out if they do block ports, and if there is any way you can arrange to have them unblocked. (Note that getting those ports opened up may require you to purchase a business internet plan from your ISP.)

    I'm not on the WHS team, I just post a lot. :)
    Sunday, April 12, 2009 1:49 PM
    Moderator
  • Actually, this one was my bad... or WHS's.

    WHS initially failed the second test as well -- couldn't configure my router through uPnP. I switched routers, and it could. Apparently, even though it said it had configured my router, it hadn't mapped a single port. Which apparently lead to the third test failing.

    Since kariya21 asked for the results from ShieldsUP!, I pasted those, and since ShieldsUP! was pretty much congratulating me on those stealthed ports, I thought that was actually a good thing... ...guess it wasn't. (I know my way around computers most of the time, but I'm lost in advanced networking situations...)

    Taking a look at my router's settings, then manually forwarding the ports that WHS apparently didn't forward even though it said it did, seems to have opened those ports. ShieldsUP! Seems to not like that idea much and complains that they aren't stealthed anymore. On the other hand... I can now remotely connect to my home server.

    All in all, it took me a week or so to get the thing running properly (the remote access wasn't the only problem I encountered), which I think is quite a bit for a pre-built system intended for home users. Then again, if it'll keep running as it does now, a week'll have been more than worth it!

    Thanks kariya21 for pointing at the ports, and thanks Ken Warren for pointing out what was wrong with them. My WHS problems are solved!

    Monday, April 13, 2009 6:35 PM
  • Blame your router(s) for this one.
    I'm not on the WHS team, I just post a lot. :)
    Monday, April 13, 2009 7:35 PM
    Moderator
  • Actually, this one was my bad... or WHS's.

    WHS initially failed the second test as well -- couldn't configure my router through uPnP. I switched routers, and it could. Apparently, even though it said it had configured my router, it hadn't mapped a single port. Which apparently lead to the third test failing.

    Since kariya21 asked for the results from ShieldsUP!, I pasted those, and since ShieldsUP! was pretty much congratulating me on those stealthed ports, I thought that was actually a good thing... ...guess it wasn't.

    Nope, it wasn't. :)  That website is all about security.  Most of the time having ports show up as Stealth is good, but not in this case.  After all, if the ports are Stealth, no one can the server (not even you).

    (I know my way around computers most of the time, but I'm lost in advanced networking situations...)

    Taking a look at my router's settings, then manually forwarding the ports that WHS apparently didn't forward even though it said it did, seems to have opened those ports. ShieldsUP! Seems to not like that idea much and complains that they aren't stealthed anymore. On the other hand... I can now remotely connect to my home server.

    All in all, it took me a week or so to get the thing running properly (the remote access wasn't the only problem I encountered), which I think is quite a bit for a pre-built system intended for home users. Then again, if it'll keep running as it does now, a week'll have been more than worth it!

    Thanks kariya21 for pointing at the ports, and thanks Ken Warren for pointing out what was wrong with them. My WHS problems are solved!

    Tuesday, April 14, 2009 4:43 AM
    Moderator