January 1, 0001

— type: post layout: post meta: {} title: Wireless Client Update for Windows XP with Service Pack 2 tags: - Tips and Tricks published: true status: publish — Windows released the Wireless Client Update for Windows XP with Service Pack 2 in January of 2007. By all accounts it seems to have resolved some of the reasons why I switched to using the Intel PROSet Wireless application.

The Wireless Client Update lets you configure wireless networks as broadcast networks or as nonbroadcast networks. Additionally, Wireless Auto Configuration sends probe requests only for nonbroadcast networks.

Since the latest release of the Intel software caused 100% CPU usage on my machine I ditched and went back to Windows management of wireless. With this Client Update installed I haven’t had any problems so far with my wireless network that isn’t broadcasting the SSID. Excellent. Thanks to the Non-broadcast Wireless Networks with Microsoft Windows article for providing the link to this breakthrough. Setting up the nonbroadcast network isn’t as simple as it was for the Intel wireless management, but at least it’s possible without the machine going into a tailspin:

  1. View the wireless networks that are available. More than likely the nonbroadcast network won’t be displayed.
  2. Click on the Change advanced settings link underneath the Related tasks heading in the left hand pane.
  3. Choose the Wireless networks tab.
  4. In the Preferred networks section click on the Add button.
  5. Fill in the SSID that is being broadcast and select the Connect even if this network is not broadcasting checkbox.
  6. Save the changes and then see if Windows tries to connect to the network. This should fail since you haven’t specified the wireless network key. I found that I had to do this before Windows would even let me set the Wireless network key though.
  7. Hopefully now the network shows up in the list of networks that are available. If it does, go into the configuration settings for it again (this time the SSID should be disabled) and specify the correct wireless network secuirty settings for your network.
comments powered by Disqus