I was hoping that with the arrival of Service Pack 2, Microsoft's
position on non-broadcast SSIds might be more in line with the rest
of the industry.
However it does not seem to be the case.
Here are the results of some attempts to associate with a non-broadcast
SSID both in the absence and presence of broadcast SSIDs.
Three types of "silent" SSIDs were defined.
1) 802.1x
2) WEP key defined
3) No WEP key
The Wireless Network Connection Properties has the followed "Advanced"
settings.
Access point (infrastructure) networks only is checked
Automatically connect to non-preferred networks is unchecked
All broadcast SSIDs are removed from the preferred list.
The 802.1x SSID was configured as follows.
Association Window
Network Authentication - Open
Data encryption - WEP
The key is provided for me automatically - Checked
Authentication Window
Enable IEEE 802.1x authentication - Checked
EAP type - Protected EAP(PEAP)
Properties
Validate server certificate - Unchecked
Select Authentication Method - Secured password(EAP-MSCHAPv2)<BR>
Automatically use my Windows logon name - Unchecked
Enable Fast Reconnect - Unchecked
Authenticate as computer ... - Unchecked
Authenticate as guest ... - Unchected
The results were
No successful association was made to the 802.1x SSID either in the
absence or presence of a broadcast SSID.
This was attempted by adding the SSID afresh and also following a reboot.
As soon as the 802.1x SSID was set to broadcast, the XP machine could
detect it and successfully connected when requested to do so.
The two other types of SSID could be made to connect as follows
1) Immediately after the SSID was added to the preference list.
(IE by removing it and then adding again if already present.)
Moving it to the top of the list, or opening the properties and
clicking OK, both had no effect.
This was possible in both the absence and presence of a broadcast SSID.
2) On system startup, but only in the absence of a broadcast SSID.
Can anyone make their XP SP2 machines behave any better with different
settings. The 802.1x situation seems to be the bigger problem.
Bill
Bill Byers email: [log in to unmask]
Edinburgh University Computing Service Phone: (+44) (0)131 650 4951
James Clerk Maxwell Building Fax: (+44) (0)131 650 6552
The King's Buildings, Mayfield Road URL:
http://www.homepages.ed.ac.uk/bill
Edinburgh, EH9 3JZ
|