NETDOM 1.7 Reports Access Denied with Windows NT 4.0 SP4 (197160)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 SP4
This article was previously published under Q197160 SYMPTOMS
When you use NETDOM version 1.7 (which is included in the Windows NT 4.0
Resource Kit Supplement 3) on a computer with Windows NT 4.0 Service Pack
4, you receive the following error message:
Access Denied
RESOLUTION
NETDOM 1.8 corrects this problem and is available on the
following Microsoft FTP site:
For Intel processors:
ftp://ftp.microsoft.com/reskit/nt4/x86/
For Alpha-based processors:
ftp://ftp.microsoft.com/reskit/nt4/alpha/
The new version of NETDOM has been modified so that it works with all
computers running Windows NT 4.0 Service Pack 4. NETDOM 1.8 also provides
the following new feature set:
- Option to trigger partial synchronization from a backup domain
controller (BDC) to a primary domain controller (PDC):
NETDOM BDC \\BDCNAME /PARTIALSYNC - Option to trigger full synchronization from a BDC to a PDC
NETDOM BDC \\BDCNAME /FULLSYNC
Secure channels are no longer checked by comparing passwords on both sides
of the secure channel. The new release of NETDOM relies on the NETLOGON
service to query secure channels status (as NLTEST utility). If a secure
channel is incorrect, NETDOM can reset it automatically. For more
information, please see the following articles in the Microsoft Knowledge
Base:
150493
How to Join a Domain From the Command Line
175024
Resetting Domain Member Secure Channel
150518
NetLogon Service Fails when Secure Channel Not Functioning
175025
How to Build and Reset a Trust Relationship from a Command Line
Some changes have been made on Windows NT 4.0 Service Pack 4 so that
computer account password changes are no longer replicated urgently (flag
ANNOUNCE_IMMEDIATE). NETDOM 1.8 displays new warning messages stating that
a possible cause of an incorrect member's secure channel is synchronization
between the BDC, with which the member has established a secure channel,
and the PDC.
STATUS
Microsoft has confirmed this to be a problem in NETDOM version 1.7.
Modification Type: | Major | Last Reviewed: | 8/10/2001 |
---|
Keywords: | kbprb KB197160 |
---|
|