A Windows XP-based client computer can establish a security association to a peer computer even though the client computer does not have a System Health Authentication OID
This article has been archived. It is offered "as is" and will no longer be updated.
You are using a Windows XP Service Pack 3-based computer that has the Network Access Protection Agent service running. You set the following registry subkey so that only the certificates that include a System Health Authentication (184.108.40.206.4.1.3220.127.116.11) Object Identifier (OID) can be used by a peer computer to establish a security association.
After you do this, a Windows XP-based computer that does not have a certificate that includes a System Health Authentication (18.104.22.168.4.1.322.214.171.124) OID can still establish a security association. Therefore, this "unhealthy" client can still connect to a peer computer.
Hotfix informationA 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 this specific problem.
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, submit a request to 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.
PrerequisitesTo apply this hotfix, you must have Windows XP Service Pack 3 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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 XP with Service Pack 3, x86-based versions
|File name||File version||File size||Date||Time||Platform|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, visit the following Microsoft Web sites:
257225 IPsec troubleshooting in Microsoft Windows 2000 Server
Article ID: 958877 - Last Review: 01/16/2015 10:58:05 - Revision: 2.0
Microsoft Windows XP Professional, Microsoft Windows XP Home Edition
- kbnosurvey kbarchive kbautohotfix kbexpertiseinter kbsurveynew kbqfe KB958877