getting "Status code 13' connecting to a di-524 dlink router wep shared key

[madamos]

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.)

 

[Saltgrass]

The D-link supports Open System, have you tried that?

I am not a network expert, or Windows for that matter, but it sounds like it isn't the level of encryption, but the type.

What key you use depends on both systems. If you can use a passphrase, that is usually easier, but you may have to use the same HEX numbers, or ASCII if both systems support it. The 104 bit you use is also called a 128 bit and a 40 bit is a 64 bit. The lower numbers refer only to the part you can change.

 

[madamos]

Thanks for replying.

Its set right now to use a passphrase according to my friend. I'm not going to be there again until Sunday, but the plan is to go over the settings again when I'm there and I'll check the passphrase and auth type then.

Oh, if it helps anyone I found that dlink has emulator/simulators of their router interface up on the web:

DI-524

 

[johngalt]

I have a pair of those and I had to use it in a pinch when my DGL-4300 stopped grabbing an IP address from my cable modem. The DL-524 worked fine with my HP 2710p laptop running Windows 7 x86, until I bought the DGL-4500....

 

[madamos]

Fixed, though not what I'd have thought.

Illustrating my biggest problem with newer MS software, the settings aren't always what you think they are.

I'd deleted and readded the connection. The SSID was being broadcast and I'd just entered the key when asked. None of that worked.

I'd tried changing the settings from open to shared and back and forth.

Last night I tried one more time, opened the network item from the systray, right clicked on the network and opened properties and changed the dropdown from open to shared and entered the passphrase again. Then it started working. :shock:

What I don't understand is why it automagically selected Open for the auth type? I'd set it to shared from the network and sharing center in control panel - but aparently the setting never "stuck".

Its just plain wierd. But its working now so, yay!

 

[Digger]

madamos, actually this is good for roaming protection and honeypots. You have to setup your profiles for networks using encryption, atleast this has been a good habit for me. This way it wont roam away to another AP (if i'm totally understanding your situtation).
Also i would persuade your friend to change to WPA anyways. WPA2 is starting to already become mainstream, i say by next year it WILL be. Only problem with wpa2 is things like Nintendo Wii and ps2 (and psp i think) doesnt support that encryption.

Alot better encryption, especially if you have sensitive data and are jumping from network to network. I have yet to play around with this situation much on my laptop. Have yet to take it outside my own network.