locked
This computer cannot connect to your home server, check your network... (again!) RRS feed

  • Question

  • I am having problems connecting to Windows Home Server Console – I have seen there are a lot of threads on this so here are the symptoms and what I have tried!

    Symptom: When I right click on the WHS Icon and select “Windows Home Server Console” I get the usual window up, enter my password and click next.  Comes back with the standard error “This computer cannot connect to your home server.  Check your network connection  ...”. 

    Window Home Server is powered up and working normally, doing backups and I am able to see the file shares – so it is definitely there...

    This happens from all my PCs at home.  Note Windows Home Server Console has worked in the past – I think these symptoms started when I had to uninstall .NET Framework 3.5 and 3.0, then reinstall .NET Framework 2.0 to resolve a corrupted install.  Then of course re-install all the updates and .NET Framework 3.0 and 3.5 again.

    I can use Remote Desktop Connection into my WHS and from there I can open Windows Home Server Console.

    I can ping my IP Address 192.168.0.4 and server name whs-pwbaker

    I have tried:-

    ·         Connecting to Windows Home Server Console with the LAN disconnected.

    ·         Adding my IP Address and Server name to the lmhosts and hosts files

    127.0.0.1       localhost
    192.168.0.4    whs-pwbaker
    ::1             localhost

    ·         Running discovery.exe getting “This operation cannot be completed at this time ...”

    ·         Rebooting more times than you can shake a stick at!

    All with no progress – any ideas?

    Regards, Peter


    Regards, Peter
    Sunday, December 26, 2010 4:10 PM

Answers

  • Fixed it... 

    The Symptoms described by Yoon here http://forum.wegotserved.com/index.php/topic/13987-whs-connector-issues-wsus-30-on-whs-no-longer-working/ were identical to mine and the advice offered by Drashna Jaelre (WGS) was a real help...

    Open up IIS (Internet Informational Services) console on the server, check the enroll directory, right click -> properties, and check the "ASP.NET" tab and make sure it's set to 2.x. 

    This did not work for me so I also checked the enrollId directory, right click -> properties, and check the "ASP.NET" tab and make sure it's set to 2.x. 

    Combination of two actions above and a reboot fixed my issues – nice!


    Regards, Peter
    • Marked as answer by Peter W Baker Friday, December 31, 2010 2:04 PM
    Friday, December 31, 2010 2:04 PM

All replies

  • Did you check date, time and time zone on both your home server and the client?

    Best greetings from Germany
    Olaf

    Sunday, December 26, 2010 9:05 PM
    Moderator
  • Hi Olaf, yes sorry I should have put that in as well, same timezone, all adjusting for Daylight Time Savings and same time within 60 seconds - regards, Peter
    Regards, Peter
    Sunday, December 26, 2010 11:06 PM
  • In this case (and if the date including day, month, year matches as well) the DNS settings would be interesting.

    In the FAQ How to Troubleshoot Network Connection Problems with Windows Home Server I described the influence of wrong settings (i.e. external DNS server, DNS suffix and DNS search suffixes).

    Which output gives ipconfig /all on client and server?
    What happens, if you disable TCP/IP v6 Protocol or disconnect the router from the Internet?
    Does the server or the client have multiple active network adapters?
    Can you see related error messages or warnings matching the time of your connection attempts in the event log of your home server?

    What happens, if you try to open http://yourservername:55000 in Internet Explorer? (.NET Framework and ASP.NET misconfigurations often are causing strange behavior and can sometimes be veriefied and fixed in IIS. In this case you would see an ASP.NET version 1.something in the bottom of an error screen for above call.)

    If this all does not help, a server reinstall may be the only way to solve the problem.

    Best greetings from Germany
    Olaf

    Monday, December 27, 2010 10:53 PM
    Moderator
  • Hi Olaf - thanks for the continued info, I will have another read of the troubleshooting network connection article tomorrow,

    Not sure if it helps there is clearly something trying to happen as when I try to connect to the console I can hear the disk on the home server being accessed as if it checking something and then I get the error message... 

    but here is what I can see already:-

    Which output gives ipconfig /all on client and server?

    WHS

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : WHS-PWBAKER

       Primary Dns Suffix  . . . . . . . :

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

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

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

     

    Ethernet adapter Local Area Connection 3:

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

       Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit Ethernet NIC

       Physical Address. . . . . . . . . : 00-B0-C2-01-65-2E

     

    Ethernet adapter Local Area Connection 4:

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC

       Physical Address. . . . . . . . . : 00-1C-C0-D0-73-9D

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       IP Address. . . . . . . . . . . . : 192.168.0.11

       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. . . . . . . . . . : 28 December 2010 18:34:34

       Lease Expires . . . . . . . . . . : 29 December 2010 18:34:34

    Client

    Microsoft Windows [Version 6.1.7600]

    C:\Users\PeterWBaker>ipconfig/all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : DELLinsp545S

       Primary Dns Suffix  . . . . . . . :

       Node Type . . . . . . . . . . . . : Hybrid

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

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

     

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek PCIe FE Family Controller

       Physical Address. . . . . . . . . : 00-24-E8-10-E8-0A

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       Link-local IPv6 Address . . . . . : fe80::acc9:4332:76a9:b9e3%11(Preferred)

       IPv4 Address. . . . . . . . . . . : 192.168.0.13(Preferred)

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

       Lease Obtained. . . . . . . . . . : 28 December 2010 21:05:04

       Lease Expires . . . . . . . . . . : 29 December 2010 21:05:04

       Default Gateway . . . . . . . . . : 192.168.0.1

       DHCP Server . . . . . . . . . . . : 192.168.0.1

       DHCPv6 IAID . . . . . . . . . . . : 251667688

       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-DF-C8-EF-00-24-E8-03-32-89

     

       DNS Servers . . . . . . . . . . . : 192.168.0.1

       NetBIOS over Tcpip. . . . . . . . : Enabled

     

    Tunnel adapter isatap.{487967DF-73A9-4EBF-BB42-6AC74FE5B4D8}:

     

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

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Microsoft ISATAP Adapter

       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

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

       Autoconfiguration Enabled . . . . : Yes

     

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

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

       Autoconfiguration Enabled . . . . : Yes

       IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:73b8:28ef:2250:a06c:8485(Preferred)

       Link-local IPv6 Address . . . . . : fe80::28ef:2250:a06c:8485%13(Preferred)

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

       NetBIOS over Tcpip. . . . . . . . : Disabled

    Q. What happens, if you disable TCP/IP v6 Protocol or disconnect the router from the Internet?

    A. I am not smart enough to “disable TCP/IP v6 Protocol” but when I disconnect my Router it make no difference.

    Q. Does the server or the client have multiple active network adapters?

    A. No both just have 1 NIC (connected) onto a wired network

    Q. Can you see related error messages or warnings matching the time of your connection attempts in the event log of your home server?

    A. I can’t see anything strange in here – only the following at the time I try to log in 0110Hrs this morning:-

    Type

    Date

    Time

    Source

    Category

    Event

    User

    Computer

    Success Audit

    29/12/2010

    01:10:18

    Security

    Account Logon

    680

    PeterWBaker

    WHS-PWBAKER

    Success Audit

    29/12/2010

    01:10:18

    Security

    Logon/Logoff

    540

    PeterWBaker

    WHS-PWBAKER

    Success Audit

    29/12/2010

    01:10:17

    Security

    Logon/Logoff

    540

    IUSR_SERVER

    WHS-PWBAKER

    Success Audit

    29/12/2010

    01:10:17

    Security

    Logon/Logoff

    552

    NETWORK SERVICE

    WHS-PWBAKER

    Success Audit

    29/12/2010

    01:10:17

    Security

    Account Logon

    680

    IUSR_SERVER

    WHS-PWBAKER

    Q. What happens, if you try to open http://yourservername:55000 in Internet Explorer? (.NET Framework and ASP.NET misconfigurations often are causing strange behavior and can sometimes be veriefied and fixed in IIS. In this case you would see an ASP.NET version 1.something in the bottom of an error screen for above call.)

    A. I get the standard “Windows Home Server Connector Setup” welcome page and when I connect...

    I hope that helps to help me!  Regards, Peter


    Regards, Peter
    Wednesday, December 29, 2010 1:56 AM
  • Hi

    I just ran The Windows Home Server Connector Trouble shooter and it says after the tests are complete.

    ·         Cannot connect to the server internal Web site (password hint page)

    ·         Cannot connect to the server internal Web site (ASPX page)

    ·         Cannot connect to the server internal Web site over IP address (password hint page)

    ·         Cannot connect to the server internal Web site over IP address (ASPX page)

    And then recommends to Check the following:

    ·         Your home server and home computers are connected to the same router <<<They areJ

    ·         Internet Information Services (IIS) is running on Windows Home Server.

    ·         The "WHS site" is started on IIS.

    ·         There is a security certificate installed on the "WHS site".

    ·         TCP ports 55000 and 56000 are open on your Windows Home Server Windows Firewall.

    Given my issues started after quite some .NET re-installed I am leading towards IIS - does this help?

    Thanks, Peter


    Regards, Peter
    Wednesday, December 29, 2010 2:21 AM
  • Hi Peter,

    there is no easy or documented way to fix WHS after reinstalling .NET Framework.

    So the only recommended method, before wasting more time. would be a server reinstall. How this is accomplished, depends from the WHS (OEM or self build?).

    Best greetings from Germany
    Olaf

    Wednesday, December 29, 2010 9:28 PM
    Moderator
  • Hi Olaf, Oh dear!

    The box is an OEM build from a UK Company called Tranquil PC.  It is a headless system without a DVD drive so I guess quite tricky - are you able to point me at any publicised ways to rebuild?

    Thanks in advance, Peter


    Regards, Peter
    Wednesday, December 29, 2010 10:29 PM
  • Tranquil should be able to provide information on how to proceed.
    I'm not on the WHS team, I just post a lot. :)
    Thursday, December 30, 2010 1:13 PM
    Moderator
  • Hi Peter,
    the manual should contain the instructions for your specific model and recovery DVD should be included in delivery.
    A client is involved in such reinstallation, from which you should uninstall the connector software before starting the process.

    Anyway it is recommended to backup important data either to an external disk or to a client before starting over.

    Best greetings from Germany
    Olaf

     

    Thursday, December 30, 2010 8:17 PM
    Moderator
  • Hi Olaf/Ken

    Can anyone tell me if rebuilding the server will delete my backup database?  I have external backups of my photos and Music so no problem there.  I have a client that has died:-(

    Thanks Peter

    PS. seems like the issue stopping me accessing the console remotely also stops the client finding the server to do a restore - is this likely?


    Regards, Peter
    Friday, December 31, 2010 1:09 PM
  • Fixed it... 

    The Symptoms described by Yoon here http://forum.wegotserved.com/index.php/topic/13987-whs-connector-issues-wsus-30-on-whs-no-longer-working/ were identical to mine and the advice offered by Drashna Jaelre (WGS) was a real help...

    Open up IIS (Internet Informational Services) console on the server, check the enroll directory, right click -> properties, and check the "ASP.NET" tab and make sure it's set to 2.x. 

    This did not work for me so I also checked the enrollId directory, right click -> properties, and check the "ASP.NET" tab and make sure it's set to 2.x. 

    Combination of two actions above and a reboot fixed my issues – nice!


    Regards, Peter
    • Marked as answer by Peter W Baker Friday, December 31, 2010 2:04 PM
    Friday, December 31, 2010 2:04 PM