Announcement

Collapse
No announcement yet.

"Network path was not found" when joining domain

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • "Network path was not found" when joining domain

    This problem seems to be quite common, but after reading several suggestions from different forums to fixing it I still haven't managed to get things to work.

    I'm trying to join a Windows XP Pro client to a Windows Server 2003 domain. After entering the domain name and clicking on "Change" in Computer Name Changes dialog box, I am prompted for a username and password. I enter a username and password (with administrator rights on the domain) but all I get is an error message saying: "The following error occurred attempting to join the domain 'domainname.com': The network path was not found".

    The same thing happens with a Windows 2000 client when I try to join the domain (called domainname.com here; that's not the real domain name of course).

    On the domain controller I've used dcpromo.exe to install Active Directory and DNS.

    I've added a new user to AD and made it a member of the Domain Admins group.

    The forward lookup zones in DNS shows two folders: _msdcs.domainname.com and domainname.com. The latter had six folders and three files in it at first: one State of Authority, one Name Server and one Host file. The Host file's name is "domainname" and its data is the ip address (let's say it's 197.198.220.250) of the Windows Server 2003 DC.

    I then added the client under domainname.com: the name is "clientname" and the data is the static IP address of the client (let's say it's 197.198.220.251). I'm not sure if I'm supposed to add this manually or not.

    I've also added a reverse lookup zone to DNS and given it a network ID of 197.198.220 and pointed it to "domainname.com". After that, I've added a PTR record with host IP number 197.198.220.0 and host name "servername.domainname.com". I'm not sure if this is correct.

    Then, I've manually added the client computer under "Computers" in DNS. I'm not sure if I'm supposed to do this manually either.

    "nslookup" from client gives this:

    Default server: servername.domainname.com
    Address: 197.198.220.250

    Pinging with domainname.com from the client works, as does pinging with servername.domainname.com. Pinging with domainname alone does not work.

    Pinging the client from the server by IP works. Pinging it with clientname works only after I've manually added the records to DNS.

    "netdiag" shows no problems; DNS test passes.

    "net view domainname.com" from the client gives this:
    "System error 53 has occurred. The network path was not found", although I'm not sure if this is even supposed to work.

    NetBIOS is enabled on the client and on the server.

    The primary DNS server address on the client is 197.198.220.250 (the server's IP). There is no secondary address. The primary DNS address on the server is the same IP. The secondary address is the DNS address given to us by the ISP.

    The weird thing is, I actually got the domain joining working yesterday for a while, but I couldn't log in the domain from either of the clients. Netdiag showed that the DNS test failed, so I decided to remove the DNS and AD roles from the server and install them again. Now the DNS test passes but the network path is still not found.

    If there's some required info that I've missed, I'd be happy to post it.

    Thanks,

    - Jerry

  • #2
    Re: "Network path was not found" when joining domain

    Make sure that you don't have firewall at your server side.

    If so turn off the firewall or manually allow the client computer to access your server.

    If you are using additional DCs then make sure to put the AD Server that is holding Global Catalog.

    I am sure this will help you more.

    [email protected]

    Comment


    • #3
      Re: "Network path was not found" when joining domain

      Thanks for your reply.

      Both firewalls have been turned off. There is only one DC.

      - Jerry

      Comment


      • #4
        Re: "Network path was not found" when joining domain

        Did you let dcpromo install DNS for you?

        Run dcdiag from both the DC and the client.
        Regards,
        Jeremy

        Network Consultant/Engineer
        Baltimore - Washington area and beyond
        www.gma-cpa.com

        Comment


        • #5
          Re: "Network path was not found" when joining domain

          I ran dcpromo and installed AD then DNS, yes.

          Here's the result from dcdiag using the domain controller SERVERNAME:

          -----
          C:\>dcdiag.exe

          Domain Controller Diagnosis

          Performing initial setup:
          Done gathering initial info.

          Doing initial required tests

          Testing server: Default-First-Site-Name\SERVERNAME
          Starting test: Connectivity
          ......................... SERVERNAME passed test Connectivity

          Doing primary tests

          Testing server: Default-First-Site-Name\SERVERNAME
          Starting test: Replications
          ......................... SERVERNAME passed test Replications
          Starting test: NCSecDesc
          ......................... SERVERNAME passed test NCSecDesc
          Starting test: NetLogons
          ......................... SERVERNAME passed test NetLogons
          Starting test: Advertising
          ......................... SERVERNAME passed test Advertising
          Starting test: KnowsOfRoleHolders
          ......................... SERVERNAME passed test KnowsOfRoleHolders
          Starting test: RidManager
          ......................... SERVERNAME passed test RidManager
          Starting test: MachineAccount
          ......................... SERVERNAME passed test MachineAccount
          Starting test: Services
          ......................... SERVERNAME passed test Services
          Starting test: ObjectsReplicated
          ......................... SERVERNAME passed test ObjectsReplicated
          Starting test: frssysvol
          ......................... SERVERNAME passed test frssysvol
          Starting test: frsevent
          ......................... SERVERNAME passed test frsevent
          Starting test: kccevent
          ......................... SERVERNAME passed test kccevent
          Starting test: systemlog
          ......................... SERVERNAME passed test systemlog
          Starting test: VerifyReferences
          ......................... SERVERNAME passed test VerifyReferences

          Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
          ......................... ForestDnsZones passed test CrossRefValidation

          Starting test: CheckSDRefDom
          ......................... ForestDnsZones passed test CheckSDRefDom

          Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
          ......................... DomainDnsZones passed test CrossRefValidation

          Starting test: CheckSDRefDom
          ......................... DomainDnsZones passed test CheckSDRefDom

          Running partition tests on : Schema
          Starting test: CrossRefValidation
          ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
          ......................... Schema passed test CheckSDRefDom

          Running partition tests on : Configuration
          Starting test: CrossRefValidation
          ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
          ......................... Configuration passed test CheckSDRefDom

          Running partition tests on : DOMAINNAME
          Starting test: CrossRefValidation
          ......................... DOMAINNAME passed test CrossRefValidation
          Starting test: CheckSDRefDom
          ......................... DOMAINNAME passed test CheckSDRefDom

          Running enterprise tests on : DOMAINNAME.COM
          Starting test: Intersite
          ......................... DOMAINNAME.COM passed test Intersite
          Starting test: FsmoCheck
          ......................... DOMAINNAME.COM passed test FsmoCheck

          ---

          I couldn't find dcdiag for Windows XP, so I ran it on the Windows 2000 client:

          C:\Program Files\Support Tools>dcdiag /sOMAINNAME

          Domain Controller Diagnosis

          Performing initial setup:
          An error cocured during DNS host lookup

          --

          C:\Program Files\Support Tools>dcdiag /sOMAINNAME.COM

          Domain Controller Diagnosis

          Performing initial setup:
          The host Check the DNS server, DHCP, server name, etc

          --

          C:\Program Files\Support Tools>dcdiag /s:SERVERNAME

          Domain Controller Diagnosis

          Performing initial setup:
          The host Check the DNS server, DHCP, server name, etc
          Last edited by JerryLee; 7th June 2006, 14:23.

          Comment


          • #6
            Re: "Network path was not found" when joining domain

            Originally posted by JerryLee
            An error cocured during DNS host lookup
            There is obviouly a DNS problem.
            -Verify the clients have the proper preferred DNS server (which you said you did)
            -Check to make sure DNS has dynamic updates enabled
            -Verify that the "_ldap._tcp.dc._msdcs.DomainName" is present
            %systemroot%\System32\Config\Netlogon.dns contains all the DNS entries that are required for AD to function. This file is created during dcpromo setup
            Regards,
            Jeremy

            Network Consultant/Engineer
            Baltimore - Washington area and beyond
            www.gma-cpa.com

            Comment


            • #7
              Re: "Network path was not found" when joining domain

              Do you have DHCP running on the server? Check for spelling and punctuation errors in the domain name. Use ipconfig /all and check the DNS Suffix Search List for errors.

              When joining the client to the domain, try using username = administrator\domainname.com and password.
              11 was a racehorse.
              22 was 12
              1111 race 1 day
              22112


              ************************************************** * ************************************************** ***********
              ** Remember to give credit where credit is due and click the LIKE option in the bottom right corner **
              ************************************************** ************************************************** ****** * *****

              Comment


              • #8
                Re: "Network path was not found" when joining domain

                Originally posted by biggles77
                When joining the client to the domain, try using username = administrator\domainname.com and password.
                Don't you mean "domainname.com\administrator" ?...
                Regards,
                Jeremy

                Network Consultant/Engineer
                Baltimore - Washington area and beyond
                www.gma-cpa.com

                Comment


                • #9
                  Re: "Network path was not found" when joining domain

                  Originally posted by JeremyW
                  There is obviouly a DNS problem.
                  -Verify the clients have the proper preferred DNS server (which you said you did)
                  -Check to make sure DNS has dynamic updates enabled
                  -Verify that the "_ldap._tcp.dc._msdcs.DomainName" is present
                  %systemroot%\System32\Config\Netlogon.dns contains all the DNS entries that are required for AD to function. This file is created during dcpromo setup
                  They have the correct DNS server.

                  Dynamic updates are enabled.

                  There is an _ldap record (Data: [0][100][389]SERVERNAME.DOMAINNAME.COM)
                  under _msdcs.DomainName -> dc -> _tcp in DNS, if that's what you mean. There are similar _ldap records under almost every subfolder of _msdcs_DomainName.

                  Netlogon.dns looks like this:

                  --

                  SRV 0 100 389 SERVERNAME.SERVERNAME.local.
                  SERVERNAME.com. 600 IN A 195.197.229.244
                  _ldap._tcp.SERVERNAME.com. 600 IN SRV 0 100 389 SERVERNAME.DOMAINNAME.COM.
                  _ldap._tcp.Default-First-Site-Name._sites.SERVERNAME.com. 600 IN SRV 0 100 389
                  SERVERNAME.DOMAINNAME.COM.
                  _ldap._tcp.pdc._msdcs.SERVERNAME.com. 600 IN SRV 0 100 389 SERVERNAME.DOMAINNAME.COM.
                  _ldap._tcp.gc._msdcs.SERVERNAME.com. 600 IN SRV 0 100 3268 SERVERNAME.DOMAINNAME.COM.
                  _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.SERVERNAME.com. 600 IN SRV 0
                  100 3268 SERVERNAME.DOMAINNAME.COM.
                  _ldap._tcp.c556035b-accd-4819-9fc0-01fb081dd06d.domains._msdcs.SERVERNAME.com.
                  600 IN SRV 0 100 389 SERVERNAME.DOMAINNAME.COM.
                  gc._msdcs.SERVERNAME.com. 600 IN A 195.197.229.244
                  102252e0-ff8a-445a-b1f5-0164170aa705._msdcs.SERVERNAME.com. 600 IN CNAME
                  SERVERNAME.DOMAINNAME.COM.
                  _kerberos._tcp.dc._msdcs.SERVERNAME.com. 600 IN SRV 0 100 88 SERVERNAME.DOMAINNAME.COM.
                  _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.SERVERNAME.com. 600 IN
                  SRV 0 100 88 SERVERNAME.DOMAINNAME.COM.
                  _ldap._tcp.dc._msdcs.SERVERNAME.com. 600 IN SRV 0 100 389 SERVERNAME.DOMAINNAME.COM.
                  _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.SERVERNAME.com. 600 IN SRV 0
                  100 389 SERVERNAME.DOMAINNAME.COM.
                  _kerberos._tcp.SERVERNAME.com. 600 IN SRV 0 100 88 SERVERNAME.DOMAINNAME.COM.
                  _kerberos._tcp.Default-First-Site-Name._sites.SERVERNAME.com. 600 IN SRV 0 100 88
                  SERVERNAME.DOMAINNAME.COM.
                  _gc._tcp.SERVERNAME.com. 600 IN SRV 0 100 3268 SERVERNAME.DOMAINNAME.COM.
                  _gc._tcp.Default-First-Site-Name._sites.SERVERNAME.com. 600 IN SRV 0 100 3268
                  SERVERNAME.DOMAINNAME.COM.
                  _kerberos._udp.SERVERNAME.com. 600 IN SRV 0 100 88 SERVERNAME.DOMAINNAME.COM.
                  _kpasswd._tcp.SERVERNAME.com. 600 IN SRV 0 100 464 SERVERNAME.DOMAINNAME.COM.
                  _kpasswd._udp.SERVERNAME.com. 600 IN SRV 0 100 464 SERVERNAME.DOMAINNAME.COM.
                  DomainDnsZones.SERVERNAME.com. 600 IN A 195.197.229.244
                  _ldap._tcp.DomainDnsZones.SERVERNAME.com. 600 IN SRV 0 100 389
                  SERVERNAME.DOMAINNAME.COM.
                  _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.SERVERNAME.com. 600 IN
                  SRV 0 100 389 SERVERNAME.DOMAINNAME.COM.
                  ForestDnsZones.SERVERNAME.com. 600 IN A 195.197.229.244
                  _ldap._tcp.ForestDnsZones.SERVERNAME.com. 600 IN SRV 0 100 389
                  SERVERNAME.DOMAINNAME.COM.
                  _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.ikepa.com. 600 IN
                  SRV 0 100 389 SERVERNAME.DOMAINNAME.COM.

                  --

                  There are also old records called SERVERNAME.DOMAINNAME.local from a previous attempt that have been commented with ";".

                  ipconfig /all on the server gives this:

                  --

                  Windows IP Configuration



                  Host Name . . . . . . . . . . . . : SERVERNAME

                  Primary Dns Suffix . . . . . . . : DOMAINNAME.com

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

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

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

                  DNS Suffix Search List. . . . . . : DOMAINNAME.com



                  Ethernet adapter Local Area Connection:



                  Connection-specific DNS Suffix . :

                  Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For
                  Complete PC Management NIC (3C905C-TX)

                  Physical Address. . . . . . . . . : 00-02-1E-F6-95-16

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

                  IP Address. . . . . . . . . . . . : 197.198.220.244

                  Subnet Mask . . . . . . . . . . . : 255.255.255.248

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

                  DNS Servers . . . . . . . . . . . : 197.198.220.244

                  Primary WINS Server . . . . . . . : 197.198.220.244

                  --

                  Note that I changed the IP addresses. 197.198.220.244 is the server's IP here.

                  I also tried to join it by using DOMAINNAME.COM\Administrator, but I got the same error.

                  Btw. your help is much appreciated!

                  Comment


                  • #10
                    Re: "Network path was not found" when joining domain

                    Is 255.255.255.248 really your netmask? If so, do you only have 4 clients or do you have multiple subnets?

                    This is what I would do:
                    -Delete all the DNS records that you created manually
                    -Install and configure the DHCP server service on your DC
                    -Set the clients to use the DHCP server

                    The clients should be able to update the DNS server automatically. The clients shouldn't need an A record to join the domain.

                    I think there's something missing though... could you describe your network topology? And if you're using private IP addresses could you use the actual numbers? Addresses in the private range are 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, 192.168.0.0 - 192.168.255.255
                    Regards,
                    Jeremy

                    Network Consultant/Engineer
                    Baltimore - Washington area and beyond
                    www.gma-cpa.com

                    Comment


                    • #11
                      Re: "Network path was not found" when joining domain

                      Originally posted by JeremyW
                      Is 255.255.255.248 really your netmask? If so, do you only have 4 clients or do you have multiple subnets?

                      This is what I would do:
                      -Delete all the DNS records that you created manually
                      -Install and configure the DHCP server service on your DC
                      -Set the clients to use the DHCP server

                      The clients should be able to update the DNS server automatically. The clients shouldn't need an A record to join the domain.

                      I think there's something missing though... could you describe your network topology? And if you're using private IP addresses could you use the actual numbers? Addresses in the private range are 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, 192.168.0.0 - 192.168.255.255
                      255.255.255.248 is really our netmask. We only have 2 clients. It's a very small company.

                      We're not using private addresses. All computers have a static IP.

                      I can try configuring the DHCP service as a last resort, but it seems it might only get me in more trouble. I thought it would've been easier since we don't really need DHCP.

                      The line from the ISP is connected to a switch; the server and the two clients are all connected to the switch.

                      If I understand correctly, the "default gateway" in TCP/IP properties points to the switch. Its IP address is xxx.xxx.xxx.241. The IP of the server is xxx.xxx.xxx.244, and the two clients are xxx.xxx.xxx.245 and xxx.xxx.xxx.246. The others are not in use.

                      What's strange to me is that before I manually add A records in DNS I can't ping other computers by name, only by IP address. After adding them the conversion works both ways.

                      There's nothing in Netlogon.dns that begins with "_ldap._tcp.dc." - is that correct or should it be there?
                      Last edited by JerryLee; 8th June 2006, 14:11.

                      Comment


                      • #12
                        Re: "Network path was not found" when joining domain

                        Your problem is the way you have your network setup.

                        Windows XP relies heavilly on DNS and will automatically try and find the DNS server you have specified in your TCP/IP properties. This i would imagine is your ISP's DNS server. Then when the machine contacts the DNS server to query for a DC for the your domain name it fails thus the error.

                        What you wold be better doing is setting up a proper domain internally first. For this i would highly recommend using the 192.168.0.0/255.255.255.0 address then subnetting there to give you your 4 addresses that you need.

                        So in my opinion you would setup your machines thus.

                        Server

                        IP - 192.168.0.1 SNM - 255.255.255.248

                        Client 1

                        IP - 192.168.0.3 SNM - 255.255.255.248 DNS - 192.168.0.1

                        Client 2

                        IP - 192.168.0.4 SNM - 255.255.255.248 DNS - 192.168.0.1

                        I would also recommend getting a router on your internet line and setting the external inteface to one of the public IP's that you have and the internal interface to one of you internal IP's

                        Router

                        External
                        IP 1.1.1.1

                        Intenal
                        IP 192.168.0.5

                        Hopefully this will help

                        Comment


                        • #13
                          Re: "Network path was not found" when joining domain

                          Originally posted by JeremyW
                          Don't you mean "domainname.com\administrator" ?...
                          Bloody keyboard, always typing the important stuff backwards. Thanks Jeremy, looked wrong when I typed it @ 2.45am local but brain was more dead than normal.
                          11 was a racehorse.
                          22 was 12
                          1111 race 1 day
                          22112


                          ************************************************** * ************************************************** ***********
                          ** Remember to give credit where credit is due and click the LIKE option in the bottom right corner **
                          ************************************************** ************************************************** ****** * *****

                          Comment


                          • #14
                            Re: "Network path was not found" when joining domain

                            Originally posted by wullieb1
                            Your problem is the way you have your network setup.

                            Windows XP relies heavilly on DNS and will automatically try and find the DNS server you have specified in your TCP/IP properties. This i would imagine is your ISP's DNS server. Then when the machine contacts the DNS server to query for a DC for the your domain name it fails thus the error.

                            What you wold be better doing is setting up a proper domain internally first. For this i would highly recommend using the 192.168.0.0/255.255.255.0 address then subnetting there to give you your 4 addresses that you need.

                            So in my opinion you would setup your machines thus.

                            Server

                            IP - 192.168.0.1 SNM - 255.255.255.248

                            Client 1

                            IP - 192.168.0.3 SNM - 255.255.255.248 DNS - 192.168.0.1

                            Client 2

                            IP - 192.168.0.4 SNM - 255.255.255.248 DNS - 192.168.0.1

                            I would also recommend getting a router on your internet line and setting the external inteface to one of the public IP's that you have and the internal interface to one of you internal IP's

                            Router

                            External
                            IP 1.1.1.1

                            Intenal
                            IP 192.168.0.5

                            Hopefully this will help
                            Thank you for your reply. I will try that if you think that is causing the problem. However, the DNS server in the TCP/IP properties is not the DNS of the ISP - it is the IP of the server aka domain controller. This is true for all the computers, both clients and the server.

                            If I use the DNS of the ISP, then pinging with name fails. Currently it works.

                            Comment


                            • #15
                              Re: "Network path was not found" when joining domain

                              I dont know how relevant my posting is, but i thought this might help someone. Infact I stumbled up on this post as me too was facing the same problem. Ok this is what helped me out. Pls check if "Client For Microsoft Networks" is disabled from the Network Connection properties pages. I found this was disabled at one of my client place and wasted my so much time. But sometimes brain doesnt work as we want

                              Hope it might help someone
                              Regards
                              Dotfish

                              Comment

                              Working...
                              X