A Cisco VPN server does not provide differential services if you connect to the VPN server through a VPN connection that is based on the IKEv2 protocol from a computer that is running Windows 7 or Windows Server 2008 R2

Consider the following scenario:

• You have a computer that is running Windows 7 or Windows Server 2008 R2.
• Users connect the computer to a Cisco VPN server through a virtual private network (VPN) connection that is based on the Internet Key Exchange version 2 (IKEv2) protocol.
• You configure the Cisco VPN server to forward authentication requests to a specified Remote Authentication Dial-in User Service (RADIUS) server.
  
  Note The RADIUS server is usually known as the Authentication Authorization Accounting server.

In this scenario, the VPN server cannot provide differential services according to the identity of the connected user. For example, some differential services include Virtual Routing and Forwarding (VRF), applications of QoS policy, and specific Firewall rules.

This issue occurs because the VPN client only sends the client IP address in the Identification payload field of the IKEv2 message. However, the Cisco VPN server expects the Identification payload field also to contain user name and domain name information. This behavior prevents the Cisco VPN server from forwarding an authentication request to the corresponding RADIUS server. Therefore, unexpectedly, the VPN server cannot group connected users.

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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global 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 7 and 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 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 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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 7

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

For all supported IA-64-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 VPN tunneling protocols, visit the following Microsoft Web site: For more information about the identification payloads of IKEv2, refer to the section 3.5 in the following Web site: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

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

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

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.