Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Can't establish remote access RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have just upgraded a server running Windows Home Server 2003 to 2011 and put content back on it.  Using 2003, the Remote Access feature worked right out of the box with no problems, having obtained a domain name from Microsoft at homeserver.com.  Since the upgrade I cannot get the remote access feature to work—the wizard states that Port Forwarding is not enabled.

    I have manually enabled Port Forwarding on Ports 80, 443, and 4125 on my router.  In addition, I established a static IP address for the server 192.168.1.254.  No hardware has been changed in the upgrade.

    I have Verizon FiOS DSL, and am using the Actiontec_IGD router.  I can not connect to http://SERVER.homeserver.com from any location inside the network or from outside although I can connect to http://SERVER from inside the network.  UPnP is enabled on my router.   Finally, I successfully passed all aspects of the Microsoft Internet Connectivity Evaluation Tool

    Basic Internet Connectivity Test

    Network Address Translator Type

    Traffic Congestion Test

    TCP High Performance Test

    UPnP Support Test

    Multiple Simultaneous Connection States Test

     

    are all supported.  Please help as I am tearing what little hair I have left out.

    David

     

    Tuesday, November 8, 2011 2:31 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Firstly you actually only need Port 443 (https://) and optionally Port 80 (http://) - Port 4125 is not required at all. Have you re-registered your old domain name with the new Server? Is the name of your Server (SERVER) also the registered domain name SERVER.homeserver.com?

    From the Internet, try pinging your homeserver.com domain and see if you get the address allocated to your modem by Verizon.

    Also try running ShieldsUp at www.grc.com to confirm the ports are correctly forwarded to your server.

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
    • Marked as answer by HuntDR Wednesday, November 9, 2011 3:10 AM
    Tuesday, November 8, 2011 2:47 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Firstly you actually only need Port 443 (https://) and optionally Port 80 (http://) - Port 4125 is not required at all. Have you re-registered your old domain name with the new Server? Is the name of your Server (SERVER) also the registered domain name SERVER.homeserver.com?

    From the Internet, try pinging your homeserver.com domain and see if you get the address allocated to your modem by Verizon.

    Also try running ShieldsUp at www.grc.com to confirm the ports are correctly forwarded to your server.

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
    • Marked as answer by HuntDR Wednesday, November 9, 2011 3:10 AM
    Tuesday, November 8, 2011 2:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    How can you tell whether your internet IP is updating the windows live domain servers correctly via the WHS 2011 dynamic dns update feature?  I have been looking through all logs in this folder and am at a loss.  I can browse https://xxxx.homeserver.com on my LAN without any issue.  But  NSLOOKUPs are not reporting my internet IP as being associated with my xxxx.homeserver.com domain.

    c:\ProgramData\Microsoft\Windows Server\Logs\


    however, if I point to my https://xxxx.dyndns.org, i can see my remote access page (though the SSL cert doesn't match my xxxx.homeserver.com for which it was registered).  so my port forwarding is correct as well.

    Please advise.  This is becoming frustrating.

    Tuesday, November 8, 2011 3:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Phil--

    Thank you so much.  This was incredibly helpful.  Pinging the SERVER.homeserver.com address showed that Microsoft must have deallocated the name (don't know if that is the right term?).  I ended up registering with a private domain service.

    ShieldsUp has shown that the port 443 was in fact open.  I am waiting for my certificate request to be processed but this is more progress/answers than I have been able to find in a week of reading web sites and manuals.  I work slowly-- this isn't my day job-- so it may be a day or so before I know the final answer, but thanks for pointing me to a path forward.

    More later.

    David

    Wednesday, November 9, 2011 3:10 AM