New
#1
getting "Status code 13' connecting to a di-524 dlink router wep shared key
Hi,
I'm having a strange issue with my Windows 7 Lenovo S10 netbook and a friends WEP enabled router. I am able to connect to my home network wr54g linksys on WPA and at the office there's a guest network running (oddly) a 104bit WEP that I can use. However at my friends house I was trying to connect to his DI-524 Dlink router and recevied some very strange (to me) messages. Here is the detailed information from the event log:
-----------------------
Log Name: System
Source: Microsoft-Windows-Diagnostics-Networking
Date: 2/8/2009 6:29:42 PM
Event ID: 6100
Task Category: Helper Class Info
Level: Information
Keywords: (70368744177664),Helper Class Events
User: LOCAL SERVICE
Computer: antaeus
Description:
Details about wireless network adapter diagnosis:
For complete information about this session see the wireless connectivity information event.
Helper Class: Native WiFi MSM
Initialize status: Success
Information for connection being diagnosed
Interface GUID: 5f560a5c-5f1c-42b0-842a-21713fb9b364
Interface name: Broadcom 802.11g Network Adapter
Interface type: Native WiFi
Profile: Discovery connection
SSID: BubbaHotep
SSID length: 10
Connection mode: Infra
Security: Yes
Connect even if network is not broadcasting: No
Result of diagnosis: Problem found
Root cause:
Windows does not support automatically connecting to a network using WEP shared-key authentication.
Detailed root cause:
802.11 connection to WEP network failed with status code 13: Unsupported authentication algorithm
Repair option:
Modify the wireless security settings for “BubbaHotep”
If you set up or own this network, you might be able to fix the problem by configuring the wireless router or access point to use open authentication.
Contact the network administrator or your hardware manufacturer for further assistance.
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>0x4000400000000002</Keywords>
<TimeCreated SystemTime="2009-02-09T01:29:42.514918800Z" />
<EventRecordID>1205</EventRecordID>
<Correlation ActivityID="{C91D4831-3104-4C07-A8EC-1356569E43C9}" />
<Execution ProcessID="1096" ThreadID="3464" />
<Channel>System</Channel>
<Computer>antaeus</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="HelperClassName">wireless network adapter</Data>
<Data Name="EventDescription">For complete information about this session see the wireless connectivity information event.
Helper Class: Native WiFi MSM
Initialize status: Success
Information for connection being diagnosed
Interface GUID: 5f560a5c-5f1c-42b0-842a-21713fb9b364
Interface name: Broadcom 802.11g Network Adapter
Interface type: Native WiFi
Profile: Discovery connection
SSID: BubbaHotep
SSID length: 10
Connection mode: Infra
Security: Yes
Connect even if network is not broadcasting: No
Result of diagnosis: Problem found
Root cause:
Windows does not support automatically connecting to a network using WEP shared-key authentication.
Detailed root cause:
802.11 connection to WEP network failed with status code 13: Unsupported authentication algorithm
Repair option:
Modify the wireless security settings for “BubbaHotep”
If you set up or own this network, you might be able to fix the problem by configuring the wireless router or access point to use open authentication.
Contact the network administrator or your hardware manufacturer for further assistance.
-----------------------------------------
I'm wondering if Windows 7 has some kind of issue with older versions of WEP and possibly lower encryption? Potentially could it be simply that if we kick up the encryption it will work? I'm fairly confident that if I convince him to kick it to WPA it will work - but where's the fun in that.
Thanks for reading.
(Posted from the same Lenovo S10 running Windows 7 Ultimate on a WEP network that it seems to like for some reason.)