locked
Another Remote Access Issue RRS feed

  • Question

  •  

    So far I cannot get remote access to work.  I tried to have WHS setup my router but that didn't work.  THe only items that get a green check mark are "verifying that your website is available on you home server" and "verifying that Remote Access is available on you your home server".  I forwarded ports 80, 443, and 4125 manually.  Is that all I would have to do?  Here is something might cause a hicup.  I have and Actiontec DSL modem for my Qwest service.  I then connect a Belkin Mimo router in to that.  My server and desktop pc are wired to the router and my notebook is wireless to it.  When I set up port forwarding for Utorrent, I had to forward the ports from my modem to the ip my router was receiving (192.168.0.2).  Then I to forward the same ports from the router to the desktop pc (192.168.2.4).  I set up the WHS this way as well.   Does this sound correct?  What am I missing?
    Tuesday, January 29, 2008 4:20 AM

All replies

  • Yes, you'll need to set up your modem/router configuration similar to how you got uTorrent to work.

     

    Questions:

    1) How are you checking that remote access is working (you need to be testing from an external source)?

    2) Does connecting to https://servername inside your network let you log into WHS?

    3) Can you add static routes to you DSL modem?

    Tuesday, January 29, 2008 5:10 AM
    Moderator
  • 1.  It says page cannot be loaded.  No option to log in, just seems like I typed a wrong address.

    2.  I used to get a log in option but was never able to log in.  Now I don't even get that.

    3.  How would I check this?

     

    Tuesday, January 29, 2008 2:59 PM
  • So there are more issues going on than your router.

     

    1) From a client on the LAN, try pinging the server (start --> run --> cmd, ping servername) - do you get 4 successful responses?

    2) From a client on the LAN, try pinging the server's IP address (as above)

    3) Repeat above for WLAN client, if you can

    4) Can you Remote Desktop into the server (start --> run --> mstsc, enter server name, user is Administrator, password is your WHS console password)? If so, can WHS browse the internet?

    5) Post the IP settings for a LAN client and WHS (start --> run --> cmd, ipconfig /all)

    Tuesday, January 29, 2008 6:20 PM
    Moderator
  • 1.  Yes

    2.  Yes

    3. Wife is away with the laptop.

    4.  I can get the log in screen but it gives me a message saying that I need to make sure that this account as rights through Terminal Services.  All my accounts have the remote access check box checked.

    5.  Desktop 196.168.2.5

    Belkin Router 196.168.2.1

    There is no mention of the WHS pc.  Buts its ip is 196.168.2.3 (it worked when I pinged it)

    Wednesday, January 30, 2008 2:11 AM
  • 4. Make sure you're entering Administrator as the username, and the WHS console password, NOT any of the user accounts you set up

    5. I need all the info from ipconfig /all

     

    Wednesday, January 30, 2008 2:19 AM
    Moderator
  • 4.  Yes I can log in with the administrator and yes I can browse the internet.

    5.  Here is everything:

     

     

    Microsoft Windows [Version 6.0.6000]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\HTPC>mstsc

    C:\Users\HTPC>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : HTPC-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Belkin

    Ethernet adapter Bluetooth Network Connection 3:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
    #3
       Physical Address. . . . . . . . . : 00-02-76-0C-AC-DB
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : Belkin
       Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
       Physical Address. . . . . . . . . : 00-1B-B9-8C-51-33
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::44fa:3d07:8a47:e9f5%8(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.2.5(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, January 27, 2008 10:52:27 PM
       Lease Expires . . . . . . . . . . : Saturday, March 07, 2144 5:19:05 AM
       Default Gateway . . . . . . . . . : 192.168.2.1
       DHCP Server . . . . . . . . . . . : 192.168.2.1
       DHCPv6 IAID . . . . . . . . . . . : 201333689
       DNS Servers . . . . . . . . . . . : 192.168.2.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

       Connection-specific DNS Suffix  . : Belkin
       Description . . . . . . . . . . . : isatap.Belkin
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.5%14(Preferred)
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : 192.168.2.1
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 7:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:28a9:14d5:3f57:fdfa(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::28a9:14d5:3f57:fdfa%9(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 12:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    C:\Users\HTPC>

     

    Wednesday, January 30, 2008 5:56 AM
  • Need ipconfig /all for your WHS as well.

     

    More things to check:

     

    1) on your client, browse to https://whsservername (NOT whatever your xxx.homeserver.com address is, the actual server name), what do you get?

    2) same thing with https://192.168.2.3

    Wednesday, January 30, 2008 6:43 AM
    Moderator
  • 1. WHen I type in the ip in IE& or the server name I get the same; there is a certificate error but i continue anyway and it works fine.

    2.  Here is WHS info

     

    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

    C:\Documents and Settings\Administrator>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : pettiths
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Belkin

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : Belkin
       Description . . . . . . . . . . . : Marvell Yukon 88E8050 PCI-E ASF Gigabit E
    thernet Controller
       Physical Address. . . . . . . . . : 00-11-11-EC-6B-37
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 192.168.2.3
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.2.1
       DHCP Server . . . . . . . . . . . : 192.168.2.1
       DNS Servers . . . . . . . . . . . : 192.168.2.1
       Lease Obtained. . . . . . . . . . : Monday, January 28, 2008 12:07:03 AM
       Lease Expires . . . . . . . . . . : Monday, January 18, 2038 7:14:07 PM

    C:\Documents and Settings\Administrator>

    Wednesday, January 30, 2008 7:02 AM
  • Cool, so internally everything looks good.

     

    What do you get when you try to acccess https://xxx.homeserver.com (whatever you've called your domain)? You'll need to be testing it from somewhere outside your network (get a friend to do it).

    Wednesday, January 30, 2008 7:27 AM
    Moderator
  • WHen my wife types the address from here work, the browser says it is loading for about 10 seconds then says the page cannot be found.

     

    I really appreciate all the help you are giving me.

     

    Thursday, January 31, 2008 12:03 AM
  • No problem. It's going to be difficult to troubleshoot this one, given the hops the request has to go through.

     

    1) Have you verified the 443 and 4125 port forwarding rules are set up exactly the same as your bittorent rule (with a different end-point of course)?

    2) When your wife pings xxxx.homeserver.com, does it resolve to the same IP address as your dsl modem's external IP?

    3) Does your ISP block 80 and 443?

     

    Thursday, January 31, 2008 3:35 AM
    Moderator
  • 1. The port forwarding is exactly the same.

    2.  how would she actually do this? (How does microsft know that xxx.homeserver.com goes to my server?)

    3.  I guess I need to call Qwest and find out.

     

    Thursday, January 31, 2008 5:17 AM
  • Ok, maybe we had a miscommuniction somewhere. "xxx" represents the name your chose to sign up for when you registered with homeserver.com. What is that name?

     

    Edit: Don't post the actual name here Smile I mean thats the address she needs to ping.

    Thursday, January 31, 2008 5:20 AM
    Moderator
  •  

    I understood that xxx was the server name.  What I ment was what does she actually do to when you say "ping".
    Thursday, January 31, 2008 3:17 PM
  • She starts a command prompt (Start→Run→cmd and press Enter). At the command prompt she types:

    ping <servername>.homeserver.com

    if you know your WAN IP address you can have her try to ping that as well, in case there's a DNS issue of some sort:

    ping 123.45.67.89

    As for testing your ports, you can use a site such as Shields Up!, which will allow you to probe ports on your network. You will need to perform this test from some PC on your network; it doesn't have to be your home server, however. If the result is that a port is STEALTH, that normally indicates that either your ISP is blocking that port, your router isn't configured to forward that port.
    Thursday, January 31, 2008 3:44 PM
    Moderator
  • Apologies. Ken's correct. I've talked about remote access t-shooting in so many posts, I forget which advice I've already given Wink

     

    Thursday, January 31, 2008 6:09 PM
    Moderator
  • I that the shields up! site and it seems that 80 443 are blicked by my ISP.  If this is correct, I guess I am out of luck.  I am switching internet providers in about 6 weeks, maybe it will work then.  Thanks to everyone for the tremendous help.

     

    Saturday, February 2, 2008 6:10 AM