locked
WHS Connector RRS feed

  • Question

  • I am getting an error that there is a new WHS connector available, but I can not install it.  I am able to open the shared folder on the server from my computer and I able to access the server via the web.  I am unable to remote into the server and I can not connect through the WHS console.  I am running Power Pack 2.  I pinged my server and received the following:

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

    C:\Users\XXX>ping XXXXXXXXX

    Pinging www.surewest.net [64.8.70.120] with 32 bytes of data:
    Reply from 64.8.70.120: bytes=32 time=32ms TTL=243
    Reply from 64.8.70.120: bytes=32 time=31ms TTL=243
    Reply from 64.8.70.120: bytes=32 time=31ms TTL=243
    Reply from 64.8.70.120: bytes=32 time=31ms TTL=243

    Ping statistics for 64.8.70.120:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 31ms, Maximum = 32ms, Average = 31ms

    C:\Users\XXXX>

    Thank you.

    Friday, May 29, 2009 4:39 AM

Answers

  • As mentioned, change the settings on the client/server PC in the Properties of the LAN connection (and not on the router, since the router seems to bring the weird configuration stuff).
    To ensure, you keep the Internet connection with manual configuration, your IP addresses must remain in the same address range as the router (as explained before), the subnet mask must be identical, the Gateway AND the DNS server should point to the address of the router.

    I am not fully sure, that the DHCP reservation should contain the server, because it could also mean, that you reserved these addresses manually.
    Or it means, that the server is not in the proper range at all by whatever reason (if the above page only contains the automatically assigned addresses), so you should enter the ipconfig /all command on your server and post that output also here.
    If you are not comfortable with setting manual IP addresses, you can try to replace that domain in the router by something without an Internet capable name like "workgroup".

    Best greetings from Germany
    Olaf
    Monday, June 1, 2009 7:51 PM
    Moderator

All replies

  • I am getting an error that there is a new WHS connector available, but I can not install it.  I am able to open the shared folder on the server from my computer and I able to access the server via the web.  I am unable to remote into the server and I can not connect through the WHS console.  I am running Power Pack 2.  I pinged my server and received the following:

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

    C:\Users\XXX>ping XXXXXXXXX

    Pinging www.surewest.net [64.8.70.120] with 32 bytes of data:
    Reply from 64.8.70.120: bytes=32 time=32ms TTL=243
    Reply from 64.8.70.120: bytes=32 time=31ms TTL=243
    Reply from 64.8.70.120: bytes=32 time=31ms TTL=243
    Reply from 64.8.70.120: bytes=32 time=31ms TTL=243

    Ping statistics for 64.8.70.120:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 31ms, Maximum = 32ms, Average = 31ms

    C:\Users\XXXX>

    Thank you.


    Is this a home built server or is this an OEM Server like an HP MediaSmart?

    If this is a home built server, is it possible that you have an NVIDIA video card on the server? This is a known issue with NVIDIA
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Friday, May 29, 2009 5:20 AM
    Moderator
  • It is home built with an Intel motherboard with an integrated graphics card.  My internet service provider has changes but it was working fine until yesterday I have not made any changes to the WHS in the past six months.
    Friday, May 29, 2009 12:54 PM
  • The ping is going to an external site (if XXXXXXXX represents the name of your home server inhouse) - which seems to point to a wrong DNS configuration, which causes your internal server name to be resolved to an external host in the Internet.
    This can be a DNS entry in the clients IP configuration pointing directly to the DNS server of your ISP, this can be a DNS search suffix entry in the IP configuration (often set by the router).
    Please post the output of the command
    ipconfig /all
    an a client PC.
    Can you connect via Remote Desktop, if you use the internal IP address of your home server?
    Best greetings from Germany
    Olaf
    Friday, May 29, 2009 1:27 PM
    Moderator
  • I can not via Remote Desktop.

    Here is the output:

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

    C:\Users\Brad>ipconfig/all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : TheBase
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : kc.surewest.net

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : kc.surewest.net
       Description . . . . . . . . . . . : Marvell Yukon 88E8039 PCI-E Fast Ethernet
     Controller
       Physical Address. . . . . . . . . : 00-1E-90-0C-41-03
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::1c2f:de82:4900:1a5%8(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Thursday, May 28, 2009 11:43:07 PM
       Lease Expires . . . . . . . . . . : Saturday, May 30, 2009 11:43:06 AM
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 64.126.4.189
                                           64.126.4.193
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

       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:ab:1a15:b838:bb42(Prefer
    red)
       Link-local IPv6 Address . . . . . : fe80::ab:1a15:b838:bb42%9(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 9:

       Connection-specific DNS Suffix  . : kc.surewest.net
       Description . . . . . . . . . . . : isatap.kc.surewest.net
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.103%18(Preferred)
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : 64.126.4.189
                                           64.126.4.193
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\Users\Brad>
    Saturday, May 30, 2009 4:13 AM
  • DNS Suffix Search List. . . . . . : kc.surewest.net
    Connection-specific DNS Suffix  . : kc.surewest.net
    DNS Servers  . . . . . . . . . : 64.126.4.189
                                          64.126.4.193

    The first two entries must go, since they attach kc.surewest.net to the name of your server before even resolving is attempted, so each resolution attempt via DNS is done via your ISP, which cannot deliver the proper internal address. And instead of responding with nothing, which would be right, it responds with the www.surewest.net IP address, which is not helpful.
    On top replace the DNS servers with the address of your router 192.168.1.1.
    This configuration change can either be done in the DHCP settings of your router, or by assigning fixed IP addresses to clients and server in their local settings.
    Remote desktop should work for the internal IP address of the server.

    Best greetings from Germany
    Olaf
    Saturday, May 30, 2009 10:44 AM
    Moderator

  •    
    Optional Settings
    (required by some Internet Service Providers)
      Host Name:
        Domain Name:
        MTU: Size:
       
    Network Setup  
    Router IP   IP Address: . . .
        Subnet Mask:
       
    DHCP Server Setting   DHCP Server: Enabled Disabled
        Start IP Address: 192 . 168 . 1. 
        Maximum Number of Users:
        IP Address Range: 192 . 168 . 1. 100 to 149
        Client Lease Time:   minutes (0 means one day)
        Static DNS 1: . . .
        Static DNS 2: . . .
        Static DNS 3: . . .
        WINS: . . .

    I see the output of ipconfig lists the name of my ISP, but when I open the Set-up page of my router (linksys WRT310N), I do not see where I can make the recommended changes.  I have attempted to include a screen shot of the Basic Setup page of the router.

    Thanks again.

    Update:

    I was able to see these settings in the router, but I do not know where it is possible to change them:

    Firmware Version: v1.00.4 Jan 3, 2008
    Current Time: Sun, 31 May 2009 00:17:38
    Internet MAC Address: 00:1E:90:0C:41:03
    Host Name:  
    Domain Name: kc.surewest.net

    Internet Connection
    Connection Type: Automatic Configuration - DHCP
    Internet IP Address: 66.64.120.188
    Subnet Mask: 255.255.254.0
    Default Gateway: 66.64.120.1
    DNS1: 192.168.1.1
    DNS2: 64.126.4.189
    DNS3: 64.126.4.193
    MTU: 1500
    DHCP Lease Time: 2 Days

    Sunday, May 31, 2009 5:16 AM
  • Hi,
    I also don't know where on that router the settings can be adjusted (maybe its in the manual?), since the pure DHCP settings look ok.
    Is the entry "domain name" somewhere in an editable field of the router?

    Alternatively you could try to set fixed IP addresses to the server and the clients in the properties of the network connection under TCP/IP settings.
    Use IP addresses different for each machine in ranges between 192.168.1.2 and .99 (or .150 to .254), the subnet mask 255.255.255.0, Default Gateway 192.168.1.1, DNS Server 192.168.1.1.
    Click the  Advanced button and check the DNS tab for remains of the surewest.net entry and remove them, if necessary.
    On the WINS tab I recommend to select to Enable NEtBIOS over TCP/IP.
    After finishing the reconfiguration boot the server and the clients and wait some time.
    On the clients you may have to run discovery.exe in C:\Program Files\Windows Home Server to reestablish the connection to the server.
    Best greetings from Germany
    Olaf
    Sunday, May 31, 2009 8:59 PM
    Moderator
  • Hello:

    I was able to find these fields in my router settings:

    DHCP Reservation
    Select Clients from
    DHCP Tables
    Client Name Interface IP Address MAC Address Select
    D51VKVF1 LAN 192.168.1.102 00:23:08:0C:E0:1A
    HP-Officejet LAN 192.168.1.104 00:21:5A:A1:CE:61
    TheBase LAN 192.168.1.105 00:1E:90:0C:41:03
    Add Clients

    Manually Adding Client
    Enter Client Name Assign IP Address To This MAC Address
    192 . 168 . 1. 

    Clients Already Reserved
    Client Name Assign IP Address To This MAC Address MAC Address
    Save Settings Cancel Changes Refresh Close


    The first item is netbook, the second a printer, and the third is my desktop.  My server is not listed...should it be?  I am able to assign a new client to a specific IP address and a MAC address if I desire.  I am no longer able to open my server's website, but I am able to open the shard folders on my desktop.  I attempted to assign separate IP addresses for my network, but I lost my internet connection and the result of my tinkering and I reset everything back to regain internet access.  I can set the domain name of my router to what ever I want, but if I leave the field blank, it defaults to my name of my ISP.  Should I reset the router?  That can be painful, I know, but I do not know what else to do?

    Thank you again for your assistance.
    Monday, June 1, 2009 4:48 AM
  • As mentioned, change the settings on the client/server PC in the Properties of the LAN connection (and not on the router, since the router seems to bring the weird configuration stuff).
    To ensure, you keep the Internet connection with manual configuration, your IP addresses must remain in the same address range as the router (as explained before), the subnet mask must be identical, the Gateway AND the DNS server should point to the address of the router.

    I am not fully sure, that the DHCP reservation should contain the server, because it could also mean, that you reserved these addresses manually.
    Or it means, that the server is not in the proper range at all by whatever reason (if the above page only contains the automatically assigned addresses), so you should enter the ipconfig /all command on your server and post that output also here.
    If you are not comfortable with setting manual IP addresses, you can try to replace that domain in the router by something without an Internet capable name like "workgroup".

    Best greetings from Germany
    Olaf
    Monday, June 1, 2009 7:51 PM
    Moderator
  • Olaf-

    I was prepared to spend the good part of the night working to the resolve this is, but it turns out that it was unnecessary.  I changed the domain name from kc.surewest.net to workgroup in the router settings and everything seems to be working correctly now.  I am currently running a back-up now from the WHS console and the remote access is working as well.

    I really appreciate you guiding me through this problem.

    Danke schon.

    Brad
    Tuesday, June 2, 2009 2:18 AM