Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The NPS server locks a user account after four tries on a Windows Server 2008 R2-based computer that performs authentication for RADIUS clients

The NPS server locks a user account after four tries on a Windows Server 2008 R2-based computer that performs authentication for RADIUS clients

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You configure a Windows Server 2008 R2-based computer that is running Network Policy Server (NPS) as the Remote Authentication Dial-In User Service (RADIUS) server to perform authentication for RADIUS clients.
  • You enable remote access account lockout and set the MaxDenials entry to 3.
  • You set the Active Directory account lockout policy for wrong passwords to 4. 
  • The password of a user expires, and the user changes the password on their desktop computer. 
  • Devices such as mobile phones or tablets try to authenticate with the server repeatedly by using the old password quickly.
  • There are small communication latencies between the computer that is running NPS and the Active Directory domain controller.

In this scenario, the user might be locked out from the Active Directory domain controller before he or she is locked out on the NPS server. However, expected behavior is that the NPS server locks the user for a specific time after the number of tries that are set in the MaxDenials entry to prevent the user account lockout. 

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Windows Server 2008 R2 Service Pack 1 installed to apply this hotfix.

Restart information

You must restart the computer after you apply this hotfix.

Replacement information

This hotfix does not replace any previously released hotfix.

File information
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductMilestoneService branch
    6.1.7601.22xxxWindows Server 2008 R2SP1LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Iassam.dll6.1.7601.22320253,44009-May-201316:47x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Iassam.dll6.1.7601.22320523,26409-May-201314:06IA-64

↑ Back to the top

Workaround

To work around this issue, make sure that the communication between the NPS server and the domain controller is a fast as possible. Also, set the Active Directory account lockout policy to a higher value.

Note If you have several NPS servers, you should set the Active Directory password policy to (number of NPS servers) * (MaxDenials) + n. The placeholder n could be any number higher than the number of NPS servers.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_0187f924d4500eea203b969c7aa63e3e_31bf3856ad364e35_6.1.7601.22320_none_a090d2a47d85a6c9.manifest
File versionNot applicable
File size1,122
Date (UTC)09-May-2013
Time (UTC)22:14
PlatformNot applicable
File nameAmd64_microsoft-windows-n..tion_service_iassam_31bf3856ad364e35_6.1.7601.22320_none_da50183e83834652.manifest
File versionNot applicable
File size2,313
Date (UTC)09-May-2013
Time (UTC)17:24
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_9ac45ad5993864168b7d63073cd07642_31bf3856ad364e35_6.1.7601.22320_none_93fd5503f1895ae5.manifest
File versionNot applicable
File size1,120
Date (UTC)09-May-2013
Time (UTC)22:14
PlatformNot applicable
File nameIa64_microsoft-windows-n..tion_service_iassam_31bf3856ad364e35_6.1.7601.22320_none_7e3320b0cb23de18.manifest
File versionNot applicable
File size2,312
Date (UTC)09-May-2013
Time (UTC)15:28
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2824560
Revision : 1
Created on : 1/7/2017
Published on : 6/18/2013
Exists online : False
Views : 157