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.

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?

Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail. The methods are covered in more detail in o…

NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…