Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Remote Access Problem with Windows Home Server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Someone please help!! I've racked my brain for days trying to get this to work, Currently my WHS is completely updated with Power Pack 3.

    While trying to get Remote Access to work, It always gives me a Green Check, and Yellow triangle (when trying to configure via UPnP) and a red X, when it tries to verify that it can see my domain from outside the router.

    The current router I use is a Linksys BEFSR41 V.3 that does support UPnP but I've manually configured my ports.

    HTTP: 80
    HTTPS:443
    RDP: 4125

    I've configured these port as per every guide I can find on the internet about this particular router, and all guides I've found out on this particular issue, and it's still not working. I've downloaded a Port checker software, and when I run it in WHS it says the ports are blocked (I have no idea where this could be blocked at, as I use Comcast Business class, and they say they don't block anything)

    I'm at a complete loss to how to get this to work. I've disabled, restarted the server, and re-run the wizard, and it keeps giving me the same error. If anyone has any guidance, or wisdom to share, it'd be much appreciated!
    Saturday, February 27, 2010 9:41 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I haven't disabled the firewall, as I thought that wouldn't affect the the port forwarding on the router. No, there's no applications, other than the ones from Microsoft that are installed on the server. I've already contacted my ISP, and they swear, up and down that they don't block any ports.

    Question, would a gateway affect this being able to work?

    My current outbound set up is as follows:

    Gateway>Router>Switch>Computer

    Any help is appreciated
    If the gateway has a built-in router (which it probably does), yes.  In that case, you should try putting either the gateway or the router in "bridge mode" (effectively eliminating one of the routers).  If that's not possible, you will probably have to forward the ports from the gateway to the router, then from the router to the server.
    • Marked as answer by Lindseytw Sunday, February 28, 2010 3:29 AM
    Sunday, February 28, 2010 2:52 AM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Someone please help!! I've racked my brain for days trying to get this to work, Currently my WHS is completely updated with Power Pack 3.

    While trying to get Remote Access to work, It always gives me a Green Check, and Yellow triangle (when trying to configure via UPnP) and a red X, when it tries to verify that it can see my domain from outside the router.

    The current router I use is a Linksys BEFSR41 V.3 that does support UPnP but I've manually configured my ports.

    HTTP: 80
    HTTPS:443
    RDP: 4125

    I've configured these port as per every guide I can find on the internet about this particular router, and all guides I've found out on this particular issue, and it's still not working. I've downloaded a Port checker software, and when I run it in WHS it says the ports are blocked (I have no idea where this could be blocked at, as I use Comcast Business class, and they say they don't block anything)

    I'm at a complete loss to how to get this to work. I've disabled, restarted the server, and re-run the wizard, and it keeps giving me the same error. If anyone has any guidance, or wisdom to share, it'd be much appreciated!
    Have you completely disabled uPnP on that router (so that your server can't do anything to it)?  Did you double-check the IP address of your server and make sure you have the exact same IP address in the port forward section of your router?  Please go to Shields Up! and run a custom port scan for 80, 443, and 4125, then post the results back here.
    Saturday, February 27, 2010 10:39 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, I've gone through my router a number of times to double check the IP Address for the server. (it is static set)

    I have also completely disabled UPnP support on the router.

    Here is what my shields up! test, run from the server displayed:

    Results from scan of ports: 80, 443, 4125

        0 Ports Open
        0 Ports Closed
        3 Ports Stealth
    ---------------------
        3 Ports Tested

    ALL PORTS tested were found to be: STEALTH.

    TruStealth: FAILED - ALL tested ports were STEALTH,
                       - NO unsolicited packets were received,
                       - A PING REPLY (ICMP Echo) WAS RECEIVED.

    Hope this helps.
    Sunday, February 28, 2010 12:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, I've gone through my router a number of times to double check the IP Address for the server. (it is static set)

    I have also completely disabled UPnP support on the router.

    Here is what my shields up! test, run from the server displayed:

    Results from scan of ports: 80, 443, 4125

        0 Ports Open
        0 Ports Closed
        3 Ports Stealth
    ---------------------
        3 Ports Tested

    ALL PORTS tested were found to be: STEALTH.

    TruStealth: FAILED - ALL tested ports were STEALTH,
                       - NO unsolicited packets were received,
                       - A PING REPLY (ICMP Echo) WAS RECEIVED.

    Hope this helps.
    Since the IP address is correct, the only options left that I can think of are A) your ISP is blocking the ports or B) the firewall on your server is misconfigured.  Have you tried completely disabling Windows Firewall on the server?  Have you installed any applications on the server (which, by the way, is unsupported)?
    Sunday, February 28, 2010 1:53 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I haven't disabled the firewall, as I thought that wouldn't affect the the port forwarding on the router. No, there's no applications, other than the ones from Microsoft that are installed on the server. I've already contacted my ISP, and they swear, up and down that they don't block any ports.

    Question, would a gateway affect this being able to work?

    My current outbound set up is as follows:

    Gateway>Router>Switch>Computer

    Any help is appreciated
    Sunday, February 28, 2010 2:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I haven't disabled the firewall, as I thought that wouldn't affect the the port forwarding on the router. No, there's no applications, other than the ones from Microsoft that are installed on the server. I've already contacted my ISP, and they swear, up and down that they don't block any ports.

    Question, would a gateway affect this being able to work?

    My current outbound set up is as follows:

    Gateway>Router>Switch>Computer

    Any help is appreciated
    If the gateway has a built-in router (which it probably does), yes.  In that case, you should try putting either the gateway or the router in "bridge mode" (effectively eliminating one of the routers).  If that's not possible, you will probably have to forward the ports from the gateway to the router, then from the router to the server.
    • Marked as answer by Lindseytw Sunday, February 28, 2010 3:29 AM
    Sunday, February 28, 2010 2:52 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's a SMC 8014 Gateway, and I believe you're correct, it does have a built in router. How would I go about "daisy chaining" the forwarding on the built-in router in the gateway, to my network router?
    Sunday, February 28, 2010 3:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you Kariya21, for your help. These has seemed to solve the issue. I managed to log into the gateway, and forward these requests to the internal router, then on the internal router, forward these request to the server. I was able to pull up the website from my blackberry, but unable to access it from the internal network. I assume all the port forwarding is at work, preventing this. Thank you for your time.
    Sunday, February 28, 2010 3:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you get specific steps to help solve the problem with your smc-8014?  I seem to be having the same problem.  Comcast just switched me to this modem and now I am unable to configure remote access.  Any advice would be appreciated
    Friday, May 28, 2010 12:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I seem to be having the same problem with my smc gateway.  can you forward to me the steps you took to solve the problem? 

    Comcast is telling me that it absolutely cant be done with this modem. 

     

    Thanks

    Friday, May 28, 2010 4:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here's a way you might want to try gateway(smc gateway) ------new router (make sure it can port forward)---------hooked into whs/clients

    forward a ____ port like 442 to port 443 or something like 8443 to port 443 and so on with the others ports that you know

    so your homeserver remote address looks like https://name.homeserver.com:8443

    turn off upn in both routers if possiable, manually configer the ports in the "new router" what you are doing is going thru port 8443..... the the "new router" turns port 8443 to your whs port 443 ...... you should be able to access from your own home network thru a webpage.... sometimes it takes doing the "console" re,ote access again  but don't worry about the website they give you because it wont have the forwarded port showing in the console.

    hope this helps and yes IPS's lie about closing port 80 and 443

    my answers or disscusion points might not always right but they may have points not yet looked at. If you feel insulted by any points this is not my intention, i'm trying to help
    • Edited by Jackal696 Friday, May 28, 2010 7:58 PM port mix up
    Friday, May 28, 2010 7:57 PM