Microsoft KB Archive/936358

= Error message when you try to access shared resources after a VPN connection is established from a Windows Vista-based computer to a Windows Server 2003-based server: &quot;System error 2148074324 has occurred&quot; =

Article ID: 936358

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, 64-Bit Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard x64 Edition

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
Consider the following scenario:
 * On a Windows Vista-based client computer, you establish a virtual private network (VPN) connection.
 * The client computer is connected to a Microsoft Windows Server 2003-based server for authentication through the VPN connection.
 * The certificate that is used for authentication does not include the Extended Key Usage (EKU) information for a smart card logon.

When you try to access shared resources through the VPN connection, you may receive the following error message:

System error 2148074324 has occurred.

The smartcard certificate used for authentication was not trusted. Please contact your system administrator.

Note This issue does not occur on a Microsoft Windows XP-based client computer.



CAUSE
The issue occurs because Windows Server 2003 requires the EKU information for the smart card logon. If the certificate that is used for authentication does not include the EKU information, Windows Server 2003 denies Kerberos requests.



RESOLUTION
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer 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.

Note After you apply the hotfix on a computer that is running Windows Server 2003, certificates that do not include EKU information for smartcard logon are supported by Kerberos authentication.

Prerequisites
To apply this hotfix, you must have one of the following service packs installed:
 * Windows Server 2003 with Service Pack 1 (SP1)
 * Windows Server 2003 with Service Pack 2 (SP2)

Active Directory must also be installed on the server.

Restart requirement
After you apply this hotfix, you must restart the server.

Hotfix replacement information
This hotfix does not replace any other previously released hotfixes.

Registry information
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. To enable this hotfix, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate the following registry subkey:

 Right-click Kdc, point to New, and then click DWORD Value. Type SCLogonEKUNotRequired, and then press ENTER . On the Edit menu, click Modify. In the Value data box, type 1, and then click OK.</li> Exit Registry Editor.</li></ol>

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 2003 with Service Pack 2, x64-based versions
<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: Vista, VPN, Kerberos, SCLogonEKUNotRequired, CredMan

Keywords: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver KB936358

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.