Alice Faber answered this one for me in a usenet posting:
If you're connecting through the Windows XP interface, click on the
Advanced tab. In some XP installations, there's a default setting that
will guarantee that you won't connect, hidden on the Advanced tab. I
forget the exact wording of it (I don't have access to an XP box to
check), but it will say something about smart card authentication.
On the main tab, you may have to search out a pulldown menu that will
allow you to selecte Shared authentication also.
The key phrase is "shared authentication". A google search on this phrase and "airport" brought a lot of hits:
A few key notes:
Be sure the right XP services are running
1.) Go to Start -> Control Panel -> Performance and Maintenance -> Administrative Tools -> Services.
2.) Scroll down to Wireless Zero Configuration, and double-click Wireless Zero Configuration.
3.) On the General tab, after Startup type, change the startup type to Automatic.
4.) Start the service by clicking Start.
A few discussions, and an aside that Apple's advanced tech support was clueless.
This is where they point out the need to enable "shared authentication". There's a hint that older 802.11b implementations don't support it.
Lots of discussions on Airport wireless.
Serious Mac wireless vendor.
Accessing a Airport Network with a Windows XP PC or laptop (WEP enabled)
Patch required if running Windows XP and WPA on an AEBS
The three main reasons people have problems are
1. WEP Key in plain text and not HEX
If you enable WEP on the AEBS, you need to note down the Hex Airport Network Password, if you are using 128bit encryption this will be a 26 digit number.
If you open the Airport Admin Utility you should see something like this
You may need to click a button called Password
Note that I have blanked out my passwords
The Wireless ASCII Equivalent Password is the plain text network password you use to access your Airport network with a Mac.
The Wireless Hex Equivalent Password is the hex version of the plain text, and this is what you would use with your PC.
2.IEEE 802.1x authentication is on
Ensure that the Enable IEEE 802.1x authentication for this network check box is not checked.
3. Authentication Mode is not set to Shared
Ensure Network Authentication (Shared Mode) box is ticked
On a separate topic, a wireless bridge for 802.11g AEBS networks, I found:
and an other great usenet posting sent me to:
Bottom line: usenet lives.