WEP+XP doesn't work, yet WEP+Linux is fine

qubit · 12-31-2004

This problem has been bothering me.

I have a DLink DWL-5000AP (802.11a AP), and I have been unsuccessful in connecting to it using Windows under Open and Shared WEP (Proxim Silver PCCard, DLink DWL-A650 PCCard, DLink DWL-AG520 PCI). All the computers have the same installation, so I'm suspecting a Windows error. The installation is of Windows SP1 with August Autopatcher (no SP2).

Wondering if this were really a Windows problem, I started up linux on one of the computers, used the proxim card (atheros chipset and cvs madwifi drivers), and stuck in the commands: "iwconfig ath0 essid blah key s:zzzzz enc on", and if it were shared, "iwpriv ath0 authmode 2", and a "dhclient ath0" would get me right on track, while the windows machine AT THAT SAME MOMENT would not be able to get authenticated at all.

Disabling WEP and falling back to the MAC whitelist works fine. Entering the key in hex and ASCII makes no difference. I just get "Wireless Networks Detected, Click here to . . .", and it sends me in an infinite loop. Deleting the network from the preferred networks list and reconfiguring makes no difference.

I've also tinkered with the AP. I've upgraded the firmware to the latest version on dlink's site, used a default shared key, or individualized shared key, 64 bits and 128 bits, to no avail. Linux, however, kept up with every change made, and everything was working (including pinging and accessing the rest of the network through the AP).

Can anyone shed light on this problem? Thanks in advance.

streaker69 · 12-31-2004

It's gotta be something you're missing on your configuration there. I currently have 4 machines on my network here at the house, all WinXP sp2 with varying NIC's. One Dell Truemobile 1150, One WPC54G, a USR 11mb card (don't remember the model) and a Netgear PCI 54mb Card. They all connect just fine to my Linksys WAP54G and my WAP11. All running 128bit WEP.

I've set up hundreds of machines with varying operating systems and NIC's in the past year or so, and I've never seen the problem you're describing.

qubit · 01-01-2005

Configurations settings aside (though I have mysteriously experienced Windows insisting that my network is Open and not Shared when I tell it to, and resets itself back to Open in the next "Wireless Network Found!" cycle), have there been any instances were the patches and updates installed on Windows affect whether or not you can connect to a WEP network? There are several articles on Microsoft's Knowledge Base, but none of them deal with my computers. I also suspect the fact that all of them are almost nearly identical in terms of patches.

Thorn · 01-01-2005

Quote:

Originally Posted by qubit

...(though I have mysteriously experienced Windows insisting that my network is Open and not Shared when I tell it to, and resets itself back to Open in the next "Wireless Network Found!" cycle)...

"Open" and "Shared" are Authentication methods and have nothing to do with the encrypted status of the network.

When you switch it to "Shared" on Windows , you're telling it to use a different way to authenticate. If you also don't set it to Shared on the AP, then it fails authenticate on the next detection cycle, and resets to Open, authenticates using Open and works. Windows is just telling you that.

By the way "Open" is more secure than "Shared", due to the way it functions. Leave it set to Open Authentication with WEP/WPA encryption to make the network as secure as possible using the built in mechanisms. (It's not too secure, but it's a start.)

qubit · 01-01-2005

Ah okay thanks. I'll set it to open then.

Does it matter that Windows reverted back to open even though the AP had shared authentication set?

On a side note, where can I find something that describes the technical differences between open and shared, and why shared is less secure?

wrzwaldo · 01-01-2005

Quote:

Originally Posted by qubit

Ah okay thanks. I'll set it to open then.

Does it matter that Windows reverted back to open even though the AP had shared authentication set?

On a side note, where can I find something that describes the technical differences between open and shared, and why shared is less secure?

Google...

qubit · 01-01-2005

Quote:

Originally Posted by wrzwaldo

Google...

Ironically, google pointed me back to netstumbler forums. =)

WEP Authentication

As an update, the linux laptop I had used to diagnose my connection now has successfully connected onto windows. I repeated what I did on the other computers, and still no sign of success. The only thing I changed was the SSID on the AP (leaving it on broadcast so my dumb Windows clients won't dump that AP for another broadcasting its SSID). As far as I can see, the length of the SSID may have an affect, going from a 11-letter long SSID to a 4-letter long SSID. May this have an effect?

ShadowFX · 02-01-2005

Quote:

Originally Posted by qubit

Ironically, google pointed me back to netstumbler forums. =)

WEP Authentication

As an update, the linux laptop I had used to diagnose my connection now ...<SniP>... May this have an effect?

subscribe to:
microsoft.public.windows.networking.wireless

There is a discussion on this problem.

12-31-2004	#1 (permalink)
qubit Registered Member Join Date: Dec 2004 Posts: 4	WEP+XP doesn't work, yet WEP+Linux is fine This problem has been bothering me. I have a DLink DWL-5000AP (802.11a AP), and I have been unsuccessful in connecting to it using Windows under Open and Shared WEP (Proxim Silver PCCard, DLink DWL-A650 PCCard, DLink DWL-AG520 PCI). All the computers have the same installation, so I'm suspecting a Windows error. The installation is of Windows SP1 with August Autopatcher (no SP2). Wondering if this were really a Windows problem, I started up linux on one of the computers, used the proxim card (atheros chipset and cvs madwifi drivers), and stuck in the commands: "iwconfig ath0 essid blah key s:zzzzz enc on", and if it were shared, "iwpriv ath0 authmode 2", and a "dhclient ath0" would get me right on track, while the windows machine AT THAT SAME MOMENT would not be able to get authenticated at all. Disabling WEP and falling back to the MAC whitelist works fine. Entering the key in hex and ASCII makes no difference. I just get "Wireless Networks Detected, Click here to . . .", and it sends me in an infinite loop. Deleting the network from the preferred networks list and reconfiguring makes no difference. I've also tinkered with the AP. I've upgraded the firmware to the latest version on dlink's site, used a default shared key, or individualized shared key, 64 bits and 128 bits, to no avail. Linux, however, kept up with every change made, and everything was working (including pinging and accessing the rest of the network through the AP). Can anyone shed light on this problem? Thanks in advance.

12-31-2004	#2 (permalink)
streaker69 Psychic Amish Stumbler Join Date: Jul 2004 Location: Virginville, BlueBall, Bird In Hand, Intercourse, Paradise, PA Posts: 11,798	It's gotta be something you're missing on your configuration there. I currently have 4 machines on my network here at the house, all WinXP sp2 with varying NIC's. One Dell Truemobile 1150, One WPC54G, a USR 11mb card (don't remember the model) and a Netgear PCI 54mb Card. They all connect just fine to my Linksys WAP54G and my WAP11. All running 128bit WEP. I've set up hundreds of machines with varying operating systems and NIC's in the past year or so, and I've never seen the problem you're describing. __________________ "One of these days, I'm going to cut you to pieces." If you're offended by this post, please feel free to report it to one of the many helpful moderators of this forum. Thank you.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

01-01-2005	#3 (permalink)
qubit Registered Member Join Date: Dec 2004 Posts: 4	Configurations settings aside (though I have mysteriously experienced Windows insisting that my network is Open and not Shared when I tell it to, and resets itself back to Open in the next "Wireless Network Found!" cycle), have there been any instances were the patches and updates installed on Windows affect whether or not you can connect to a WEP network? There are several articles on Microsoft's Knowledge Base, but none of them deal with my computers. I also suspect the fact that all of them are almost nearly identical in terms of patches.

01-01-2005	#5 (permalink)
qubit Registered Member Join Date: Dec 2004 Posts: 4	Ah okay thanks. I'll set it to open then. Does it matter that Windows reverted back to open even though the AP had shared authentication set? On a side note, where can I find something that describes the technical differences between open and shared, and why shared is less secure?