Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Logged-on user accounts do not receive a pop-up balloon to authenticate an 802.1X secured network in Windows 7 and in Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows 7 or Windows Server 2008 R2, and the computer joins a workgroup.
  • An 802.1X secured network connection is created in Network Connections.
  • You use more than one user account to log on to the 802.1X secured network from the computer.
In this scenario, only the first user account receives a pop-up balloon to enter credentials to log on to the 802.1X secured network. Successive user accounts do not receive this pop-up balloon. Additionally, the network connection to the 802.1X secured network is in an "Authentication Failed" state. Because of the issue, successive users cannot access the network resources, such as file servers, shared printer or applications.

Note Successive user accounts may sometimes receive a pop-up balloon to enter credentials to log on to the domain after a long wait, such as a wait of several minutes.

↑ Back to the top


Cause

This issue occurs because the Wired AutoConfig (DOT3SVC) service does not handle the event data correctly when a user account logs on to the computer.

↑ Back to the top


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 website: 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, you must be running one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

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.

Note You can stop the Wired AutoConfig service before you install the hotfix to avoid restarting.

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
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.20xxx
    Windows 7 and Windows Server 2008 R2RTMLDR
    6.1.760
    1.17xxx
    Windows 7 and Windows Server 2008 R2SP1GDR
    6.1.760
    1.21xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, very important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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 very important for maintaining 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 7
File nameFile versionFile sizeDateTimePlatform
Dot3.mofNot applicable6,07222-Jul-200923:04Not applicable
Dot3api.dll6.1.7600.2088291,13617-Jan-201105:30x86
Dot3dlg.dll6.1.7600.2088247,10417-Jan-201105:30x86
Dot3msm.dll6.1.7600.20882115,20017-Jan-201105:30x86
Dot3svc.dll6.1.7600.20882215,55217-Jan-201105:30x86
Report.system.netdiagframework.xmlNot applicable29,35622-Jul-200923:04Not applicable
Report.system.wired.xmlNot applicable19,29022-Jul-200923:04Not applicable
Rules.system.netdiagframework.xmlNot applicable57,28622-Jul-200923:04Not applicable
Rules.system.wired.xmlNot applicable40,90222-Jul-200923:04Not applicable
Dot3api.dll6.1.7601.1751491,13620-Nov-201012:18x86
Dot3msm.dll6.1.7601.17514115,20020-Nov-201012:18x86
Dot3svc.dll6.1.7601.21643215,55217-Jan-201105:36x86
Report.system.netdiagframework.xmlNot applicable29,35610-Jun-200921:20Not applicable
Report.system.wired.xmlNot applicable19,29010-Jun-200921:20Not applicable
Rules.system.netdiagframework.xmlNot applicable57,28610-Jun-200921:20Not applicable
Rules.system.wired.xmlNot applicable40,90210-Jun-200921:20Not applicable
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Dot3.mofNot applicable6,07222-Jul-200923:23Not applicable
Dot3api.dll6.1.7600.2088284,99217-Jan-201106:13x64
Dot3dlg.dll6.1.7600.2088257,85617-Jan-201106:13x64
Dot3msm.dll6.1.7600.20882103,93617-Jan-201106:13x64
Dot3svc.dll6.1.7600.20882254,46417-Jan-201106:13x64
Report.system.netdiagframework.xmlNot applicable29,35622-Jul-200923:23Not applicable
Report.system.wired.xmlNot applicable19,29022-Jul-200923:23Not applicable
Rules.system.netdiagframework.xmlNot applicable57,28622-Jul-200923:23Not applicable
Rules.system.wired.xmlNot applicable40,90222-Jul-200923:23Not applicable
Dot3api.dll6.1.7601.1751484,99220-Nov-201013:26x64
Dot3msm.dll6.1.7601.17514103,93620-Nov-201013:26x64
Dot3svc.dll6.1.7601.21643254,46417-Jan-201106:19x64
Report.system.netdiagframework.xmlNot applicable29,35610-Jun-200920:37Not applicable
Report.system.wired.xmlNot applicable19,29010-Jun-200920:37Not applicable
Rules.system.netdiagframework.xmlNot applicable57,28610-Jun-200920:37Not applicable
Rules.system.wired.xmlNot applicable40,90210-Jun-200920:37Not applicable
Dot3.mofNot applicable6,07222-Jul-200923:04Not applicable
Dot3api.dll6.1.7600.2088291,13617-Jan-201105:30x86
Dot3dlg.dll6.1.7600.2088247,10417-Jan-201105:30x86
Dot3msm.dll6.1.7600.20882115,20017-Jan-201105:30x86
Dot3api.dll6.1.7601.2164391,13617-Jan-201105:36x86
Dot3dlg.dll6.1.7601.2164347,10417-Jan-201105:36x86
Dot3msm.dll6.1.7601.21643115,20017-Jan-201105:36x86

↑ Back to the top


Workaround

Workaround for Windows 7 and for Windows Server 2008 R2

To work around the issue, you can disable and then enable the 802.1X secured network connection.

↑ Back to the top


Status

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

↑ Back to the top


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 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot applicable
File size2,482
Date (UTC)18-Jan-2011
Time (UTC)00:35
PlatformNot applicable
File nameX86_4533709d4ac6a9525482100563c5ffcd_31bf3856ad364e35_6.1.7600.20882_none_d4510f352e766222.manifest
File versionNot applicable
File size1,038
Date (UTC)18-Jan-2011
Time (UTC)00:35
PlatformNot applicable
File nameX86_fe17dc330b8c5da864ad2b28f93ee31c_31bf3856ad364e35_6.1.7601.21643_none_7b5cb94680c4881f.manifest
File versionNot applicable
File size695
Date (UTC)18-Jan-2011
Time (UTC)00:35
PlatformNot applicable
File nameX86_microsoft-windows-dot3svc-mof_31bf3856ad364e35_6.1.7600.20882_none_96b79a3cc70b140f.manifest
File versionNot applicable
File size1,865
Date (UTC)17-Jan-2011
Time (UTC)06:09
PlatformNot applicable
File nameX86_microsoft-windows-dot3svc_31bf3856ad364e35_6.1.7600.20882_none_6bc90870edf829cc.manifest
File versionNot applicable
File size86,521
Date (UTC)17-Jan-2011
Time (UTC)06:19
PlatformNot applicable
File nameX86_microsoft-windows-dot3svc_31bf3856ad364e35_6.1.7601.21643_none_6ddba570eafd3f4b.manifest
File versionNot applicable
File size89,640
Date (UTC)18-Jan-2011
Time (UTC)00:38
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_88dc0ffb05cb7a927d131a7697cf9896_31bf3856ad364e35_6.1.7601.21643_none_a0f2ce13315ea637.manifest
File versionNot applicable
File size699
Date (UTC)18-Jan-2011
Time (UTC)00:35
PlatformNot applicable
File nameAmd64_d3f704022d3b30a499179ab0a495bac0_31bf3856ad364e35_6.1.7601.21643_none_fa276298d146267c.manifest
File versionNot applicable
File size1,040
Date (UTC)18-Jan-2011
Time (UTC)00:35
PlatformNot applicable
File nameAmd64_da677866ef048af499f9fabf09a0e770_31bf3856ad364e35_6.1.7600.20882_none_8f7110f2227f3557.manifest
File versionNot applicable
File size1,730
Date (UTC)18-Jan-2011
Time (UTC)00:35
PlatformNot applicable
File nameAmd64_microsoft-windows-dot3svc-mof_31bf3856ad364e35_6.1.7600.20882_none_f2d635c07f688545.manifest
File versionNot applicable
File size1,867
Date (UTC)17-Jan-2011
Time (UTC)06:54
PlatformNot applicable
File nameAmd64_microsoft-windows-dot3svc_31bf3856ad364e35_6.1.7600.20882_none_c7e7a3f4a6559b02.manifest
File versionNot applicable
File size86,525
Date (UTC)17-Jan-2011
Time (UTC)07:08
PlatformNot applicable
File nameAmd64_microsoft-windows-dot3svc_31bf3856ad364e35_6.1.7601.21643_none_c9fa40f4a35ab081.manifest
File versionNot applicable
File size89,644
Date (UTC)18-Jan-2011
Time (UTC)00:35
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,500
Date (UTC)18-Jan-2011
Time (UTC)00:35
PlatformNot applicable
File nameWow64_microsoft-windows-dot3svc-mof_31bf3856ad364e35_6.1.7600.20882_none_fd2ae012b3c94740.manifest
File versionNot applicable
File size1,867
Date (UTC)17-Jan-2011
Time (UTC)06:04
PlatformNot applicable
File nameWow64_microsoft-windows-dot3svc_31bf3856ad364e35_6.1.7600.20882_none_d23c4e46dab65cfd.manifest
File versionNot applicable
File size79,649
Date (UTC)17-Jan-2011
Time (UTC)06:03
PlatformNot applicable
File nameWow64_microsoft-windows-dot3svc_31bf3856ad364e35_6.1.7601.21643_none_d44eeb46d7bb727c.manifest
File versionNot applicable
File size79,649
Date (UTC)17-Jan-2011
Time (UTC)06:05
PlatformNot applicable

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2491809
Revision : 1
Created on : 1/7/2017
Published on : 2/10/2011
Exists online : False
Views : 161