Knowledge Base

Group Policies Are Not Applied When a User Appends a Period to Their UPN Credentials During Logon

Article ID: 821102

Article Last Modified on 10/26/2006

APPLIES TO

Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Service Pack 3
Microsoft Windows 2000 Service Pack 3

SYMPTOMS

When a user logs on to the domain, domain group policies or organizational-unit-level group policies are not applied to that user. When you view the Userenv.log, you notice information similar to the following:

USERENV(f0.d4) 16:40:44:166 MyGetUserName:  GetUserNameEx failed with 1908.
   USERENV(f0.d4) 16:40:44:206 MyGetUserName:  Retrying call to GetUserNameEx in 1/2 second.

CAUSE

This problem occurs when both of the following conditions exist:

The user logs on to the domain, specifies an alternative UPN suffix, and types their credentials in the user principal name (UPN) format (for example, someone@example.com).

-and-
The user appends a period (dot) to their credentials. For example, instead of typing

someone@example.com

the user types the following:

someone@example.com.

If the user appends a period to the UPN name that specifies the alternative UPN suffix, the domain controller for that user cannot be located. Error code 1908 in the Userenv.log file corresponds to the following:

ERROR_DOMAIN_CONTROLLER_NOT_FOUND

RESOLUTION

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must be running Windows 2000 Service Pack 3 (SP3) to install this hotfix. For additional information about how to obtain the latest Windows 2000 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   11-Jun-2003  19:18  5.0.2195.6748     124,688  Adsldp.dll       
   11-Jun-2003  19:18  5.0.2195.6748     132,368  Adsldpc.dll      
   11-Jun-2003  19:18  5.0.2195.6748      63,760  Adsmsext.dll     
   11-Jun-2003  19:18  5.0.2195.6743     381,200  Advapi32.dll     
   06-Jun-2003  19:53  5.0.2195.6753      69,392  Browser.dll      
   11-Jun-2003  19:18  5.0.2195.6680     134,928  Dnsapi.dll       
   11-Jun-2003  19:18  5.0.2195.6663      92,432  Dnsrslvr.dll     
   11-Jun-2003  19:18  5.0.2195.6753      47,376  Eventlog.dll     
   11-Jun-2003  19:18  5.0.2195.6747     148,240  Kdcsvc.dll       
   20-May-2003  18:49  5.0.2195.6747     205,072  Kerberos.dll     
   26-Mar-2003  21:37  5.0.2195.6695      71,888  Ksecdd.sys
   28-May-2003  20:39  5.0.2195.6749     509,712  Lsasrv.dll       
   28-May-2003  20:39  5.0.2195.6749      33,552  Lsass.exe        
   05-Apr-2003  00:12  5.0.2195.6680     117,520  Msv1_0.dll       
   11-Jun-2003  19:18  5.0.2195.6601     311,568  Netapi32.dll     
   11-Jun-2003  19:18  5.0.2195.6695     371,984  Netlogon.dll     
   11-Jun-2003  19:18  5.0.2195.6697   1,040,144  Ntdsa.dll        
   11-Jun-2003  19:18  5.0.2195.6742     392,464  Samsrv.dll       
   11-Jun-2003  19:18  5.0.2195.6737     131,344  Scecli.dll       
   11-Jun-2003  19:18  5.0.2195.6737     306,448  Scesrv.dll       
   29-May-2003  23:22  5.0.2195.6748   4,576,256  Sp3res.dll       
   11-Jun-2003  19:18  5.0.2195.6601      51,472  W32time.dll      
   16-Aug-2002  13:32  5.0.2195.6601      57,104  W32tm.exe        
   11-Jun-2003  19:18  5.0.2195.6741     126,224  Wldap32.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New Naming Schema for Microsoft Windows Hotfix Packages

Keywords: kbbug kbfix kbqfe kbwin2000presp5fix kbhotfixserver KB821102

Microsoft KB Archive/821102

Contents