Solved

DC List test failed - Failed to enumerate DC's by using the browser.  [ERROR_BAD_NETPATH]

Posted on 2004-09-19
13
12,490 Views
Last Modified: 2012-06-27
When I net a NETDIAG, it shows that DC List test failed.  I've run netdiag /fix with no joy.  Please tell me how to fix this error.
0
Comment
Question by:tcjcspen
  • 6
  • 6
13 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 12095526
What was your reason for doing this test? If there are other problems there could be an easy resolution.

In the meantime make sure that your DNS settings are correct. The client machines should be set to use the domain controllers for DNS ONLY and the AD DCs should be pointing at themselves only. No External DNS servers anywhere in the network configuration - except for DNS forwarders on the server (if required).

Simon.
0
 

Author Comment

by:tcjcspen
ID: 12097184
I ran a netdiag becasue I am having trouble getting a desktop on the network.  When I try to join the network I get the following error message; "Windows cannot find the network path.  Verify that the network path is correct and the destination computer is not busy or turned off".
0
 
LVL 104

Expert Comment

by:Sembee
ID: 12097460
Could you clarify "getting a desktop on the network"?

Is this accessing a server?
Is this adding the workstation to a domain?
If it is a domain, is the machine already a domain?

It is usual tests time:

Can you ping the server by name, FQDN and IP address?
Presuming that this is an AD domain, are the DNS settings correct?

Simon.
0
 

Author Comment

by:tcjcspen
ID: 12097655
Simon,

This is my first time to set up a server, so bear with me.  I have a domain set up named "trueblue".  I have a laptop alraedy on the domain but I cannot get this desktop on the domain.  I have the following functions set up on the server:  DNS, DHCP, Domain Controller and file server.  Being that I'm new, I believe the DNS setting are correct but I cannot say with 100% certainty.

When I pinged the server from the desktop using spenserver, spenserver.trueblue.local and 192.168.1.5, all three times the server replied with 0% loss.

Chris
0
 
LVL 104

Expert Comment

by:Sembee
ID: 12102653
0% loss is good - that means that the Workstation can see the server.
How exactly are you trying to get the workstation on to the domain?

You haven't said what OS the workstation is running, but if it is Windows 2000 or XP then it needs to join the domain. If that is what you are trying to do then please clarify.

It might just be quicker to say what you are trying to do, and then we can point out where you are going wrong.

Simon.
0
 

Author Comment

by:tcjcspen
ID: 12110260
Simon,

I'm trying to just say what I'm doing but I'm sure we are speaking different languages.  I'm trying to join an XP Pro machine (desktop) to a domain that I have created on a machine running Windows Server 2003 .  I already have one machine (laptop) running XP Pro joined to the domain.  However, when I try to change the name of the of the desktop to join the domain (trueblue), I get the following error message: "Windows cannot find the network path.  Verify that the network path is correct and the destination computer is not busy or turned off".  But, as you say, and the pings show, the client can see the server, it just can't join the domain for some reason.

Now, becasue of this error message, I ran a netdiag on the server and came up with the error message that I started this threat with.

Again, all I'm trying to do is get the desktop, which can "see" the server, to join the domain but every time I try I get the error message about not being able to find the network path, as already noted above.

Chris
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 104

Expert Comment

by:Sembee
ID: 12127977
I don't know why there was a request to close this question...

Now that I have seen what you are trying to do, the first thing you must check is DNS. DNS must be pointing at the domain controller ONLY. This will allow it to connect to the domain controller and is the main cause of machines failing to join the domain. The error message that you have outlined at the start of this thread is a clear indication of the machine failing to see the domain controller.

Have you used this machine name before? If so then that could also be causing the problem - you should remove all trace of it from the domain.

I asked for clarification because "getting the machine on the network" could mean any number of things.
Adding the machine to the domain is something very specific.

Simon.
0
 

Author Comment

by:tcjcspen
ID: 12149133
Simon,

I was trying to cancel this question becasue the motherboard popped on the desktop in question, not becasue you asked for clarification.  I didn't know how long it would be down and if it would still be a problem after it was fixed.  As it turns out, I went ahead and changed the motherboard and recovered the data from my hard drives, but I still can't join the domain.  So, let's forget the cancel request and try to get this computer on my domain.  

Here is what I've accomplished:

I took your suggestion from the last post and went into the DNS server looking for any errors I could find, and I did finally find something.  Under the "Forward Lookup Zones", I have three things listed:  msdcs.trueblue.local, trueblue.local, and truebluehomes.com.  The error was under the msdcs.trueblue.local, the name of the name server was wrong, so I changed it.  Then I re-ran a netdiag and a dcdiag and everything passed.  So, there is no longer a DC List test failure.


Unfortunately, I still can't get the desktop to register on the domain.  Here is what I've tried:

I tried to change the computer name and get the message that Windows cannot find the network path...
I tried using the Network Identification Wizard and I get a pop-up that says, "An account for this computer has been found in the domain "TrueBlue".  Would you like to use this?"  When I click on yes, I get the error message that says Windows cannot find the network path...


Here is what I don't understand:

If I have some settings wrong on the server, why did it let my laptop join the domain?
What specific setting in the DNS do you think might be wrong?  I wish I could send page views so you could look at them...  FYI - no errors show up in the DNS Events log.
There are currently no "Forwarders" listed, do I need to list some up my ISP's servers?
There are currently no "Reverse Lookup Zones", do I need to create these?  If so, how?


Thanks for your help!

Chris


0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 12150392
Thank you for the explanation on the reason to close the question. It helps if you do post the reasons as our (experts) nature is to help and when we have failed (by someone wanting a question closed rather than accepting an answer) we like to know why.

Anyway...

You shouldn't need a reverse lookup zone to resolve this particular problem, but I usually create one on networks that I build - it keeps the DNS config nice and tidy.

In this particular case this is what I would do.
1. If the machine is currently part of a domain, or appears to be, then drop it in to a workgroup. Reboot.
2. When the machine comes back, change its name. Reboot.
3. On the domain flush out entries for the old machine name. Disable the machine account then disable.
Do the same in DNS and WINS.
4. On the workstation, verify that the DNS is pointing to the domain controller. If you are using WINS as well then this needs to be checked as well.
5. Attempt to join the domain.
Don't use the wizard, just right click on "My Computer" and choose Properties. Then click on "Computer Name". Click the button "Change". Adjust the option to be a member of the domain and type the domain name. Press enter and you should be prompted for credentials. Enter a domain admins credentials - username and password. You don't need to enter the domain name anywhere.
Apply/OK out and reboot when prompted.

Simon.
0
 

Author Comment

by:tcjcspen
ID: 12154384
Simon,

Thank you for your help and patience!  I finally got the message "Welcome to the 'TrueBlue' Domain" on my desktop.  Let me ask a few final questions and then I will close this question out and award the points to you.

1.  Once part of a domain, should the other computers on the domain show up in "My Network Places" or do they just show up under "My Computer" once the networked drives have been mapped?

2.  Is there a way to link the desktop login and the network login?  What I'm trying to do is view the files from my desktop login while I'm logged into the domain.

Chris
0
 
LVL 104

Expert Comment

by:Sembee
ID: 12154692
The other machines will only show up in "Entire Network". If you want them to show anywhere else then you must add them, either as a new network place or a mapped network drive.

If you have been logging in to the machine locally then you need to move the files to your domain login. Windows XP has this habit of not showing the domain information when you reach the CTRL-ALT-DEL prompt. You need to click on the Advanced button (IIRC) and then change the domain setting from the local machine to the domain.

Simon.
0
 

Author Comment

by:tcjcspen
ID: 12155193
Thank you!

Chris
0

Featured Post

Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

Join & Write a Comment

Suggested Solutions

Nslookup is a command line driven utility supplied as part of most Windows operating systems that can reveal information related to domain names and the Internet Protocol (IP) addresses associated with them. In simple terms, it is a tool that can …
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
This video demonstrates how to create an example email signature rule for a department in a company using CodeTwo Exchange Rules. The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items…

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now