Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Connector install problem RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I am hoping someone can help me with installing the WHS connector software on a second laptop.  Here's what I have done / found on this laptop:

    1. Went to \\server\software\Home server connector software and ran setup.exe
    2. After the install started I got an error: "The wizard can not find your home server"
    3. Selected "Find my home server manually"
    4. Entered the server name - still unable to find server
    5. Entered the server static IP address-- still unable to find server
    6. Pinged server name-- no problems
    7. Pinged server static IP address-- no problems
    8. Attempted to remote desktop to WHS using server name-- failed to connect
    9. Attempted to remote desktop to WHS using static server IP address-- connected

    Any ideas for what I should do to get connector to run on this machine?





    Tuesday, October 27, 2009 3:54 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Can you run ipconfig /all on the laptop you're having trouble with, a computer you're not having trouble with, and your home server, and post the results here?
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, October 27, 2009 3:48 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    ==============

    WHS Server:

    ============== 

       Host Name . . . . . . . . . . . . : servername

       Primary Dns Suffix  . . . . . . . :

       Node Type . . . . . . . . . . . . : Unknown

       IP Routing Enabled. . . . . . . . : No

       WINS Proxy Enabled. . . . . . . . : No

     

    Ethernet adapter Local Area Connection:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit Ether

    net NIC

       Physical Address. . . . . . . . . : 00-1D-7D-31-1E-AF

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 192.168.1.202

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . : 192.168.1.1

       DNS Servers . . . . . . . . . . . : 68.87.71.226

                                           68.87.73.242

     

    Laptop that is not working properly:

     

    Windows IP Configuration

     

            Host Name . . . . . . . . . . . . : laptopname

            Primary Dns Suffix  . . . . . . . : comapny.loc

            Node Type . . . . . . . . . . . . : Unknown

            IP Routing Enabled. . . . . . . . : No

            WINS Proxy Enabled. . . . . . . . : No

            DNS Suffix Search List. . . . . . : company.loc

     

    Ethernet adapter Local Area Connection 3:

     

            Media State . . . . . . . . . . . : Media disconnected

            Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Con

    nection

            Physical Address. . . . . . . . . : 00-21-70-E4-38-CC

     

    Ethernet adapter Wireless Network Connection:

     

            Connection-specific DNS Suffix  . :

            Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN

            Physical Address. . . . . . . . . : 00-22-FB-1D-C2-9E

            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 . . . . . . . . . . . : 208.67.222.222

                                                208.67.220.220

            Lease Obtained. . . . . . . . . . : Tuesday, October 27, 2009 8:33:13 PM

     

            Lease Expires . . . . . . . . . . : Wednesday, October 28, 2009 8:33:13

    PM

     

     

    Working machine

     

            Host Name . . . . . . . . . . . . : desktopname

            Primary Dns Suffix  . . . . . . . :

            Node Type . . . . . . . . . . . . : Unknown

            IP Routing Enabled. . . . . . . . : No

            WINS Proxy Enabled. . . . . . . . : No

     

    Ethernet adapter Local Area Connection 3:

     

            Connection-specific DNS Suffix  . :

            Description . . . . . . . . . . . : Realtek RTL8169/8110

            Physical Address. . . . . . . . . : 00-1E-2A-B2-4F-CA

            Dhcp Enabled. . . . . . . . . . . : No

            IP Address. . . . . . . . . . . . : 192.168.1.200

            Subnet Mask . . . . . . . . . . . : 255.255.255.0

            Default Gateway . . . . . . . . . : 192.168.1.1

            DNS Servers . . . . . . . . . . . :   68.87.71.226

    68.87.74.242

     

     

     

     

    Wednesday, October 28, 2009 2:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Your non-working machine is not configured the same as your server and the machine that's working. The server and the computer that are working are using Comcast DNS servers, while the one that's not working is using OpenDNS servers. Effectively, the computer that's not working is on a different subnet as a result of the configuration difference.

    Since the computer that's not working appears to be a company-supplied laptop, you may not be permitted to make changes to the network configuration. Assuming you are, perhaps the simplest solution would be to add an entry in the hosts file on that machine for your server. The hosts file is located in C:\Windows\system32\drivers\etc .
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, October 28, 2009 3:12 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Changed the DNS setting on the non-working machine to obtain a DNS address automatically.

    I am now able to get through most of the connector install-- after successfully joining the WHS and configuring the backup, the install errors out with the following message: "Home Server Discovery has encountered a problem and needs to close.  We are sorry for the inconvenience."

    Not sure if this is a real problem or not-- at least the connector software is now installed and, if I manually run it, I have what seems to be a functional app in the notification tray.
    Wednesday, October 28, 2009 3:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    ...
    I am now able to get through most of the connector install-- after successfully joining the WHS and configuring the backup, the install errors out with the following message: "Home Server Discovery has encountered a problem and needs to close.  We are sorry for the inconvenience."
    ...
    Are you an administrator on that machine? The connector must be installed by an administrator.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, October 28, 2009 2:58 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    First, thanks for all the help.

    No, I am not the administrator-- I had to install as a user account.

    All the functionality that I've tried seems to be working (able to access console from system tray, backup ran properly,. . . .).  Should I be worried?




    Wednesday, October 28, 2009 5:03 PM