User Names That Begin with "!" May Not Work with a Domain Controller (303145)



The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2

This article was previously published under Q303145

SYMPTOMS

User names that begin with an exclamation point (!) and are presented in their User Principle Name (UPN) format (for example, such as !test@Domain.com) may not work when they are used to connect to a domain controller. A typical situation is to log on to a computer (which is in the Domain.com) domain by using a local account, and then try to add a domain user to a local group or set permissions on a file. Depend on the settings on the domain controller, the following prompt may appear:
You are logged on with an account that does not have access to:

Domain.com

Enter the name and password of an account with permissions for this domain and click OK.
If you then enter the user name and password, such as !test@Domain.com, you receive the following response:
The following error occurred while using the user name and password entered:

An invalid Active Directory pathname was passed.
If you use the traditional SAM account name format for the user name, such as Domain\!test, no error message occurs and you can browse the user list.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:
   Date         Time   Version          Size     File name
   ------------------------------------------------------
  7/27/2001    12:59a   5.0.2195.3951   502,032  Lsasrv.dll(56-bit)
  7/30/2001    02:52a   5.0.2195.3973   130,320  Adsldpc.dll
  7/30/2001    02:52a   5.0.2195.3858   355,088  Advapi32.dll
  7/30/2001    02:47a   5.0.2195.3951   519,440  Instlsa5.dll
  7/30/2001    02:52a   5.0.2195.3951   143,120  Kdcsvc.dll
  7/27/2001    12:56a   5.0.2195.3951   197,392  Kerberos.dll
  6/26/2001    08:16p   5.0.2195.3781    69,456  Ksecdd.sys
  7/27/2001    12:59a   5.0.2195.3951   501,520  Lsasrv.dll
  7/27/2001    12:59a   5.0.2195.3951    33,552  Lsass.exe
  6/27/2001    04:08p   5.0.2195.3789   112,128  Msv1_0.dll
  7/30/2001    02:52a   5.0.2195.3868   909,072  Ntdsa.dll
  7/30/2001    02:52a   5.0.2195.3925   382,224  Samsrv.dll
  7/30/2001    02:52a   5.0.2195.3781   128,784  Scecli.dll
  7/30/2001    02:52a   5.0.2195.3649   299,792  Scesrv.dll
  7/30/2001    02:52a   5.0.2195.3838   123,664  Wldap32.dll

				

WORKAROUND

To work around this issue, do not use a UPN name, use the traditional SAM account name instead.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product

For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:

296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes


Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbDirServices kbfix kbWin2000PreSP3Fix kbWin2000sp3fix KB303145