Problem Attempting Remote Administration with Local Users and Groups Snap-in (241808)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Datacenter Server
This article was previously published under Q241808 SYMPTOMS
When you attempt to perform remote administration of a user account database using the Local Users and Groups snap-in, you may receive the following error message:
Access denied
CAUSE
This behavior can occur if the connection to the remote computer was initiated using an Internet Protocol (IP) address rather than a NetBIOS name.
RESOLUTION
Initiate the connection to the remote computer using an authenticated NetBIOS name connection, rather than with an IP address.
Another workaround is to create an ipc$ connection using net use \\<ip address>\ipc$ /u <domain\user>.
This will now allow remote administration of a user account database.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
The Local Users and Groups snap-in maintains an internal and external computer name. The internal name is the target computer's NetBIOS name, and the external name is whatever name is supplied to the snap-in. The Local Users and Groups snap-in always uses the internal (NetBIOS) name to perform operations. If you are authenticated on the target computer with a non-NetBIOS name, these operations may not succeed.
NOTE: The Local Users and Groups snap-in applies to Member servers and Workgroups servers only. Domain controllers use the Active Directory Users and Computers tool instead.
| Modification Type: | Major | Last Reviewed: | 11/21/2003 |
|---|
| Keywords: | kbenv kberrmsg kbprb KB241808 |
|---|
|