locked
Remote Access Trouble - IP's, VoIP and Confusion RRS feed

  • Question

  • Hello All,
    My first post, but have been reading for a while, so your patience is requested & appreciated.

    Set up the Acer Aspire easyStore H340 and it works great on my home network. I can successfully access it through WHS Console on my WLAN via a laptop running Vista Home Premium & a desktop running XP MCE 2005.

    My current local connection setup (from the wall to WHS box) is as follows:
    Cable Modem => Ooma VoIP => Rosewill Router RNX-N4PS => WHS box

    After enabling port forward TCP for port 443 only, I turned on remote access, and got these results:
    • Verifying that your remote website is available local (OK)
    • Configuring your router using UPnP standards (OK)
    • Verifying that your remote website is available from the internet (OK)

    Even though these test results indicate that "remote website is available", when I navigate to the domain name while on my local network, I get the message: "The connection has timed out." I thought this was only due to that fact that I was on my local network, because I was able to access the remote website by entering the servers IP address directly into my browser, but apparently I was wrong.

    The trouble became clear when I couldn't access the WHS machine while away last week...when attempting to connect via the domain name set up through the WHS console remote access settings, the browser read: "The connection has timed out."

    Sorry for rambling on, but some interesting things occur when I enter the IP addresses of the various equipment on my home network while also connected through the local network. The website displayed as the result of entering each domain name (or each piece of equipment's IP) is as follows:

    • https://mysite.homeserver.com => "The connection has timed out."
    • http://mysite.homeserver.com => Ooma Setup Page
    • https://WHS.IP.Address => WHS Remote Webpage
    • http://WHS.IP.Address => WHS Remote Webpage
    • http://WHS.Remote.Website.IP.Address => Ooma Setup Page
    • http://Ooma.IP.Address => Ooma Setup Page (Ooma setup page reports the same IP for the "Modem" as the WHS Console reports for the "Website IP Address")

    Any help is greatly appreciated!
    Wednesday, August 19, 2009 4:19 AM

All replies

  • Hi,
    if there is double NAT involved, this is not supported by Windows Home Server.
    Either you can configure the modem in bridged node, or you manage to forward the appropriate ports between all devices in the chain.

    On the other side, accessing the own network from own network via Internet is not supported by some routers, and your chain may not be an exception here.
    So you should try to access WHS from outside of your home to get reliable verification.

    Best greetings from Germany
    Olaf
    Wednesday, August 19, 2009 12:34 PM
    Moderator