locked
Connector install fails at configuring computer backup RRS feed

Answers

  • On 6/16/2010 11:41 PM, spring1975 wrote:

    Let me preface this with the fact that this computer has been restored using the restore PC process from the server I'm not trying to reconnect to.  So if there's a process I should go through to reconnect this computer after a restore, please let me know.  Otherwise...

    I had the connector working for a few days after the restore.  I had uninstalled and reinstalled the connector by visitinghttp://<myserver>:55000 <http://&lt;myserver&gt;:55000>

    The connector lost its connection earlier this week some time, and I haven't been able to re-establish the connection since.  What I've tried...

    Visiting the server's webpage to have it uninstall and re-install the connector like last time.  Running throught the connector troubleshooter.  It says there's no problem.

    I've tried a few things posted in this forum.

    I've checked the date/time on the server and my PC (both are within a second of each other)
    http://social.microsoft.com/Forums/en/whssoftware/thread/65f5bdcb-b3ae-4a6a-ae6d-0cc3e7befba1

    I've disabled the anti-virus and firewalls (Norton Internet Security Suite 2010)
    http://social.microsoft.com/Forums/en-US/whssoftware/thread/284a4604-3469-4c69-82f2-c411bec786a5

    I've checked the event viewer and found no errors
    http://social.microsoft.com/Forums/en/whshardware/thread/aad0a638-d8b1-4226-8dc4-3840f386bfd8

    I've tried rebooting my router (linksys WRT54GL)

    All make no difference.  Any other suggestions aside from reinstalling the server?  I'm all ears.

    One more thing to try is going into the connector's folder on your
    client (most likely in C:\Program Files\Windows Home Server Connector or
    something similar) and running discovery.exe.  This *should* reconnect
    it with your server.

    Before doing that, make sure that the client and server have the same
    workgroup (or domain) names, and are on the same network.  The workgroup
    can be found by going to Control Panel--> System (or pressing the
    Windows Key + the Pause Key at the same time).  The IP Addresses can be
    found by opening a Command Prompt (Accessories --> Command Prompt or
    Run..  cmd) and typing ipconfig.  They should have basically the same
    information except for the last number.

    For example

    (Correct)

    Client:

    Ethernet Connection 1

    IP Address:  192.168.2.2
    Subnet Mask: 255.255.255.0
    Default Gateway: 192.168.2.1

    Server:

    Ethernet Connection 1

    IP Address 192.168.2.80
    Subnet Mask 255.255.255.0
    Default Gateway 192.168.2.1

    (Incorrect)

    Client

    Ethernet Connection 1

    IP Address 192.168.1.2 <--Note the 1 instead of a 2 in the third group.
    Subnet Mask 255.255.255.0
    Default Gateway 192.168.1.1

    Server

    Ethernet Connection 1

    IP Address 192.168.2.80
    Subnet Mask 255.255.255.0
    Default Gateway 192.168.2.1

    Also if you see something like this for ipconfig

    IP Address 169.254.0.x (where x can be anything from 0 to 255) then it
    means that your computer wasn't able to get an IP address on the network.

    If your IP address is wrong, then you need to make sure that both
    computers are getting their IP addresses from the same source (a router
    or computer on the network), or if they are configured statically (using
    the Properties of the network adapter), that they are on the same network.

    Hope these help you, and have a great day:)
    Patrick.


    Smile... Someone out there cares deeply for you.
    Have you updated your OS and Antivirus today?
    http://update.microsoft.com


    Smile.. Someone out there cares deeply for you.
    • Marked as answer by spring1975 Friday, June 18, 2010 12:18 AM
    Thursday, June 17, 2010 5:26 PM

All replies

  • On 6/16/2010 11:41 PM, spring1975 wrote:

    Let me preface this with the fact that this computer has been restored using the restore PC process from the server I'm not trying to reconnect to.  So if there's a process I should go through to reconnect this computer after a restore, please let me know.  Otherwise...

    I had the connector working for a few days after the restore.  I had uninstalled and reinstalled the connector by visitinghttp://<myserver>:55000 <http://&lt;myserver&gt;:55000>

    The connector lost its connection earlier this week some time, and I haven't been able to re-establish the connection since.  What I've tried...

    Visiting the server's webpage to have it uninstall and re-install the connector like last time.  Running throught the connector troubleshooter.  It says there's no problem.

    I've tried a few things posted in this forum.

    I've checked the date/time on the server and my PC (both are within a second of each other)
    http://social.microsoft.com/Forums/en/whssoftware/thread/65f5bdcb-b3ae-4a6a-ae6d-0cc3e7befba1

    I've disabled the anti-virus and firewalls (Norton Internet Security Suite 2010)
    http://social.microsoft.com/Forums/en-US/whssoftware/thread/284a4604-3469-4c69-82f2-c411bec786a5

    I've checked the event viewer and found no errors
    http://social.microsoft.com/Forums/en/whshardware/thread/aad0a638-d8b1-4226-8dc4-3840f386bfd8

    I've tried rebooting my router (linksys WRT54GL)

    All make no difference.  Any other suggestions aside from reinstalling the server?  I'm all ears.

    One more thing to try is going into the connector's folder on your
    client (most likely in C:\Program Files\Windows Home Server Connector or
    something similar) and running discovery.exe.  This *should* reconnect
    it with your server.

    Before doing that, make sure that the client and server have the same
    workgroup (or domain) names, and are on the same network.  The workgroup
    can be found by going to Control Panel--> System (or pressing the
    Windows Key + the Pause Key at the same time).  The IP Addresses can be
    found by opening a Command Prompt (Accessories --> Command Prompt or
    Run..  cmd) and typing ipconfig.  They should have basically the same
    information except for the last number.

    For example

    (Correct)

    Client:

    Ethernet Connection 1

    IP Address:  192.168.2.2
    Subnet Mask: 255.255.255.0
    Default Gateway: 192.168.2.1

    Server:

    Ethernet Connection 1

    IP Address 192.168.2.80
    Subnet Mask 255.255.255.0
    Default Gateway 192.168.2.1

    (Incorrect)

    Client

    Ethernet Connection 1

    IP Address 192.168.1.2 <--Note the 1 instead of a 2 in the third group.
    Subnet Mask 255.255.255.0
    Default Gateway 192.168.1.1

    Server

    Ethernet Connection 1

    IP Address 192.168.2.80
    Subnet Mask 255.255.255.0
    Default Gateway 192.168.2.1

    Also if you see something like this for ipconfig

    IP Address 169.254.0.x (where x can be anything from 0 to 255) then it
    means that your computer wasn't able to get an IP address on the network.

    If your IP address is wrong, then you need to make sure that both
    computers are getting their IP addresses from the same source (a router
    or computer on the network), or if they are configured statically (using
    the Properties of the network adapter), that they are on the same network.

    Hope these help you, and have a great day:)
    Patrick.


    Smile... Someone out there cares deeply for you.
    Have you updated your OS and Antivirus today?
    http://update.microsoft.com


    Smile.. Someone out there cares deeply for you.
    • Marked as answer by spring1975 Friday, June 18, 2010 12:18 AM
    Thursday, June 17, 2010 5:26 PM
  • I just got home, saw your post and tried changing the server's workgroup.  Then I tried the connector again and it worked.  However, I can't repeat this behavior, so I'm marking this answer hesitantly.  I have another computer that is in a different workgroup and the connector worked just fine.

    I hate these things.  This supposedly worked, but who knows if it was the real cause if I can't repeat it!

    Friday, June 18, 2010 12:46 AM