Microsoft KB Archive/241808

= Problem Attempting Remote Administration with Local Users and Groups Snap-in =

Article ID: 241808

Article Last Modified on 3/1/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * 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 \\ \ipc$ /u .

This will now allow remote administration of a user account database.



STATUS
Microsoft 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.

Additional query words: mmc

Keywords: kbenv kberrmsg kbprb KB241808

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.