locked
Unable to connect using the Home Server Console RRS feed

  • Question

  • I have a really odd issue.  I have a brand new installation of Windows Home Server.  I have downloaded this as part of my technet subscription and was replacing a trial version I had downloaded earlier.  The trial version was working without issue.  Now, I did a complete Server re-install (removing all backups, etc.) and setup the system like new.  I uninstalled all Home server stuff from my other computers before removing the home server and starting over.

    Here is my problem, I am unable to connect to the server using the Home Server Console.  This is true for local instances as well as when trying to connect via the Web Site interface.

    The message I get via either method is as follows:

    This computer cannot connect to your home server.  Check you network connection and make sure your home server is powered on.  If your home server has recently restarted, try again in a few minutes.

    I can RDP into the server (by server name) and can run the console directly from the server.  I have re-installed the server 3 times already and always get the same result.

    One thign that was odd is that when installing updates, I got some Search error messages in the application log saying that the home server connector software was not able to be updated.  I thought I read that these erorr messages can be ignored, but maybe theyr are the culprit.

    I have disconnected from the internet with no change and have re-installed the connector software multiple times with no change.  In the system tray, I get netowrk alerts and it knows when the home server is being rebooted.  I can even start and complete a mnaual backup via the tray icon with no issues.  I just cannot conenct using the console, which si pretty important.


    Any help or suggestions would be greatly appreciated.


    Dizneykev
    Friday, April 10, 2009 6:53 PM

All replies

  • Hi,
    did you alter the hosts file on the client in the past to resolve the name of WHS to a certain IP address?
    Could you post the output of
    ipconfig /all
    on both a client and the server?
    Best greetings from Germany
    Olaf
    Friday, April 10, 2009 8:03 PM
    Moderator
  • I am not sure how to post the output from the ipconfig.  I believe the entire issue has to do with the Power Pack 2 upgrade.  When I uninstall and re-install the Connector software from the server, all of the prompts in the license agreement state it is Home Server with power pack 1, not 2.  Can anyone tell me the dates of the connector software for power pack 2?  If there was a place to download this software directly, I would try that, but hours of Internet searches have found no such location to directly download the connector.

    The details in the home server console on the server clearly indicate that it SHOULD be power pack 2 as the versions are correct.

    Dizneykev



    Friday, April 10, 2009 10:57 PM
  • ...  When I uninstall and re-install the Connector software from the server, all of the prompts in the license agreement state it is Home Server with power pack 1, not 2. ...
    That's normal. Microsoft chose not to update the EULA that's displayed when you install Power Pack 2, so it really should refer to Power Pack 1. Not very, umm, wise, IMO...

    I'm not on the WHS team, I just post a lot. :)
    Friday, April 10, 2009 11:47 PM
    Moderator
  • I am in the process of re-installing the server from scratch for the fourth time.  This time I am going to install the connector and see if it works right from the box.  Then, I will manually update the server one itme at a time until I find what breaks it.  I am almost 100% certain it is an update killing the process.  Reading multiple threads, it sounds like it might be the .NEt 3.5 upgrade, so that is the last thing I will try to install.

    Any other ideas?

    Dizneykev
    Friday, April 10, 2009 11:52 PM
  • OK, brand new fresh load does not work right out of the box either.  This is really frustrating.  I do not understand what would keep this from working.  I realized you asked about the etc/hosts file.  I did not have any entry in here, but did try to add it to the local computers entry and it does not make any difference.  I am completely stumped at this time.


    Dizneykev
    Saturday, April 11, 2009 12:18 AM
  • OK, brand new fresh load does not work right out of the box either.  This is really frustrating.  I do not understand what would keep this from working.  I realized you asked about the etc/hosts file.  I did not have any entry in here, but did try to add it to the local computers entry and it does not make any difference.  I am completely stumped at this time.


    Dizneykev


    Are you running a third-party firewall on your client?  Can you try completely disabling the firewall on both client and server?  Also, in order to provide an ipconfig /all of a client and server, you need run it in a cmd prompt window.  Then right-click on the title bar, select Edit, then select Select All, then paste it here.

    Saturday, April 11, 2009 12:58 AM
    Moderator
  • I am not running any type of third party firewall applications.  The weird thing is that with the previous load (the trial version), everything worked correctly.  Now, with a new load, everything works, except for the console.  Below are the results of the ipconfig statements.

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Kevin>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Daddy
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : cinci.rr.com

    Ethernet adapter Local Area Connection 3:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
    it Ethernet NIC (NDIS 6.0) #2
       Physical Address. . . . . . . . . : 00-1F-D0-80-FE-9F
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection 2:

       Connection-specific DNS Suffix  . : cinci.rr.com
       Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
    it Ethernet NIC (NDIS 6.0)
       Physical Address. . . . . . . . . : 00-1F-D0-9B-4F-BA
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2002:ae67:9110:0:9402:f1f2:90e6:4b12(Pref
    erred)
       Temporary IPv6 Address. . . . . . : 2002:ae67:9110:0:8149:6b66:7e92:6e08(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::9402:f1f2:90e6:4b12%16(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.113(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Thursday, April 09, 2009 10:20:45 PM
       Lease Expires . . . . . . . . . . : Sunday, April 12, 2009 7:04:20 AM
       Default Gateway . . . . . . . . . : fe80::221:29ff:febf:28f8%16
                                           192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 385884112
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0D-5C-B8-8E-00-15-58-51-12-AB

       DNS Servers . . . . . . . . . . . : 65.24.7.10
                                           65.24.7.11
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.cinci.rr.com
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 20:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : cinci.rr.com
       Description . . . . . . . . . . . : isatap.cinci.rr.com
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 23:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{1C8CDF11-44F3-44A1-B219-BDAC45CD4
    6DA}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    C:\Users\Kevin>

    The above was on one of the client computers, below is from the Home Server.

    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

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

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : vaultdisney
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : cinci.rr.com

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : cinci.rr.com
       Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) PCI-E Gigabi
    t Ethernet NIC
       Physical Address. . . . . . . . . : 00-1F-D0-1D-8E-D6
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 192.168.1.109
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 65.24.7.10
                                           65.24.7.11
       Lease Obtained. . . . . . . . . . : Saturday, April 11, 2009 8:59:18 AM
       Lease Expires . . . . . . . . . . : Sunday, April 12, 2009 8:59:18 AM

    C:\Documents and Settings\Administrator>


    None of the client computers can connect through the console.  Also, if I get to the server remotely (through the web page), I can do everything except get to the console.


    Your help in solving the mystery is appreciated.

    Dizneykev
    Saturday, April 11, 2009 2:55 PM
  • Sorry, wasn't online the last days, so I could not answer earlier.
    You have two points in your IP configuration, which may cause a delay or even wrong name resolution:
    The DNS Server entry does not point to your router, but directly to the DNS servers of your ISP.
    Your Connection-specific DNS Suffix cinci.rr.com causes the domain name cinci.rr.com to be attached to each local name resolved by DNS.
    Both cause an attempt to resolve the name against DNS at your ISP, which will end usually in a timeout.
    Change the DHCP configuration in your router, so that it issues its own internal address as DNS server to the client and that it does not promote a DNS suffix at all.
    Best greetings from Germany
    Olaf
    Monday, April 13, 2009 8:21 PM
    Moderator
  • Ok, I am still having problems.  I can find not way to disable the router from promoting the DNS suffix of cinci.rr.com.  If I put my own host name in there, it will use that suffix instead, but there is not a way to prevent it from promoting one.  I have added the ip address of the router to the top of the DNS list.  It still times out.  The thing I do not understand is why I can ping by the name of the server without a problem?  I can also find everything by just entering the servername.  I can also ping from the server back tot he clients without an issue.  Also, the only thing that is different with my configuration is that I reloaded the server from the trial/evaluation version to the full OEM package.  Nothing on my network changed at all.  Any more suggestions would be greatly appreciated.  I am at my wits end with this.  All of the computers I have connected get connector updates immediately (like network warnings, know when the serve ris down, etc.)  They are all also backing up correctly and I can configure the backups when remoted into the server console.  I am just at a loss.  I have included the latest ipconfig /all results just in case it helps again.

    First, from the client:

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Kevin>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Daddy
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : cinci.rr.com

    Ethernet adapter Local Area Connection 3:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
    it Ethernet NIC (NDIS 6.0) #2
       Physical Address. . . . . . . . . : 00-1F-D0-80-FE-9F
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection 2:

       Connection-specific DNS Suffix  . : cinci.rr.com
       Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
    it Ethernet NIC (NDIS 6.0)
       Physical Address. . . . . . . . . : <removed>
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2002:ae67:9110:0:9402:f1f2:90e6:4b12(Pref
    erred)
       Temporary IPv6 Address. . . . . . : 2002:ae67:9110:0:f50c:94d2:e737:1545(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::9402:f1f2:90e6:4b12%16(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.113(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Tuesday, April 14, 2009 12:32:55 AM
       Lease Expires . . . . . . . . . . : Wednesday, April 15, 2009 12:32:55 AM
       Default Gateway . . . . . . . . . : fe80::221:29ff:febf:28f8%16
                                           192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 385884112
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0D-5C-B8-8E-00-15-58-51-12-AB

       DNS Servers . . . . . . . . . . . : 192.168.1.1
                                           65.24.7.10
                                           65.24.7.11
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : <removed>
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.cinci.rr.com
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 13:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : cinci.rr.com
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 23:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{1C8CDF11-44F3-44A1-B219-BDAC45CD4
    6DA}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    C:\Users\Kevin>


    Now, the results from the Server. 


    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

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

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : vaultdisney
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : cinci.rr.com

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : cinci.rr.com
       Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) PCI-E Gigabi
    t Ethernet NIC
       Physical Address. . . . . . . . . : <removed>
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 192.168.1.109
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.1
                                           65.24.7.10
                                           65.24.7.11
       Primary WINS Server . . . . . . . : 192.168.1.1
       Lease Obtained. . . . . . . . . . : Tuesday, April 14, 2009 12:34:04 AM
       Lease Expires . . . . . . . . . . : Wednesday, April 15, 2009 12:34:04 AM

    C:\Documents and Settings\Administrator>


    I am not sure why it is still getting the WINS server as the router ip.  I playes with that option (mostly becuase I had tried everythign else).  That setting has been removed from the configuration on the router.


    I anxiously await any additional help.


    Dizneykev
    Tuesday, April 14, 2009 4:50 AM
  • While you have added your router as DNS server, you have not removed the ISP entries. Windows only uses one of the entries, unless the tried DNS server is unreachable (and I I think also changes the used DNS server at all only in this case).
    The way DNS takes should be:
    Client tries to use cached entries to resolve the name (this includes the entries in the clients hosts file in c:\windows\system32\drivers\etc) - editing this file would be a workaround, but cause trouble in the future, in case the IP address of your server changes at a later time
    Client queries DNS server (=router)
    router decides, if the query gets forwarded to the DNS server of the ISP or will not be resolved via DNS (if you have attached the DNS suffix the name will always get the extension attached and DNS will try to resolve the name via the DNS server, which is authoritative for the domain in that suffix)
    if DNS name resolution fails, no other methods are tried

    So maybe, that the console tries always to resolve the name via DNS.
    You can use other methods, if these try to use NetBIOS over TCP/IP first.

    Which is the model of your router?
    Best greetings from Germany
    Olaf
    Tuesday, April 14, 2009 6:28 AM
    Moderator
  • I have a Linksys WRT610N router.  I have assigned all of the local ip addresses via DHCP first, but then I went in and made sure all of my addresses stay static by reserving their addresses by MAC.  So, I am not worried about the ip changing (unless I plug into the other NIC or have to replace a board, but I can easily modify the system to reassign the correct ip address).  I have tried adding the addresses of the Home Server as well as the clients into the local HOSTS file, but that made no change.  I still get the connection error.  The weird thing is, this error comes up so quickly (maybe 5-10 seconds).  It does not seem like a timeout issue to me.  Also, if it was name resolution, would I still be able to ping the computers by their name and not the ip address?  Would I not get the same sort of error?  Or, are you saying that with the way this is getting assigned that the homeserver thinks the name of itself is (server.cinci.rr.com) and thus is searching that domain suffix first for other computers when running the connector software?  I have been tempted to try to add a DNS server on my local network and could do that if I thought it would solve the issues, I am just not 100% sure that is what is going on.

    For a true test, what would happen if I unplug my router from the external Cable Modem.  Then, rebooted the router and allowed it to reconfigure (without the cinci.rr.com domain name).  Then, reconnect the clients.  If it still fails, have we proved that this is not the issue?

    I am willing to try anything at this point.  I am sure it has to be somethign simple, but for the life of me I cannot figure out what it is.

    Dizneykev
    Tuesday, April 14, 2009 12:57 PM
  • I have a Linksys WRT610N router.  I have assigned all of the local ip addresses via DHCP first, but then I went in and made sure all of my addresses stay static by reserving their addresses by MAC.  So, I am not worried about the ip changing (unless I plug into the other NIC or have to replace a board, but I can easily modify the system to reassign the correct ip address).  I have tried adding the addresses of the Home Server as well as the clients into the local HOSTS file, but that made no change. 
    that router is not a known troublemaker in the WHS context. Did you include the domain extension cinci.rr.com here for testing? And - "addresses"? The server should have only one address. If it is multihomed, this is not supported.
    I still get the connection error.  The weird thing is, this error comes up so quickly (maybe 5-10 seconds).  It does not seem like a timeout issue to me. 
    Could also be the answer, that server.cinci.rr.com is not known. On the client type nslookup server Which DNS server responds with which result?
    Also, if it was name resolution, would I still be able to ping the computers by their name and not the ip address?  Would I not get the same sort of error?  Or, are you saying that with the way this is getting assigned that the homeserver thinks the name of itself is (server.cinci.rr.com) and thus is searching that domain suffix first for other computers when running the connector software? 
    Exactly. This is what DNS suffixes cause.
    I have been tempted to try to add a DNS server on my local network and could do that if I thought it would solve the issues, I am just not 100% sure that is what is going on.

    Besides using the router as the only DNS server for the clients, there should be nothing else. (Finally it is still a home environment.) 
    For a true test, what would happen if I unplug my router from the external Cable Modem.  Then, rebooted the router and allowed it to reconfigure (without the cinci.rr.com domain name).  Then, reconnect the clients.  If it still fails, have we proved that this is not the issue?

    I am willing to try anything at this point.  I am sure it has to be somethign simple, but for the life of me I cannot figure out what it is.

    Which security suite/firewall you are using on the client?
    Best greetings from Germany
    Olaf
    Tuesday, April 14, 2009 2:16 PM
    Moderator
  • I would be interested in the results of a couple of ping tests, from a client machine on your network. Try to ping your server by name, and try again to ping it by it's LAN IP address. Post the results here.

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, April 14, 2009 3:43 PM
    Moderator
  • I have a Linksys WRT610N router.  I have assigned all of the local ip addresses via DHCP first, but then I went in and made sure all of my addresses stay static by reserving their addresses by MAC.  So, I am not worried about the ip changing (unless I plug into the other NIC or have to replace a board, but I can easily modify the system to reassign the correct ip address).  I have tried adding the addresses of the Home Server as well as the clients into the local HOSTS file, but that made no change. 
    that router is not a known troublemaker in the WHS context. Did you include the domain extension cinci.rr.com here for testing? And - "addresses"? The server should have only one address. If it is multihomed, this is not supported.
    I still get the connection error.  The weird thing is, this error comes up so quickly (maybe 5-10 seconds).  It does not seem like a timeout issue to me. 
    Could also be the answer, that server.cinci.rr.com is not known. On the client type nslookup server Which DNS server responds with which result?
    Also, if it was name resolution, would I still be able to ping the computers by their name and not the ip address?  Would I not get the same sort of error?  Or, are you saying that with the way this is getting assigned that the homeserver thinks the name of itself is (server.cinci.rr.com) and thus is searching that domain suffix first for other computers when running the connector software? 
    Exactly. This is what DNS suffixes cause.
    I have been tempted to try to add a DNS server on my local network and could do that if I thought it would solve the issues, I am just not 100% sure that is what is going on.

    Besides using the router as the only DNS server for the clients, there should be nothing else. (Finally it is still a home environment.) 
    For a true test, what would happen if I unplug my router from the external Cable Modem.  Then, rebooted the router and allowed it to reconfigure (without the cinci.rr.com domain name).  Then, reconnect the clients.  If it still fails, have we proved that this is not the issue?

    I am willing to try anything at this point.  I am sure it has to be somethign simple, but for the life of me I cannot figure out what it is.

    Which security suite/firewall you are using on the client?
    Best greetings from Germany
    Olaf
    When I refer to addresses, I mean that I have statically assigned all of my computers.  So, they have a reserved address on the DHCP Server.  I have done this for all of my essential pc's in the home.  Each PC or Server only has one network card, so they do not possess multiple ip addresses.  Sorry for the confusion.  I currently have my firewalls disabled on the machines when I am testing, but I use AVG Full version for ym anti-virus software.  I do not currently have any anti-virus loaded on the home server until I get things resolved.


    I can ping both boxes one way or the other via name or ip address and they return immediately.

    I have added the name of the server to the client's etc/hosts table now and it returns with the correct ip address.  I have also added an entry for a client computer to the server's etc/hosts file, it has no impact on the success of the connection.

    I even added an entery for homeserver.cinci.rr.com to the client etc/hosts and client.cicni.rr.com to the server's etc/host file and this does not work either.


    A nslookup for the server name tries to find it only at the address of 192.168.1.1 (the router's ip)  I get a domain unknown error.


    Still trying.


    Dizneykev



    Tuesday, April 14, 2009 8:50 PM
  • Just for reference, here are the results from the requested ping from the client pc.

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Kevin>ping vaultdisney

    Pinging vaultdisney [192.168.1.109] with 32 bytes of data:
    Reply from 192.168.1.109: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.109: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.109: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.109: bytes=32 time<1ms TTL=128

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

    C:\Users\Kevin>ping 192.168.1.109

    Pinging 192.168.1.109 with 32 bytes of data:
    Reply from 192.168.1.109: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.109: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.109: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.109: bytes=32 time<1ms TTL=128

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

    Please continue to try to help.  Maybe we are getting closer?  I wish there was a way to keep the cinci.rr.com DNS suffix from coming through.

    Just so I am sure, if I were to add the entry of this:

    192.168.1.109  vaultdisney.cinci.rr.com

    to the /etc/hosts file on the client pc, and I still cannot connect using the connector software prove anything?  Just for grins and giggles, I added the ip address of my client pc to the server /etc/hosts file as well (daddy.cinci.rr.com) with no change in the behaviour.  I even tried just the name without the dns suffix and it made no difference either.  I just cannot figure out what the problem may be.  It has to be something simple, since it worked 2 weeks ago with the trial version of the software.


    The fact that the backups and alerts and everythign are working (and all the shares for that matter) make me wonder what could be the problem.

    Dizneykev
    Wednesday, April 15, 2009 2:03 AM
  • Its definitively client stuff, so no reason to alter anyting on the servers hosts file.
    Does your client have more than one network interface cards? (This includes WLAN, Firewire and similar devices.) If yes, disable these or ensure at least, that in the network settings under Advanced/Advanced Settings the priority is set to the LAN adapter.
    Also, if there are any protocols besides TCP/IP (i.e. NetBIOS or IPX), uninstall them.

    And at least I should ask, if the server has an NVidia graphic card and you installed NVidia drivers.
    These tend to block RDP connections due to a lack of a certain system ressource, and since the console is only a special RDP session, this could be a reason as well.
    In this case you should see several informations pointing to RDPDD.DLL in the servers event log.

    Best greetings from Germany
    Olaf
    Wednesday, April 15, 2009 2:58 PM
    Moderator
  • Ok.  I have disabled the second network card on my client system with no change.  So far, I have WHS connector installed on 4 different computers on my network and none of them connect.  I do not have any Nvidia drivers installed on the WHS.  The way I have been able to administer the WHS currently is to connect to the server directly via an RDP session.  I know this is not technically supported, but it works without problem.  I can get to the RDP session by either typing in the name of my home server, or by ip address, they both work without hesitation.  I am completely baffled now.  I wish someone had an answer, as I am running out fo questions at this point.

    Dizneykev
    Wednesday, April 15, 2009 5:13 PM
  • Well, the last option which would come into mind, would be to try a fixed IP address on the client and server to reduce or eliminate router influence, entering only:
    IP address (from the same subnet as before, but outside of the range, which the router hands out)
    Subnet Mask
    Default Gateway (the router)
    DNS Server (the router)

    On Advanced TCP/IP settings of the LAN connection remove all DNS related suffixes, disable  Register this connections addresses in DNS, enable NetBIOS over TCP/IP on the WINS tab.

    Reboot the machines, and if necessary rerun discovery.exe on each client (in C:\Program Files\Windows Home Server) to reestablish the connection and adjust port forwarding in the router for Remote access to match the now fixed IP address of the server.

    Best greetings from Germany
    Olaf
    Friday, April 17, 2009 7:53 AM
    Moderator