An NPS server that is running Windows Server 2008 SP2 or Windows Server 2008 R2 does not send an Access-Reject packet to an NPS client

Consider the following scenario:

• You install the Network Policy and Access Services server role on a server that is running Windows Server 2008 Service Pack 2 (SP2) or Windows Server 2008 R2. The Network Policy Server (NPS) role service automatically becomes available on the server.
• You configure the Ping User-Name registry entry on the server.
• A client sends a RADIUS Access-Request packet to the server. The RADIUS Access-Request packet contains the specified user name that matches the value in Ping User-Name registry entry on the server.

In this scenario, the server does not send an Access-Reject packet to the client. Therefore, the client detects that the server is unavailable. However, the server is available.

Note The expected behavior is that the server sends the Access-Reject packet to the client.

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, visit the following Microsoft Web site: 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

To apply this hotfix, your computer must be running Windows Server 2008 Service Pack 2(SP2) or Windows Server 2008 R2. Additionally, the computer must have the "Network Policy and Access Services" server role installed.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 file information notes

• 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.
  Collapse this tableExpand this table

  6.0.600 2 . 22xxx

  Windows Server 2008

  SP2

  LDR

• 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" section. MUM files 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 x86-based versions of Windows Server 2008 SP2

For all supported x64-based versions of Windows Server 2008 SP2

For all supported IA-64-based versions of Windows Server 2008 SP2

Windows Server 2008 R2 file information notes

• 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

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: For more information about Ping User-Name registry entry, visit the following TechNet Web site:

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008 SP2

Additional files for all supported x64-based versions of Windows Server 2008 SP2

Additional files for all supported IA-64-based versions of Windows Server 2008 SP2

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2