locked
console and RDC cannot see WHS, but backup and share folders work fine? RRS feed

  • Question

  • I had to reinstall WHS, and use only Vista 64 clients.
    So now the server is up, and backups are running, but I cannot connect with the HWS console, or with RDC?
    Both tell menb the server is not here.
    Network neighbor hood see the server, and I can ping it.
    Tried HOSTS file entry, but does not change anything.

    Please help.

    Michael 
    Friday, November 21, 2008 3:18 PM

All replies

  • Michael,

    The first thing to try, Navigate on each of your Clients with Windows explorer, to the ' Program Files/Windows Home Server ' folder, from there 'double-click' on Discovery.exe', this will search your network for your server and re-set the appropriate paths. This is assuming that the server IP address has changed from the original, so if this doesn't work, let us know.

    Good luck,

    Colin




    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Friday, November 21, 2008 3:23 PM
    Moderator
  • Hi Michael,
    let me assume you have a NVidia or ATI video card in your Home Server?
    In this case try to import the following lines on your server  after saving them in a text file with extension .reg: 

    Windows Registry Editor Version 5.00
     
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
    "SessionImageSize"=dword:00000020

    Reboot and check, if the problem is solved.
    Best greetings from Germany
    Olaf
    Friday, November 21, 2008 3:25 PM
    Moderator
  • ok, done that, passed, but Console still give me the error meesage of "Password Invalid", and if I debug the consol it tells the server ios not there.
    RDC still does not work.

    Are you recommending HOSTS file set for the IP address of not?
    Friday, November 21, 2008 3:59 PM
  • Well. YEEEAAAHH.

    This solved the problem.

    Correct NVIDIA graphic and mother board

    Thansk so much>

    Friday, November 21, 2008 4:01 PM
  • ok, saga continues.

    Back works, shared folders are here. disocery.exe reconnets to server, but console does not startup any more, no ping, and no RDC.

    Thansk for any additional help.

    Saturday, November 22, 2008 2:45 AM
  • Hello,
    this seems to be a name resolution problem now.
    Please log in to the server locally, open a command line, type
    ipconfig /all
    and post the output here.
    Do the same for a client.
    On the client, what is the output of
    nslookup server
    and
    nbtstat -A IP Address of your server
    While on the server, check, if the settings for the Remotedesktop exception in the Windows Firewall are still correct. Try also to uncheck the Remotedesktop allowance in Control Panel/System/Remote tab, apply and enable this again.
    Check the event log for error messages, warnings or informations regarding rdp connections.
    Finally reboot the client and the server.

    Does a ping to the IP address of your server work?
    Do you have a 3rd party security suite installed? It's firewall may also block communication between client and WHS.

    Best greetings from Germany
    Olaf
    Saturday, November 22, 2008 10:41 AM
    Moderator
  • Olaf,

    thanks for the tips. While collecting all this data.. tried diabling my Norton 360 on the client, and then was able to connect to the server, even ping the name.
    I enabled it again and it still connects, very strange though.
    Anyway.

    Ping with IP worked, ping with name did not.

    nslook server on the client, times out without any information.


    C:\Users\Mickey>nbtstat -A 192.168.0.196

    Local Area Connection 2:
    Node IpAddress: [192.168.0.198] Scope Id: []

               NetBIOS Remote Machine Name Table

           Name               Type         Status
        ---------------------------------------------
        SAUTERSERVER01 <00>  UNIQUE      Registered
        WORKGROUP      <00>  GROUP       Registered
        SAUTERSERVER01 <20>  UNIQUE      Registered
        WORKGROUP      <1E>  GROUP       Registered

        MAC Address = 00-04-4B-03-C1-1F


    Local Area Connection:
    Node IpAddress: [192.168.0.199] Scope Id: []

               NetBIOS Remote Machine Name Table

           Name               Type         Status
        ---------------------------------------------
        SAUTERSERVER01 <00>  UNIQUE      Registered
        WORKGROUP      <00>  GROUP       Registered
        SAUTERSERVER01 <20>  UNIQUE      Registered
        WORKGROUP      <1E>  GROUP       Registered

        MAC Address = 00-04-4B-03-C1-1F


    ns server lookup


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : sauterserver01
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : hsd1.ma.comcast.net.

    Ethernet adapter Local Area Connection 3:

       Connection-specific DNS Suffix  . : hsd1.ma.comcast.net.
       Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
       Physical Address. . . . . . . . . : 00-04-4B-03-C1-1F
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 192.168.0.196
       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. . . . . . . . . . : Saturday, November 22, 2008 4:32:33 AM
       Lease Expires . . . . . . . . . . : Sunday, November 23, 2008 4:32:33 AM


    Hope that's for now. Rebooted etc.
    Saturday, November 22, 2008 2:10 PM
  • Ok, other finding.

    IT'S RANDOM.

    Network traffic on my own network???
    Saturday, November 22, 2008 4:11 PM
  • Hi,
    random name resolution problems can have various reasons (besides a changed IP address due to router downtime):
    • If a client is multihomed or has mutliple network protocols and the LAN adapter is not the primary adapter (in network properties in menu Advanced/Advanced settings), it may try to communicate via other adapters first, which at least will cause timing behaviors.
    • If the server is multihomed you may experience the same with responses from the server.
    • NetBIOS over TCP/IP seems not to be enabled on the server.
    • Short time after boot up the (NetBIOS) names may not be provided to the browser master in network.
    Try to remove the DNS Suffix Search List entry (this may be set in the router configuration), since this has also influence where to search the server.

    An unsupported workaround would also be, to add a line with IP address and server name into the clients hosts file (in Windows\system32\drivers\etc). The danger with such manual adjustments is later troubleshooting: If the router was down or gets changed or you reinstall the server, the server may get a different IP address. This  may lead to a situation that the client tries to resolve via an outdated record in the hosts file and will fail.

    Best greetings from Germany
    Olaf
    Saturday, November 22, 2008 5:43 PM
    Moderator