locked
Problems with Connector and Backups. RRS feed

  • Question

  • Ok, I had one machine set up from the PP1 Beta that I was testing out. I will refer to it as PC1 and it was named WHS. I wasn't happy with the performance of it and I set up a second machine and tried it out. I'm will refer to it as PC2 and it was named Server. I had both PCs on my network at the same time, but with PC1 as the main unit. Fast forward. The trial ran out on PC1. No problem. I had already copies the data onto PC2 (which I am installing the OEM version on shortly, as I am happy with the performance.) The drop dead date for PC1 was yesterday, so I decommissioned it yesterday. Today I changed the name of the PC2 to the WHS and changed the IP address to the one I was using for PC1. Of course, the Connector icons in the tollbar did not recognize the change. On one client machine, I reran the Connector software from the WHS. It went through the Connector set up and on the screen "Now Configuring Your Computer" there is a Failed X beside the "Configuring computer backup." and it says "Ensure that your Home Server is powered on and connected to the network."

    I run the Troubleshooter (which if I try to run it from a DOS prompt, I get an error "'ClientTroubleshooter.exe' is not recognized as an internal or external command, operable program or batch file.") and it give me the following problems listed:

    "The version of the Connector software does not match the version of Windows Home Server." This is strange as I deleted the software from the client computer and loaded it from the WHS web page.

    "Cannot connect to the server secure internal Web site" Funny, I can from IE.

    "A firewall product is found on the home computer" Yupe, the Window one. It says that I have One Care loaded, but I don't.

    I can also reach the server's web page from the http://whs or http:/whs:55000, which is where I launched the Connector install software from.

    I can "ping WHS" and get the vaild IP address back and responces.
    I can "ping -a WHS" and the vaild IP address and replies back.
    I can "net view whs" and see the shares.
    When I first did a "nslookup whs" I got this:

    Server:  dns.rnc.net.cable.rogers.com
    Address:  64.71.255.198

    Name:    whs
    Addresses:  8.15.7.107, 63.251.179.17, 65.200.200.47

    I then released my public IP from my router (Linksys WRT54G 2.2) and tried it again. That time I got:

    *** Can't find server name for address 192.168.1.1: No information
    *** Default servers are not available
    Server:  UnKnown
    Address:  192.168.1.1

    *** No address (A) records available for whs

    I renewed my IP on the router and now I am getting:

    *** Can't find server name for address 192.168.1.1: Non-existent domain
    *** Default servers are not available
    Server:  UnKnown
    Address:  192.168.1.1

    *** No address (A) records available for whs

    If I change the DNS from the address of my router to "Obtain DNS Server address automaticly" I then get this:

    Server:  dns.rnc.net.cable.rogers.com
    Address:  64.71.255.198

    *** dns.rnc.net.cable.rogers.com can't find whs: Non-existent domain


    On another client that I did not try to reinstall the Connector software on, the Icon in the taskbar is black. If I double click on it, the WHS Console launchs and I can enter the password. It will log into the console adn I can control the server from there. Also, the Backup Now option is greyed out on the connector menu. 

    Where do I go from here? 


     

    Tuesday, October 28, 2008 3:54 AM

All replies

  • Hello,
    did you try to run discovery.exe from Program Files\Windows Home Server on the client to reconnect?
    Is the new server fully patched up?
    Did you play around with the hosts file to configure name resolution? In this case there could still stuck wrong entries on the client.
    Is NetBIOS over TCP/IP enabled on both the Client and Server? (Network Connection Properties, TCP/IP,  Advanced, WINS tab)?

    Not each router is a full fletched DNS server, so it is ok to not return a name - better than getting a wrong result, if you use the ISPs DNS server directly.

    Best greetings from Germany
    Olaf
    Tuesday, October 28, 2008 1:10 PM
    Moderator
  • Ok, If I run Discovery.exe, I have the same results. As far as I know, the server is fully patched. (I have it set to Auto Download and update.) I only played with the Host file on one client machine and currently all of the client machines are having the same problem. All of the PC's were setup with NetBIOS over TCP/IP as default, so I switched then to enabled, but it didn't change anything.

    Here are a few things that make me go Hmmmm.
    I changed the name of the replacement server to the same name as the older server. I also used the same IP address, so unless something was going off the MAC addresses, it should work. Also, I can access the server by pinging the name of the server, I can see and access the shares on the server. I can use the Windows Home Server Console that was installed on the other clients to connect to the server and access the different Tabs in the console. If the problem was a network related problem, when I tried to connect to the server via the console, it wouldn't be able to validate my password and connect to the server. Nor would I expect to be able to connect and control the server via RDC.

    The problem remains that I can not configure or perform any form of backups. I am thinking that the problem is with the server, as I am having the same problems with all the clients.
    Monday, November 3, 2008 4:41 AM
  • Hi Ted,
    please post the output of the command
    ipconfig /all
    on both one client and the server.
    Best greetings from Germany
    Olaf
    Monday, November 3, 2008 8:05 AM
    Moderator
  • Here is from one Client.

    Windows IP Configuration

            Host Name . . . . . . . . . . . . : MicroPC
            Primary Dns Suffix  . . . . . . . :
            Node Type . . . . . . . . . . . . : Hybrid
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
            DNS Suffix Search List. . . . . . : phub.net.cable.rogers.com

    Ethernet adapter Wireless Network Connection:

            Connection-specific DNS Suffix  . : phub.net.cable.rogers.com
            Description . . . . . . . . . . . : Microsoft Wireless Notebook Adapter
    MN-730
            Physical Address. . . . . . . . . : 00-0D-3A-72-D5-A2
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 192.168.1.102
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.1.1
            DHCP Server . . . . . . . . . . . : 192.168.1.1
            DNS Servers . . . . . . . . . . . : 64.71.255.198
            Lease Obtained. . . . . . . . . . : Monday, November 03, 2008 9:52:57 AM

            Lease Expires . . . . . . . . . . : Tuesday, November 04, 2008 9:52:57 A
    M

    Ethernet adapter Hamachi:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Hamachi Network Interface
            Physical Address. . . . . . . . . : 7A-79-05-35-77-9C
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : No
            IP Address. . . . . . . . . . . . : 5.53.119.156
            Subnet Mask . . . . . . . . . . . : 255.0.0.0
            Default Gateway . . . . . . . . . :
            DHCP Server . . . . . . . . . . . : 5.0.0.1
            Lease Obtained. . . . . . . . . . : Monday, November 03, 2008 10:47:53 A
    M
            Lease Expires . . . . . . . . . . : Monday, November 03, 2008 10:52:08 A
    M

    C:\Documents and Settings\Ted>


    Here is from another client.

    Windows IP Configuration

            Host Name . . . . . . . . . . . . : CompaqP4
            Primary Dns Suffix  . . . . . . . :
            Node Type . . . . . . . . . . . . : Unknown
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
            DNS Suffix Search List. . . . . . : phub.net.cable.rogers.com

    Ethernet adapter Local Area Connection:

            Connection-specific DNS Suffix  . : phub.net.cable.rogers.com
            Description . . . . . . . . . . . : Intel(R) PRO/100 VM Network Connecti
    on
            Physical Address. . . . . . . . . : 00-08-02-36-91-64
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 192.168.1.101
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.1.1
            DHCP Server . . . . . . . . . . . : 192.168.1.1
            DNS Servers . . . . . . . . . . . : 64.71.255.198
            Lease Obtained. . . . . . . . . . : Monday, November 03, 2008 4:16:54 AM

            Lease Expires . . . . . . . . . . : Tuesday, November 04, 2008 4:16:54 A
    M

    Ethernet adapter Hamachi:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Hamachi Network Interface
            Physical Address. . . . . . . . . : 7A-79-05-7C-20-71
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : No
            IP Address. . . . . . . . . . . . : 5.124.32.113
            Subnet Mask . . . . . . . . . . . : 255.0.0.0
            Default Gateway . . . . . . . . . :
            DHCP Server . . . . . . . . . . . : 5.0.0.1
            Lease Obtained. . . . . . . . . . : Sunday, November 02, 2008 4:12:53 PM

            Lease Expires . . . . . . . . . . : Monday, November 02, 2009 4:12:53 PM


    C:\Documents and Settings\Ted>

    Here is from the server.

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : WHS
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter LAN 1B:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Network Co
    nnection
       Physical Address. . . . . . . . . : 00-04-23-79-90-6B
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.1.20
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.1

    Ethernet adapter LAN 1A:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Network Co
    nnection #2
       Physical Address. . . . . . . . . : 00-04-23-79-90-6A
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.1.25
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.1


    Thanks!
    Ted

    Monday, November 3, 2008 3:54 PM
  • Hi Ted,
    there are two entries on your client, which often cause name resolution internally going wrong:
    • DNS server pointing to external address instead of to the router, as configured in your server
    • Connection specific DNS suffix - an entry, which should simply stay empty, but often is preconfigured by the router, because the ISP finds his domain so cool, maybe
    Try to change those two and reboot.
    After that try discovery again.

    Best greetings from Germany
    Olaf
    Monday, November 3, 2008 8:47 PM
    Moderator
  • Here's what I notice, Ted. 
    1. Your clients are set to use DHCP to receive their network configurations, but your server isn't.
    2. Your server and your clients are set to use different DNS servers. This is almost guaranteed to break discovery and/or backups, because your server believes it's in a slightly different subnet.
    3. Your server has two NICs, and both are probably connected. Certainly they're both configured. Windows Home Server can't operate as a multi-homed machine, and the NICs aren't teamed, so you may have trouble communicating with some clients because of that too.
    Here's what I would do first:
    1. Set your router (your DHCP server) to send it's own IP address as the DNS server.
    2. Disconnect one of the two network connections to your server.
    3. Reboot everything (including your router).

    I'm not on the WHS team, I just post a lot. :)
    Monday, November 3, 2008 10:42 PM
    Moderator
  • Ok, I realized that I had set a couple of PCs to use DHCP due to a problem I was having with my cable provider and I had to hook up directly to my modem. I have set them back to static addresses. Also, I disabled the dual NIC in the server and I am connected to the one on the MB. I have rebooted everything and there are no changes in my results. Here are the results from the IPCONFIG of each machine. Any thoughts?




    Windows IP Configuration

            Host Name . . . . . . . . . . . . : CompaqP4
            Primary Dns Suffix  . . . . . . . :
            Node Type . . . . . . . . . . . . : Unknown
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Intel(R) PRO/100 VM Network Connection
            Physical Address. . . . . . . . . : 00-08-02-36-91-64
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.1.50
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.1.1
            DNS Servers . . . . . . . . . . . : 192.168.1.1

    Ethernet adapter Hamachi:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Hamachi Network Interface
            Physical Address. . . . . . . . . : 7A-79-05-7C-20-71
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : No
            IP Address. . . . . . . . . . . . : 5.124.32.113
            Subnet Mask . . . . . . . . . . . : 255.0.0.0
            Default Gateway . . . . . . . . . :
            DHCP Server . . . . . . . . . . . : 5.0.0.1
            Lease Obtained. . . . . . . . . . : Thursday, November 06, 2008 5:48:04 AM
            Lease Expires . . . . . . . . . . : Friday, November 06, 2009 5:48:04 AM



    Windows IP Configuration

            Host Name . . . . . . . . . . . . : MicroPC
            Primary Dns Suffix  . . . . . . . :
            Node Type . . . . . . . . . . . . : Hybrid
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Wireless Network Connection:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Microsoft Wireless Notebook Adapter MN-730
            Physical Address. . . . . . . . . : 00-0D-3A-72-D5-A2
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.1.60
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.1.1
            DNS Servers . . . . . . . . . . . : 192.168.1.1

    Ethernet adapter Hamachi:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Hamachi Network Interface
            Physical Address. . . . . . . . . : 7A-79-05-35-77-9C
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : No
            IP Address. . . . . . . . . . . . : 5.53.119.156
            Subnet Mask . . . . . . . . . . . : 255.0.0.0
            Default Gateway . . . . . . . . . :
            DHCP Server . . . . . . . . . . . : 5.0.0.1
            Lease Obtained. . . . . . . . . . : Thursday, November 06, 2008 6:17:39 AM
            Lease Expires . . . . . . . . . . : Thursday, November 06, 2008 6:21:54 AM



    Windows IP Configuration

       Host Name . . . . . . . . . . . . : WHS
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network Connection
       Physical Address. . . . . . . . . : 00-0B-DB-93-01-73
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.1.10
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.1


     

    Thursday, November 6, 2008 11:31 AM
  • Hi Ted,
    NetBIOS over TCP/IP seems to be not enabled on clients and server.
    The Hamachi adapter confuses me. What happens, if you deactivate this? Where is it located in Network Properties under Advanced/Advanced Settings?
    Also with those changes, I had to perform one or two reboots of both the client and server, as I performed a server migration to different hardware two days ago, before the name resolution went in effect.
    Best greetings from Germany
    Olaf
    Thursday, November 6, 2008 12:29 PM
    Moderator