Bug report - Vista x64 wireless LAN fails after sleep/hibernate

Vista Ultimate x64 wireless LAN fails after sleep/hibernate on Thinkpad T60


Bug report.

Tested using Vista Ultimate x64 RTM, Lenovo Thinkpad T60, Intel 3945ABG
W-NIC, Linksys WAP54G AP, 802.11g LAN with WPA2-PSK/AES without radius server
and SSID broadcast disabled, on IBM Thinkpad R51 laptop. Device drivers for
Intel Wireless NIC are as downloaded from Intel's www (v10.6.0.46), other
core system drivers are all latest Vista x64 drivers available from IBM
website to date (2007-03-15).

When putting Thinkpad into sleep or hibernate by pressing Fn+F4 or Fn+F12,
on resume the wireless networking subsytem seems to be in difficulties. There
is no IPv4 connectivity, NIC fails to acquire an IP address via DHCP after
resume, and repair fails. Disabling/re-enabling the wireless NIC restores
connectivity.

Event log shows the following warning:
===
Log Name: System
Source: Microsoft-Windows-Dhcp-Client
Date: 15/03/2007 19:36:55
Event ID: 1003
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: cecil-tpad-R60
Description:
Your computer was not able to renew its address from the network (from the
DHCP Server) for the Network Card with network address 0019D209D736. The
following error occurred:
The semaphore timeout period has expired.. Your computer will continue to
try and obtain an address on its own from the network address (DHCP) server.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Dhcp-Client"
Guid="{15A7A4F8-0072-4EAB-ABAD-F98A4D666AED}" EventSourceName="Dhcp" />
<EventID Qualifiers="0">1003</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-03-15T19:36:55.000Z" />
<EventRecordID>2430</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>cecil-tpad-R60</Computer>
<Security />
</System>
<EventData>
<Data>0019D209D736</Data>
<Data>%%121</Data>
</EventData>
</Event>
===

Diagnosis immediately following this gives the following record in the event
log
===
Log Name: System
Source: Microsoft-Windows-Diagnostics-Networking
Date: 15/03/2007 19:38:50
Event ID: 6100
Task Category: (12)
Level: Information
Keywords: (2)
User: LOCAL SERVICE
Computer: cecil-tpad-R60
Description:
Helper Class (AutoConfig Helper Class) Event:

Wireless Diagnostic Informational Event

Information for connection being diagnosed
Interface GUID: 4aaed9d7-e9d5-496c-b878-857aeb6a9ea6
Interface name: Intel(R) PRO/Wireless 3945ABG Network Connection
Interface type: Native WiFi

Connection incident diagnosed
Auto Configuration ID: 1
Connection ID: 1

Connection status summary
Connection started at: 2007-03-15 16:58:06-366
Profile match: Success
Pre-Association: Success
Association: Success
Security and Authentication: Success

List of visible access point(s): 2 item(s) total, 2 item(s) displayed
BSSID BSS Type PHY Signal(dB) Chnl/freq SSID
-------------------------------------------------------------------------
00-18-F8-31-EF-E3 Infra g -144 1
00-18-F8-31-EF-E3 Infra <unknown> -144 1

Connection History

Information for Auto Configuration ID 1

List of visible networks: 3 item(s) total, 3 item(s) displayed
BSS Type PHY Security Signal(RSSI) Compatible SSID

------------------------------------------------------------------------------
Infra g Yes 78 Yes
Infra <unknown> Yes 78 Yes
Infra b Yes 100 Yes _TG_WAP54G_R4hc14jh3P1swd

List of preferred networks: 1 item(s)
Profile: _TG_WAP54G_R4hc14jh3P1swd
SSID: _TG_WAP54G_R4hc14jh3P1swd
SSID length: 25
Connection mode: Infra
Security: Yes
Set by group policy: No
Connect even if network is not broadcasting: No
Connectable: Yes

Information for Connection ID 1
Connection started at: 2007-03-15 16:58:06-366
Auto Configuration ID: 1
Profile: _TG_WAP54G_R4hc14jh3P1swd
SSID: _TG_WAP54G_R4hc14jh3P1swd
SSID length: 25
Connection mode: Infra
Security: Yes
Pre-Association and Association
Connectivity settings provided by hardware manufacturer (IHV): No
Security settings provided by hardware manufacturer (IHV): No
Profile matches network requirements: Success
Pre-association status: Success
Association status: Success
Last AP: 00-18-f8-31-ef-e3
Security and Authentication
Configured security type: WPA-PSK
Configured encryption type: CCMP(AES)
802.1X protocol: No
Key exchange initiated: Yes
Unicast key received: Yes
Multicast key received: Yes
Number of security packets received: 21
Number of security packets sent: 21
Security attempt status: Success
Connectivity
Packet statistics
Ndis Rx: 92560
Ndis Tx: 57566
Unicast decrypt success: 0
Multicast decrypt success: 0
Unicast decrypt failure: 0
Multicast decrypt failure: 0
Rx success: 237
Rx failure: 0
Tx success: 0
Tx failure: 0
Roaming history: 0 item(s)



Event Verbosity:0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Networking"
Guid="{36c23e18-0e66-11d9-bbeb-505054503030}" />
<EventID>6100</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>12</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000002</Keywords>
<TimeCreated SystemTime="2007-03-15T19:38:50.673Z" />
<EventRecordID>2433</EventRecordID>
<Correlation ActivityID="{7DE2ACE7-AC92-42DB-8A3C-EC4632CF3882}" />
<Execution ProcessID="2388" ThreadID="3524" />
<Channel>System</Channel>
<Computer>cecil-tpad-R60</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="HelperClassName">AutoConfig Helper Class</Data>
<Data Name="EventDescription">Wireless Diagnostic Informational Event

Information for connection being diagnosed
Interface GUID: 4aaed9d7-e9d5-496c-b878-857aeb6a9ea6
Interface name: Intel(R) PRO/Wireless 3945ABG Network Connection
Interface type: Native WiFi

Connection incident diagnosed
Auto Configuration ID: 1
Connection ID: 1

Connection status summary
Connection started at: 2007-03-15 16:58:06-366
Profile match: Success
Pre-Association: Success
Association: Success
Security and Authentication: Success

List of visible access point(s): 2 item(s) total, 2 item(s) displayed
BSSID BSS Type PHY Signal(dB) Chnl/freq SSID
-------------------------------------------------------------------------
00-18-F8-31-EF-E3 Infra g -144 1
00-18-F8-31-EF-E3 Infra <unknown> -144 1

Connection History

Information for Auto Configuration ID 1

List of visible networks: 3 item(s) total, 3 item(s) displayed
BSS Type PHY Security Signal(RSSI) Compatible SSID

------------------------------------------------------------------------------
Infra g Yes 78 Yes
Infra <unknown> Yes 78 Yes
Infra b Yes 100 Yes _TG_WAP54G_R4hc14jh3P1swd

List of preferred networks: 1 item(s)
Profile: _TG_WAP54G_R4hc14jh3P1swd
SSID: _TG_WAP54G_R4hc14jh3P1swd
SSID length: 25
Connection mode: Infra
Security: Yes
Set by group policy: No
Connect even if network is not broadcasting: No
Connectable: Yes

Information for Connection ID 1
Connection started at: 2007-03-15 16:58:06-366
Auto Configuration ID: 1
Profile: _TG_WAP54G_R4hc14jh3P1swd
SSID: _TG_WAP54G_R4hc14jh3P1swd
SSID length: 25
Connection mode: Infra
Security: Yes
Pre-Association and Association
Connectivity settings provided by hardware manufacturer (IHV): No
Security settings provided by hardware manufacturer (IHV): No
Profile matches network requirements: Success
Pre-association status: Success
Association status: Success
Last AP: 00-18-f8-31-ef-e3
Security and Authentication
Configured security type: WPA-PSK
Configured encryption type: CCMP(AES)
802.1X protocol: No
Key exchange initiated: Yes
Unicast key received: Yes
Multicast key received: Yes
Number of security packets received: 21
Number of security packets sent: 21
Security attempt status: Success
Connectivity
Packet statistics
Ndis Rx: 92560
Ndis Tx: 57566
Unicast decrypt success: 0
Multicast decrypt success: 0
Unicast decrypt failure: 0
Multicast decrypt failure: 0
Rx success: 237
Rx failure: 0
Tx success: 0
Tx failure: 0
Roaming history: 0 item(s)

</Data>
<Data Name="EventVerbosity">0</Data>
</EventData>
</Event>
===

[Sanity check: This is a known-good wireless LAN in daily use with other
machines. Signal strength is excellent and the network seems reasonably
reliable apart from this issue. Updated drivers to most recent Intel release,
and retested, but issue remains outstanding.]

--
Cecil Ward

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://windowshelp.microsoft.com/com...orking_sharing