Authentication failure or connection to the wrong network when you use Group Policy to deploy 802.1X authentication settings to a client computer that is running Windows Vista or Windows Server 2008

Symptoms

In a network environment, you try to use Group Policy to deploy 802.1X authentication settings to a client computer that is running Windows Vista or Windows Server 2008. In this situation, the client computer incorrectly uses the built-in local default 802.1X profile before the Group Policy profile is applied.

This behavior causes the operating system to start authentication based on the built-in local authentication settings. Therefore, the computer connects to the wrong network or fails authentication instead of successfully connecting to the corporate network.

Note Disconnecting and then reconnecting the network connection, restarting the Wired AutoConfig (dot3svc) service, or restarting the computer will typically enable the authentication to complete successfully.

Cause

This issue occurs because Windows loads the default local profile before the Group Policy object (GPO)-managed profile under certain circumstances. Therefore, the default 802.1X settings are used instead of the settings in the GPO when you try to establish an 802.1X-authenticated connection to the corporate network.

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

http://support.microsoft.com/contactus/?ws=supportNote 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, you must be running Windows Vista Service Pack 2 (SP2) or Windows Server 2008 Service Pack 2 (SP2).For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

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:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

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 Vista and Windows Server 2008 file information notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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.

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    2.
    22xxx

    Windows Vista and 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 and for Windows Vista" section. MUM files 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 Server 2008 and of Windows Vista

File name

File version

File size

Date

Time

Platform

Dot3gpclnt.dll

6.0.6002.22682

43,008

19-Jul-2011

15:07

x86

Dot3.mof

Not applicable

6,072

15-Mar-2011

05:20

Not applicable

Dot3.tmf

Not applicable

443,628

19-Jul-2011

13:29

Not applicable

Dot3api.dll

6.0.6002.22682

45,056

19-Jul-2011

15:07

x86

Dot3dlg.dll

6.0.6002.22682

45,568

19-Jul-2011

15:07

x86

Dot3msm.dll

6.0.6002.22682

75,264

19-Jul-2011

15:07

x86

Dot3svc.dll

6.0.6002.22682

176,128

19-Jul-2011

15:07

x86

Dot3ui.dll

6.0.6002.22682

142,848

19-Jul-2011

15:07

x86

Gatherwiredinfo.vbs

Not applicable

12,198

15-Mar-2011

05:20

Not applicable

Gatherwiredinfo.xslt

Not applicable

743

15-Mar-2011

05:20

Not applicable

Lan diagnostics.xml

Not applicable

48,186

15-Mar-2011

05:20

Not applicable

Report.system.netdiagframework.xml

Not applicable

29,356

15-Mar-2011

05:20

Not applicable

Report.system.wired.xml

Not applicable

19,290

15-Mar-2011

05:20

Not applicable

Rules.system.netdiagframework.xml

Not applicable

57,286

15-Mar-2011

05:20

Not applicable

Rules.system.wired.xml

Not applicable

43,808

15-Mar-2011

05:20

Not applicable

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

File name

File version

File size

Date

Time

Platform

Dot3gpclnt.dll

6.0.6002.22682

51,200

19-Jul-2011

15:34

x64

Dot3.mof

Not applicable

6,072

15-Mar-2011

04:36

Not applicable

Dot3.tmf

Not applicable

472,554

19-Jul-2011

13:58

Not applicable

Dot3api.dll

6.0.6002.22682

59,904

19-Jul-2011

15:34

x64

Dot3dlg.dll

6.0.6002.22682

55,296

19-Jul-2011

15:34

x64

Dot3msm.dll

6.0.6002.22682

92,160

19-Jul-2011

15:34

x64

Dot3svc.dll

6.0.6002.22682

208,896

19-Jul-2011

15:34

x64

Dot3ui.dll

6.0.6002.22682

154,624

19-Jul-2011

15:34

x64

Gatherwiredinfo.vbs

Not applicable

12,198

15-Mar-2011

04:36

Not applicable

Gatherwiredinfo.xslt

Not applicable

743

15-Mar-2011

04:36

Not applicable

Lan diagnostics.xml

Not applicable

48,186

15-Mar-2011

04:36

Not applicable

Report.system.netdiagframework.xml

Not applicable

29,356

15-Mar-2011

04:36

Not applicable

Report.system.wired.xml

Not applicable

19,290

15-Mar-2011

04:36

Not applicable

Rules.system.netdiagframework.xml

Not applicable

57,286

15-Mar-2011

04:36

Not applicable

Rules.system.wired.xml

Not applicable

43,808

15-Mar-2011

04:36

Not applicable

Dot3.mof

Not applicable

6,072

15-Mar-2011

05:20

Not applicable

Dot3api.dll

6.0.6002.22682

45,056

19-Jul-2011

15:07

x86

Dot3dlg.dll

6.0.6002.22682

45,568

19-Jul-2011

15:07

x86

Dot3msm.dll

6.0.6002.22682

75,264

19-Jul-2011

15:07

x86

Dot3ui.dll

6.0.6002.22682

142,848

19-Jul-2011

15:07

x86

Dot3gpclnt.dll

6.0.6002.22682

43,008

19-Jul-2011

15:07

x86

2

Status

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

More Information

For more information about software update terminology, 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 file information

Additional file information for Windows Vista and for Windows Server 2008

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

File property

Value

File name

Update.mum

File version

Not applicable

File size

2,417

Date (UTC)

22-Jul-2011

Time (UTC)

19:17

Platform

Not applicable

File name

X86_05446c2aafb5dfaeb0f137727f176446_31bf3856ad364e35_6.0.6002.22682_none_58a3136cab949b9d.manifest

File version

Not applicable

File size

700

Date (UTC)

22-Jul-2011

Time (UTC)

19:17

Platform

Not applicable

File name

X86_8097169acd7f7e3aafaed5dda124a190_31bf3856ad364e35_6.0.6002.22682_none_152358270ee5a1a7.manifest

File version

Not applicable

File size

695

Date (UTC)

22-Jul-2011

Time (UTC)

19:17

Platform

Not applicable

File name

X86_microsoft-windows-dot3gpclient_31bf3856ad364e35_6.0.6002.22682_none_7c6f8664d2fa869e.manifest

File version

Not applicable

File size

13,481

Date (UTC)

19-Jul-2011

Time (UTC)

15:33

Platform

Not applicable

File name

X86_microsoft-windows-dot3svc_31bf3856ad364e35_6.0.6002.22682_none_6d87addf8a073c56.manifest

File version

Not applicable

File size

60,849

Date (UTC)

19-Jul-2011

Time (UTC)

15:35

Platform

Not applicable

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

File property

Value

File name

Amd64_8fc8feb90d4ab71ee2a8e7ef400aab2e_31bf3856ad364e35_6.0.6002.22682_none_9af6a4473b350126.manifest

File version

Not applicable

File size

1,048

Date (UTC)

22-Jul-2011

Time (UTC)

19:17

Platform

Not applicable

File name

Amd64_98cdcda0a39f751df6415d70e104b420_31bf3856ad364e35_6.0.6002.22682_none_2705662aaa62e182.manifest

File version

Not applicable

File size

1,040

Date (UTC)

22-Jul-2011

Time (UTC)

19:17

Platform

Not applicable

File name

Amd64_microsoft-windows-dot3gpclient_31bf3856ad364e35_6.0.6002.22682_none_d88e21e88b57f7d4.manifest

File version

Not applicable

File size

13,509

Date (UTC)

19-Jul-2011

Time (UTC)

16:03

Platform

Not applicable

File name

Amd64_microsoft-windows-dot3svc_31bf3856ad364e35_6.0.6002.22682_none_c9a649634264ad8c.manifest

File version

Not applicable

File size

60,909

Date (UTC)

19-Jul-2011

Time (UTC)

16:04

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,435

Date (UTC)

22-Jul-2011

Time (UTC)

19:17

Platform

Not applicable

File name

Wow64_microsoft-windows-dot3svc_31bf3856ad364e35_6.0.6002.22682_none_d3faf3b576c56f87.manifest

File version

Not applicable

File size

47,457

Date (UTC)

19-Jul-2011

Time (UTC)

15:16

Platform

Not applicable

File name

X86_microsoft-windows-dot3gpclient_31bf3856ad364e35_6.0.6002.22682_none_7c6f8664d2fa869e.manifest

File version

Not applicable

File size

13,481

Date (UTC)

19-Jul-2011

Time (UTC)

15:33

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×