How to Use Netsh to Monitor Domain Records (300603)


The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
This article was previously published under Q300603

SUMMARY

This article describes how to use the Netsh command-line utility to automate the monitoring of domain name records.

MORE INFORMATION

Netsh can monitor domain records in either of two ways. One way is documented in the following Microsoft Knowledge Base article:

300598 How to Verify the Domain Records in Windows 2000 Windows Internet Name Service

This is the command-line version of the Verify Names feature of the WINS Management snap-in. It verifies that names exist and on which servers they exist.

The Domainname 1ch record contains up to 25 IP addresses of domain controllers. It may be useful to know which 25 records exist on each WINS server, especially if more than 25 domain controllers exist in a domain; the WINS servers may have only subsets of the total number of domain controllers.

This is a sample Netsh command:

netsh wins server 10.10.10.3 show name domainnamerecord type >>Dc.txt
netsh wins server 10.20.10.4 show name domainnamerecord type >>Dc.txt

This is sample output from the Dc.txt file: 

***You have Read and Write access to the server wins1.domainname.com*

Name                  : <DOMAINNAME>         [1Ch] 
NodeType              : dd
State                 : ACTIVE    
Expiration Date       : Infinite                
Type of Rec           : INTERNET GROUP
Version No            : 0 20d 
RecordType            : STATIC 
Owner                 : 10.10.10.3
Member                : 10.10.10.1
Owner                 : 10.10.10.5
Member                : 20.20.20.20
Command completed successfully.

***You have Read and Write access to the server wins2.<domainname>.com***

Wins Server Show Name failed with Error : 
The name does not exist in the WINS database.

The first WINS server successfully returned the record with two domain controllers in the list (10.10.10.1 and 20.20.20.20). The domain controller with the address 10.10.10.1 was originally registered with the WINS server at 10.10.10.3. The domain controller with address 20.20.20.20 originally registered with the WINS server at 10.10.10.5. The record was statically entered in WINS (this may be a cause for concern). When querying the second WINS server at 10.20.10.4, it found the 1ch entry missing. This would be cause for further investigation.
Modification Type:MinorLast Reviewed:11/29/2004
Keywords:kbhowto kbnetwork KB300603
©2004 Microsoft Corporation. All rights reserved.