locked
Cannot connect to Server using connector software RRS feed

  • Question

  • I think I am having a similar problem or the same problemas a question below.  I can access shared folders fine, but when I attempt to connect via the connector software I get the error message:  "This computer cannot connect to your home server.  Check your network connection and make sure that your home server is powered on.  If your home server has recently restarted, try again in a few minutes."  The same thing from three different computers, all of which can access file shares OK.  All PCs are XP-SP3.  Connector software was last installed concurrent with PP1 installation on WHS.  Wife says she ran some updates on WHS (advertised in the system tray) a week or two ago when I was not at home.

    If I need to do a "server reinstall" -- where do I find instructions for doing so?
    Friday, May 15, 2009 1:00 AM

All replies

  • I think I am having a similar problem or the same problemas a question below.  I can access shared folders fine, but when I attempt to connect via the connector software I get the error message:  "This computer cannot connect to your home server.  Check your network connection and make sure that your home server is powered on.  If your home server has recently restarted, try again in a few minutes."  The same thing from three different computers, all of which can access file shares OK.  All PCs are XP-SP3.  Connector software was last installed concurrent with PP1 installation on WHS.  Wife says she ran some updates on WHS (advertised in the system tray) a week or two ago when I was not at home.

    If I need to do a "server reinstall" -- where do I find instructions for doing so?

    I wouldn't jump straight to a Server Reinstallation just yet. :)  First, can you ping your server both by name and by IP address?  Have you tried breaking the connection between your modem and your router (removing the ability to connect to the internet), then try connecting to the server?  Can you run ipconfig /all on your server and a client, then post the results here?
    Friday, May 15, 2009 4:04 AM
    Moderator
  • Thank you for your reply.

    I was able to ping both the IP and the name of the server, as you will see in the folowing, which also includes the "ipconfig /all" from one of the client PCs (this one happens to be a virtal PC running on a Mac under Parallells; my other PCs with the same problem are native WinXP machines) (I have obscured the names of the PC and the server and the physical ethernet addresses somewhat as I am not sure if they represent a security risk):

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Eric>ping 192.168.0.1

    Pinging 192.168.0.1 with 32 bytes of data:

    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=64

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

    C:\Documents and Settings\Eric>ping p#####tserver1

    Pinging p#####tserver1 [192.168.0.100] with 32 bytes of data:

    Reply from 192.168.0.100: bytes=32 time=5ms TTL=128
    Reply from 192.168.0.100: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.100: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.100: bytes=32 time=1ms TTL=128

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

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

    Windows IP Configuration

            Host Name . . . . . . . . . . . . : ERIC-##-VM
            Primary Dns Suffix  . . . . . . . :
            Node Type . . . . . . . . . . . . : Unknown
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
            DNS Suffix Search List. . . . . . : hsd01.il.hsd1.il.comcast.net.

    Ethernet adapter Local Area Connection 3:

            Connection-specific DNS Suffix  . : hsd01.il.hsd1.il.comcast.net.
            Description . . . . . . . . . . . : Parallels Ethernet Adapter #2
            Physical Address. . . . . . . . . : 00-##-42-##-AE-##
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 192.168.0.189
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.0.1
            DHCP Server . . . . . . . . . . . : 192.168.0.1
            DNS Servers . . . . . . . . . . . : 192.168.0.1
            Lease Obtained. . . . . . . . . . : Thursday, May 14, 2009 11:27:13 PM
            Lease Expires . . . . . . . . . . : Friday, May 15, 2009 11:27:13 PM

    C:\Documents and Settings\Eric>�

    Here is the "ipconfig /all" from the home server:

    (C) Copyright 1985-2003 Microsoft Corp.

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

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : P######TSERVER1
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : hsd01.il.hsd1.il.comcast.net.

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : hsd01.il.hsd1.il.comcast.net.
       Description . . . . . . . . . . . : CNet PRO200WL PCI Fast Ethernet Adapter
       Physical Address. . . . . . . . . : 00-##-AD-##-D4-##
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 192.168.0.100
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DNS Servers . . . . . . . . . . . : 192.168.0.1
       Lease Obtained. . . . . . . . . . : Thursday, May 14, 2009 8:45:47 PM
       Lease Expires . . . . . . . . . . : Monday, January 18, 2038 10:14:07 PM

    C:\Documents and Settings\TEMP>

    I tried both putting the cable modem on standby and powering it down fully -- neither one helped with the conection problem.

    thanks again for your help; hope you or others may have other suggestions
    Friday, May 15, 2009 5:07 AM
  • Hi,
    there is one weak point in your DHCP configuration: The entry of a Connection Specific DNS Suffix and a DNS Suffix Search list make attempts to resolve short names via DNS attach that domain to the name before attempting name resolution. This leads to the situation, that the name resolution request will be forwarded to the DNS server authoritative for that domain - and this for sure will not have any knowledge about you home server in your internal network and either answer, that the name could not be found, or respond with the IP address of a server, which has the same name and exists in that domain.
    And I assume, that the connector software uses DNS for name resolution.
    To fix this, you could either try to remove this suffix entry (how, depends from the router) and maybe release/renew the IP addresses on the client/server given the extreme long leasing time set. If you have not reserved the IP address for the server, in the last case you may have to run discovery.exe from C:\Program Files\Windows Home Server on each client to reconnect.
    Or you add an entry pointing to the server to the hosts file on each of the clients in C:\Windows\system32\drivers\etc - which is only a workaround and will cause trouble, if you ever should need to change the router (eventually a simple power loss is enough) or reinstall your server and don't remember, that you altered the configuration file here.
    Best greetings from Germany
    Olaf
    Friday, May 15, 2009 7:05 AM
    Moderator
  • Dealing with DHCP and DNS is a bit over my head, but also it seems to me that those parameters are unlikely to have changed for quite a while, and the software was working OK a few weeks ago.

    It seems more likely that the problem is related to some recent event, such as the auto-update to PP2 that apparently occurred recently.

    Is it possible do "uninstall" the PP2 update?  andif so is there some risk in doing so?

    Friday, May 15, 2009 3:09 PM
  • While I sort of agree that it seems like something changed on the server, could you try the following (I don't think this is quite what you did previously):
    • Disconnect your router from your cable modem (i.e. break your internet connection).
    • Reboot everything, starting with your router.
    • Wait 15 minutes or so.
    • See what kind of connectivity you have then.
    BTW, your server name is rather easy to figure out, even with the obfuscation. :)

    I'm not on the WHS team, I just post a lot. :)
    Friday, May 15, 2009 3:36 PM
    Moderator
  • It took a while before I could get to it; but I shut down the network, cable modem and all PCs, then started only the router and the home server, and let is run for about 20 miutes.  Then booted up 2 PCs and tried to access the server, with no change in the problem experienced -- I can still access files/folders on the server and run both automated backups and manual backups (via the context menu on the tray icon for the connector), but cannot connect to the server console via the connector software (same error message as before).  After restarting the cable modem there is also no change in capabilities.
     
    Saturday, May 16, 2009 5:15 AM
  • I have the same problem. After installing PP2 from auto update I can't connect via connector software. I read in in other forums that maybe the IE8 is the problem but even without installing it the software doesn't connect to the whs. So I went back to PP1 and wait until there is a solution for the problem.
    Saturday, May 16, 2009 8:59 PM
  • Have you tried reinstalling your connector software? Maybe there was an update that did not get made to the clients.

    WHS CTP on PIII 667, 512MB ram, 160GB main HD and 3 x 40 GB HD's for data
    Saturday, May 16, 2009 10:33 PM
  • Huckenien --

    Thanks.  How did you roll back to PP1?  Did you uninstall PP2 from "Add/Remove Programs" in the control panel?  did you have any other subsequent updates and if so did you roll them off also (my add/remove on the server shows some dotnet updates that installed subsequent to PP2)?  PS -- ie8 just showed up as an update on my server but I told it to go away, so it's not installed.

    Sunday, May 17, 2009 12:41 AM
  • peterweb --

    Thanks.  I tried reinstalling from the version currently on the server, but the install failed.  I may try to se if I can download a fresh installer from MS on the client machine and try to re-install that way.

    Sunday, May 17, 2009 12:42 AM
  • Another Related Problem - I have also attempted, unsuccesfully, to run a restore of a backed-up PC using the Home PC Restore CD (version 1800 "dual boot", which I downloaded from MS website and which seeemed to be the most current version available). This is the most important capability I would like to resolve; I really want to be able to restore that PC from its last backup on the home server. Otherwise I could live with having to re-build the server software (even though it would be a time-eating pain in the @$$).
    Sunday, May 17, 2009 2:03 AM
  • elpackrat --

    I have a fsc scaleo so I used the original restore CD from it.


    peterweb --

    I have tried but it doesn't work. Even the setup  from .../software/home server connector software/ setup.exe can't connect to the whs and it seems that it's the pp1 version because the last editing date is 13.07.2008.
    Sunday, May 17, 2009 7:30 AM
  • Thank you for your reply.

    I was able to ping both the IP and the name of the server, as you will see in the folowing, which also includes the "ipconfig /all" from one of the client PCs (this one happens to be a virtal PC running on a Mac under Parallells; my other PCs with the same problem are native WinXP machines) (I have obscured the names of the PC and the server and the physical ethernet addresses somewhat as I am not sure if they represent a security risk):

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Eric>ping 192.168.0.1

    Pinging 192.168.0.1 with 32 bytes of data:

    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=64

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

    C:\Documents and Settings\Eric>ping p#####tserver1

    Pinging p#####tserver1 [192.168.0.100] with 32 bytes of data:

    Reply from 192.168.0.100: bytes=32 time=5ms TTL=128
    Reply from 192.168.0.100: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.100: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.100: bytes=32 time=1ms TTL=128

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

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

    Windows IP Configuration

            Host Name . . . . . . . . . . . . : ERIC-##-VM
            Primary Dns Suffix  . . . . . . . :
            Node Type . . . . . . . . . . . . : Unknown
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
            DNS Suffix Search List. . . . . . : hsd01.il.hsd1.il.comcast.net.

    Ethernet adapter Local Area Connection 3:

            Connection-specific DNS Suffix  . : hsd01.il.hsd1.il.comcast.net.
            Description . . . . . . . . . . . : Parallels Ethernet Adapter #2
            Physical Address. . . . . . . . . : 00-##-42-##-AE-##
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 192.168.0.189
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.0.1
            DHCP Server . . . . . . . . . . . : 192.168.0.1
            DNS Servers . . . . . . . . . . . : 192.168.0.1
            Lease Obtained. . . . . . . . . . : Thursday, May 14, 2009 11:27:13 PM
            Lease Expires . . . . . . . . . . : Friday, May 15, 2009 11:27:13 PM

    C:\Documents and Settings\Eric>�

    Here is the "ipconfig /all" from the home server:

    (C) Copyright 1985-2003 Microsoft Corp.

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

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : P######TSERVER1
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : hsd01.il.hsd1.il.comcast.net.

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : hsd01.il.hsd1.il.comcast.net.
       Description . . . . . . . . . . . : CNet PRO200WL PCI Fast Ethernet Adapter
       Physical Address. . . . . . . . . : 00-##-AD-##-D4-##
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 192.168.0.100
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DNS Servers . . . . . . . . . . . : 192.168.0.1
       Lease Obtained. . . . . . . . . . : Thursday, May 14, 2009 8:45:47 PM
       Lease Expires . . . . . . . . . . : Monday, January 18, 2038 10:14:07 PM

    C:\Documents and Settings\TEMP>

    I tried both putting the cable modem on standby and powering it down fully -- neither one helped with the conection problem.

    thanks again for your help; hope you or others may have other suggestions

    You didn't ping your server IP address (you pinged your router).

    Having said that, please try Olaf's suggestions.
    Sunday, May 17, 2009 4:59 PM
    Moderator
  • Kariya21 --

    I could not find/figure a way to remove/change the suffix entry on my router.  However I did try adding the server to my hosts file on two of the client PCs and it did not effect any change to the situation -- still no ability to connect.  (I added "192.168.0.1{tab}P#####TSERVER1" to the Hosts files.)

    PS, I did in fact successfully ping the server at 192.168.0.100, but I messed up when re-creating the results in the message I posted here and showed a ping of 192.168.0.1 instead.

    Also, FYI, the IP address for the server is handled by DHCP on the router, but it is reserved in the router as the fixed address of 192.168.0.100, so that same address wil always be assigned to the server.
    Monday, May 18, 2009 2:53 AM
  • (I added "192.168.0.1{tab}P#####TSERVER1" to the Hosts files.)

    According to your later text the address of the server is 192.168.0.100, so why do you add your routers IP to the hosts file?
    Best greetings from Germany
    Olaf
    Monday, May 18, 2009 8:27 AM
    Moderator
  • Sorry, that's just another typing error in my post; the actual address in the Hosts file is 192.168.0.100.  Here is what the Hosts file looks like (with the server name partially obscured as in previous posts):


    # Copyright (c) 1993-1999 Microsoft Corp.
    #
    # This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
    #
    # This file contains the mappings of IP addresses to host names. Each
    # entry should be kept on an individual line. The IP address should
    # be placed in the first column followed by the corresponding host name.
    # The IP address and the host name should be separated by at least one
    # space.
    #
    # Additionally, comments (such as these) may be inserted on individual
    # lines or following the machine name denoted by a '#' symbol.
    #
    # For example:
    #
    #      102.54.94.97     rhino.acme.com          # source server
    #       38.25.63.10     x.acme.com              # x client host

    127.0.0.1       localhost
    127.0.0.1       .psf
    192.168.0.100    p#####tserver1


    Also, just to re-confirm, I am still able to access shared folders and to run automatic and manual backups.

    Monday, May 18, 2009 5:51 PM
  • Are you able to connect via remote desktop?
    Monday, May 18, 2009 9:27 PM
  • yes, I can connect to the server via remote desktop.
    Monday, May 18, 2009 10:22 PM
  • Maybe I have a solution:

    1st Try:

    Run the discovery.exe on a client.

    2nd Try:

    Please check your services if the Drive Extender Migrator service is set to manual. If not set it. All offer services with WHS in their names shout marked with automatic. Then restart and check if the date of the connector setup file in c:/whs is newer then in ..\software\home server connector software\setup.exe. One of them shout be 10.03.2009 version 6.0.2030.0. Install it.

    Hope it works.
    Monday, May 18, 2009 10:54 PM
  • Thanks very much for your continued attention and suggestions...

    I tried running discovery.exe (shows as ver. 6.0.2030.0) from the "program files\windows home server" folder on the client, and it failed with the message "This operation cannot be completed at this time.  Please try again later.  If the problem persists, please contact product support."

    I checked "Services" on the home server.  the "Drive Extender Migrator Service" is set to manual, and shows as started.  All services that have names begining with "Windows Home Server..." show as automatic and started, except for Windows Home Server Port Forwarding, which shows as disabled and is not started.=

    I found copies of the connector installer software in "C:\whs" on the server; in the "software" file share on the server, and in the "program files\windows home server" folder on the client.  All appear to be identical, with a file date of 3/10/2009 and a version of 6.0.2030.0.  The version of "WHSConsoleClient.exe I find in the "program files\windows home server" folder on the client is also ver 6.0.2030.0.


    I am unable to re-install the connector program, as the install fails with the same message as the "discovery.exe" failure described above.
    Tuesday, May 19, 2009 12:31 AM
  • i had a similar problem a while back here is my thread that might help you

    http://social.microsoft.com/Forums/en-US/whssoftware/thread/efb6f2f6-c305-46d5-adc5-8277766be60e
    There are 10 differents kinds of people in the world those who understand binary those who dont
    Tuesday, May 19, 2009 3:24 AM
  • As a practical matter, you can try the following:
    • Remove the drive from the PC you want to restore.
    • Connect the drive to another computer joined to your server. (I would use a USB-to-SATA or USB-to-IDE bridge device to connect the drive as though it was an external USB drive.)
    • On that other computer, run C:\Program Files\Windows Home Server\ClientRestoreWizard.exe.
    This will use a full, functional Windows installation as the host for the client restore wizard instead of the WinPE environment on the Home Computer Restore CD.

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, May 19, 2009 5:12 PM
    Moderator
  • David 10100111 --

    Thanks for the suggestion, but I looked and it doesn't seem to quite match my symptoms.  I can access shared folders (read/write) and can perform backups, but I can't connect with the Connector program, nor can I install (or re-install) the connector program (which you seemed to be able to do), or run the system restore CD on a PC that needs a hard-drive restored to a new disk due to drive failure.  I did look at the KB article referenced in the thread, plus one other related article, but I searched the registry on two client systems and did not find any of the items referenced in the KB articles.
    Wednesday, May 20, 2009 4:12 AM
  • Ken Warren --

    It took a while to move systems around to where I could try this (since I had to have ethernet rather than wireless connections if it was goig to work).

    Unfortunately, the clientrestorewizard would not run successfully on the client machiine.  It failed attempting to log into the server (just as the connector fails to log in).

    I'm beginning to think my only hope is to try a server reinstall with my original 2007 version, then update it to PP1 to se if it will function properly in the mode where I had it working well in the past.

    This has been very frustrating - are there any other ideas out there?
    Thursday, May 21, 2009 5:04 PM
  • Ok, I have managed to get my whs back to work with pp2. I used the original WHSrestoreCD and set only the system partition back. After installing PP2 I had the same problem you discribed. So I logged on with the remote desktop connection and uninstalled pp2 over it by ignoring the IE8 warning. After that all thinks worked just fine but not yet with PP2.

    I read it in an other forum: reboot -> install pp2 -> reboot -> reboot -> install client connector from whs

    Then you installing the client connector you will probably get the error massage from the discovery.exe but that doesn't matter the connector is allready installed. Just reboot your client and try to logon with it.
    Saturday, May 23, 2009 10:34 AM
  • Since installing PP2 I have experienced a lot of the same connectivity issues that were never experienced before with PP1. At first, I thought that it was Win7 related, but then as I dug deeper, I found it was all my machines, regardless of OS. Many have mentioned adding the WHS to the Hosts file on the router or on each workstation or uninstalling PP2. I solved this in another method. In my DHCP scope, I added the IP address of the WHS as the first DNS entry, and pushed my other two DNS entries to 2nd and 3rd positions. As soon as I forced a release/renew, all of my machines started working correctly again, so I am sure that something has changed with PP2 and networking. Hopefully this might help you too.
    Brent
    Sunday, May 24, 2009 5:38 PM
  • My apologies for the long delay in reply/resolution.  I finally decided to do the server reinstall.  It took a good chunk of an evening, but was successful.  Then I upgraded to PP1 (which had been working well for me for some time) and applied all windows update patches EXCEPT for PP2, a big dot.net upgrade/patch (I just don't trust dot.net updates very much), and ie8.  I have set my windows update to manual, and refused those three updates so they do not reappear.  Bit of a pain to have to go in and check updated manually every week or so, but better than having it not work at all.  All PCs are now connecting properly, and I was able to do the system restore on one PC that I needed to do.
    Sunday, May 31, 2009 3:35 AM
  • My apologies for the long delay in reply/resolution.  I finally decided to do the server reinstall.  It took a good chunk of an evening, but was successful.  Then I upgraded to PP1 (which had been working well for me for some time) and applied all windows update patches EXCEPT for PP2, a big dot.net upgrade/patch (I just don't trust dot.net updates very much), and ie8.  I have set my windows update to manual, and refused those three updates so they do not reappear.  Bit of a pain to have to go in and check updated manually every week or so, but better than having it not work at all.  All PCs are now connecting properly, and I was able to do the system restore on one PC that I needed to do.

    Are you using the Windows Update website?  It sounds like you are.  However, you shouldn't use it at all (since it requires server desktop access and it's unsupported).  Did you install any Software, Optional updates from the website?  If so, that could be your problem.  Those have been known to cause strange behavior on WHS.
    Sunday, May 31, 2009 3:52 PM
    Moderator