Solved

Problems using NETDIAG & DCDIAG

Posted on 2006-06-26
3
3,846 Views
Last Modified: 2008-01-09
NETDIAG /Fix - why do i get [FATAL] Failed to get the system information of this machine

How can I correct it

Also failing tests with dcdiag:  here are the results:

C:\WINNT>dcdiag /fix

DC Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial non skippeable tests

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

Doing primary tests

   Testing server: Default-First-Site-Name\PISERVER
      Starting test: Replications
         ......................... PISERVER passed test Replications
      Starting test: NCSecDesc
         ......................... PISERVER passed test NCSecDesc
      Starting test: NetLogons
         [PISERVER] An net use or LsaPolicy operation failed with error 67, The
network name cannot be found..
         ......................... PISERVER failed test NetLogons
      Starting test: Advertising
         ......................... PISERVER passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... PISERVER passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... PISERVER passed test RidManager
      Starting test: MachineAccount
         Could not open pipe with [PISERVER]:failed with 67: The network name ca
nnot be found.
         Could not get NetBIOSDomainName
         Failed can not test for HOST SPN
         Failed can not test for HOST SPN
         * Missing SPN :(null)
         * Missing SPN :(null)
         ......................... PISERVER failed test MachineAccount
      Starting test: Services
         Could not open Remote ipc to [PISERVER]:failed with 67: The network nam
e cannot be found.
         ......................... PISERVER failed test Services
      Starting test: ObjectsReplicated
         ......................... PISERVER passed test ObjectsReplicated
      Starting test: frssysvol
         [PISERVER] An net use or LsaPolicy operation failed with error 67, The
network name cannot be found..
         ......................... PISERVER failed test frssysvol
      Starting test: kccevent
         Failed to enumerate event log records, error The network name cannot be
 found.
         ......................... PISERVER failed test kccevent
      Starting test: systemlog
         Failed to enumerate event log records, error The network name cannot be
 found.
         ......................... PISERVER failed test systemlog

   Running enterprise tests on : PATRONS.LOCAL
      Starting test: Intersite
         ......................... PATRONS.LOCAL passed test Intersite
      Starting test: FsmoCheck
         ......................... PATRONS.LOCAL passed test FsmoCheck
0
Comment
Question by:Marshalk
  • 2
3 Comments
 
LVL 1

Accepted Solution

by:
Zabulon777 earned 500 total points
Comment Utility
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/netdiag-o.asp.

Examples

1. To test  the domain controller in your domain, type the following line, and then press ENTER: netdiag /v /l /test:dsgetdc

2. To display the IPSec policy, type the following line, and then press ENTER: netdiag /test:ipsec /debug

"[Fatal] Failed to Get System Information" Error Message Occurs When You Run Netdiag
 "The procedure entry point DnsGetMaxNumberOfAddressToRegister could not belocated in the dynamiclink library DNSAPI.dll." error when running netdiag on XP
What does netdiag /fix do

"[Fatal] Failed to Get System Information" Error Message Occurs When You Run Netdiag
Symptom: When you run the Netdiag tool, you receive the following error message: [Fatal] Failed to get system information of this machine.
Resolution: To resolve this issue, start the Computer Management console, click Services, and then start the Remote Registry service.

 "The procedure entry point DnsGetMaxNumberOfAddressToRegister could not belocated in the dynamiclink library DNSAPI.dll." error when running netdiag on XP

Make sure you are running the version form XP CD. There is a possibility that you have a W2K version of netdiag installed explicitly - there was a download from KB. Or you may just upgrade the OS from w2k to XP. To fix this problem, you may want to re-install it. To re-install,  run XP CD at \Support\Tools\SUPTOOLS.MSI and select "Remove all". After it is done, launch it again to install appropriate version of support tools.

What does netdiag /fix do

Netdiag /fix  switch is very useful tool to correct issues with DNS and domain controller tests. 1. DNS Test: If the computer is a domain controller, Netdiag verifies all the DNS entries in the Netlogon.dns file to determine if they are correct and updates the appropriate entries if there is a problem. 2. Domain Controller Test: If the domain GUID cached in a local computer on your primary domain is different than the domain GUID saved in a domain controller, Netdiag tries to update the domain GUID on the local computer.
0
 

Author Comment

by:Marshalk
Comment Utility
Thank you for the quick response.  I researched google nad found out about the Remote Registry services and tried it.  it worked and i was able to run the netdiag command.  I then read your comment which directed me to do the same.  The one difference is i tried to run the step 1. of your response and got the fatal error again.  I restarted the Remote Registry Service (RRS) and it worked.  Why is the RRS stopping or failing is the new question?
0
 
LVL 1

Expert Comment

by:Zabulon777
Comment Utility
I am not sure why its doing that... yo ucan read up more about RRS...

http://www.theeldergeek.com/remote_registry.htm
0

Featured Post

Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

Suggested Solutions

BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (https://kb.isc.org/article/AA-01272), affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
Let’s list some of the technologies that enable smooth teleworking. 
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

771 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

12 Experts available now in Live!

Get 1:1 Help Now