Petri.com forums Home Forums Start Page Forums Frequently Asked Questions FAQ Member List Members List
Go Back   Petri IT Knowledgebase Forums > Server Operating Systems > Windows Server 2000 / 2003 / 2003 R2
Petri.com is happy to award RicklesP the title of Most Valuable Member !!!
Register Calendar Calendar Search Petri IT Knowledgebase Forums Search Todays Posts Today's Posts Mark Forums Read
Notices

"Network path was not found" when joining domain

"Network path was not found" when joining domain

this thread has 17 replies and has been viewed 184572 times

Closed Thread
 
Thread Tools Search this Thread Display Modes
  #1  
Old 7th June 2006, 12:21
JerryLee JerryLee is offline
Casual
Casual
 
 Join Date: Jun 2006
  6 month star 12 month star
 Posts: 6
 Reputation: JerryLee is on a distinguished road (10)
Default "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  
Old 7th June 2006, 14:19
hunaromerzai hunaromerzai is offline
Casual
Casual
 
 Join Date: Jun 2006
  6 month star 12 month star
 Posts: 1
 Reputation: hunaromerzai is on a distinguished road (10)
Thumbs up 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.

hunaromerzai@disability.gov.af
  #3  
Old 7th June 2006, 15:17
JerryLee JerryLee is offline
Casual
Casual
 
 Join Date: Jun 2006
  6 month star 12 month star
 Posts: 6
 Reputation: JerryLee is on a distinguished road (10)
Default Re: "Network path was not found" when joining domain

Quote:
Originally Posted by hunaromerzai
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.

hunaromerzai@disability.gov.af
Thanks for your reply.

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

- Jerry
  #4  
Old 7th June 2006, 15:35
JeremyW's Avatar
JeremyW JeremyW is offline
Moderator
 
 Join Date: May 2006
  6 month star 12 month star
 Location: Washington DC metro area
 Posts: 3,895
 Reputation: JeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to all (646)
Default 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
  #5  
Old 7th June 2006, 16:20
JerryLee JerryLee is offline
Casual
Casual
 
 Join Date: Jun 2006
  6 month star 12 month star
 Posts: 6
 Reputation: JerryLee is on a distinguished road (10)
Default 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 at 16:23..
  #6  
Old 7th June 2006, 16:46
JeremyW's Avatar
JeremyW JeremyW is offline
Moderator
 
 Join Date: May 2006
  6 month star 12 month star
 Location: Washington DC metro area
 Posts: 3,895
 Reputation: JeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to all (646)
Default Re: "Network path was not found" when joining domain

Quote:
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
  #7  
Old 7th June 2006, 18:53
biggles77's Avatar
biggles77 biggles77 is offline
Administrator
 
 Join Date: Dec 2003
  6 month star 12 month star
 Location: Nowhere that I like.
 Posts: 11,376
 Reputation: biggles77 is a splendid one to beholdbiggles77 is a splendid one to beholdbiggles77 is a splendid one to beholdbiggles77 is a splendid one to beholdbiggles77 is a splendid one to beholdbiggles77 is a splendid one to beholdbiggles77 is a splendid one to beholdbiggles77 is a splendid one to behold (948)
Default 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.
__________________
"There I stood at the bar, wearing a Mae West, no jacket, and beginning to leak blood from my torn boot. None of the golfers took any notice of me - after all, I wasn't a member!" Kenneth Lee - after being shot down during the Battle of Britain on the 18th August 1940.

************************************************** **********************
** Remember to give credit where credit is due and leave reputation points where appropriate **
************************************************** **********************
  #8  
Old 7th June 2006, 22:34
JeremyW's Avatar
JeremyW JeremyW is offline
Moderator
 
 Join Date: May 2006
  6 month star 12 month star
 Location: Washington DC metro area
 Posts: 3,895
 Reputation: JeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to all (646)
Default Re: "Network path was not found" when joining domain

Quote:
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
  #9  
Old 8th June 2006, 13:26
JerryLee JerryLee is offline
Casual
Casual
 
 Join Date: Jun 2006
  6 month star 12 month star
 Posts: 6
 Reputation: JerryLee is on a distinguished road (10)
Default Re: "Network path was not found" when joining domain

Quote:
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!
  #10  
Old 8th June 2006, 15:29
JeremyW's Avatar
JeremyW JeremyW is offline
Moderator
 
 Join Date: May 2006
  6 month star 12 month star
 Location: Washington DC metro area
 Posts: 3,895
 Reputation: JeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to allJeremyW is a name known to all (646)
Default 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
Closed Thread


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
automate joining AD domain (XP)? Possible? JRM Windows 2000 Pro, XP Pro 3 24th July 2006 19:42
Trouble joining new domain. BIGGY Windows Server 2000 / 2003 / 2003 R2 4 24th July 2006 19:41
joining domain alitoday Windows 2000 Pro, XP Pro 1 18th January 2006 17:33
automate joining AD domain (XP)? Possible? JRM Active Directory 1 7th October 2005 22:04
group strategy SpyD Active Directory 13 23rd May 2005 23:16


All times are GMT +3. The time now is 20:17.

Steel Blue 3.5.4 vBulletin Style ©2006 vBEnhanced
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
 

Valid XHTML 1.0!   Valid CSS!

Copyright 2005 Daniel Petri