locked
Connector not connecting on XP machine. RRS feed

  • Question

  • I have my WHS up and running successfully but was unable to successfully install the Connector on my XP machine with the provided CD.  It kept telling me that the no server could be found.  I did find that any attempts to access the server through http://WHS were routing out to the internet and accessing some domain squatting site.

    I was able to browse to my machine (\\WHS\) and successfully complete the install from the shared Programs folder (\\Whs\Software\Home Server Connector Software).  The software setup, configured the backup routine for the XP machine so I thought I was good to go until I tried to access the connector console.  I put in my password but I get an error that "the computer can't connect to the home server.  check your network connection and if the server was recently rebooted, try again in a few minutes".

    I added the console app to the XP windows firewall (C:\Program Files\Windows Home Server\WHSConsoleClient.exe) and there is also an entry for "Windows Home Server Connector" (C:\Program Files\Windows Home Server\Discovery.exe).

    Any ideas?  I'm thinking it's a DNS issue based on my results with http://WHS
    Tuesday, March 17, 2009 3:38 PM

Answers

  • I took the XP machine off of the domain and now it's working.

    Thanks for the help Olaf!
    • Marked as answer by idburns Wednesday, March 18, 2009 3:24 PM
    Wednesday, March 18, 2009 3:24 PM

All replies

  • Hi,
    can you post the output of the command
    ipconfig /all
    from both the client and the server?
    Best greetings from Germany
    Olaf
    Tuesday, March 17, 2009 11:10 PM
    Moderator
  • XP Machine
    Windows IP Configuration

            Host Name . . . . . . . . . . . . : Intel
            Primary Dns Suffix  . . . . . . . : hostileterritory.org
            Node Type . . . . . . . . . . . . : Unknown
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
            DNS Suffix Search List. . . . . . : hostileterritory.org

    Ethernet adapter Local Area Connection:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) PCI-E G
            Physical Address. . . . . . . . . : <removed>
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.1.5
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.1.1
            DNS Servers . . . . . . . . . . . : 71.252.0.12
                                                68.237.161.12



    WHS

    Windows IP Configuration

            Host Name . . . . . . . . . . . . : whs
            Primary Dns Suffix  . . . . . . . :
            Node Type . . . . . . . . . . . . : Unknown
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mpbs Ethernet
            Physical Address. . . . . . . . . : <removed>
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.1.3
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.1.1
            DNS Servers . . . . . . . . . . . : 71.252.0.12
                                                68.237.161.12

    It's got something to do with the dns of hostileterritory.org I think...  I used to have a domain server with that domain name and this machine used to be on it.

    Thanks Olaf!
    Wednesday, March 18, 2009 12:56 AM
  • Hi,
    both, using that Primary DNS suffix, the DNS Suffix Search list and configuring external DNS servers instead of the internal IP address of the router may cause name resolution problems:
    The client searches for a name via DNS and asks his DNS server (and attaches also the DNS suffix to the query).
    In your configuration it is the DNS server of the ISP.
    So the query goes out to the DNS server of the ISP, which may either not find anything or even find a server with the same name in the wanted domain and delivers the wrong address.
    The first will cause potentially a timeout or work, the second will definitively fail.
    Best greetings from Germany
    Olaf
    • Marked as answer by idburns Wednesday, March 18, 2009 3:24 PM
    • Unmarked as answer by idburns Wednesday, March 18, 2009 3:24 PM
    Wednesday, March 18, 2009 9:59 AM
    Moderator
  • How do I fix it?  Do I have to remove the XP machine from the domain and go to logging into a workgroup?
    Wednesday, March 18, 2009 1:05 PM
  • I took the XP machine off of the domain and now it's working.

    Thanks for the help Olaf!
    • Marked as answer by idburns Wednesday, March 18, 2009 3:24 PM
    Wednesday, March 18, 2009 3:24 PM
  • idburns said:

    How do I fix it?  Do I have to remove the XP machine from the domain and go to logging into a workgroup?

    I'm not sure, if the machine is really a domain member (without a Windows domain controller in the original sense).
    Anyway, the entries are either set by the DHCP server or self made or both.
    Self configured items you get changed by opening Control Panel/Network Connections, right click the LAN connection and select Properties.
    Double click Internet Protocol (TCP/IP).
    If there are hard coded DNS server entries, remove them and change them against 192.168.1.1 (if the assignment of the IP addresses happens via DHCP, this is configured in the router and may have to changed there.
    Click Advanced to remove the DNS Suffix related entries.
    You can also uncheck Register this connections  ... on the DNS tab.
    (Maybe the exact wording is slightly different.)
    Reboot the machine(s) after the changes are done.

    Best greetings from Germany
    Olaf

    Wednesday, March 18, 2009 3:25 PM
    Moderator