Rogue SSID's causing connectivity problems

[trevorjackson]

I am using a Cisco 350 series access point and I keep having problems with my users picking up other SSID's and attempting to connect to them. I am using 128 bit WEP encryption on my SSID and there is some form of encryption on the rogue SSID's. They are systems using Windows XP with built in wireless NIC's. Please advise.

[mcnaz-yeo]

Try using Cisco ACU client software if your Client is using cisco card, else use the GUI which has the profile driven, this seem to have a better control then WZC. Using centrino Intel pro if your are using the intel centrion builtin eireless I presume

Regards

[chandlerbr]

Here are a couple of options you may want to explore.

If using the Cisco ACU, when the SSID field of the profile is empty/blank, the Cisco client adapter will attempt to connect to any broadcast SSID it sees. Be sure you hardcode the SSID in the ACU profile. You should make sure there are no other profiles in the ACU with blank SSIDs that are participating in Auto Profile Selection. Also, if you have no additional need for a built-in or PCMCIA WiFi adapter using Windows management, stop and disable the WZC service in the Control Panel.

If you are allowing windows to control your wireless client adapters, add the desired SSID the Wireless Network properties, configure your WEP settings and make sure you can connect to the AP. Then deselect the "Use Windows to configure my wireless network settings" option, stop the WZC service, and set the service to manual or disabled to make sure it doesn't auto-start at the next system boot-up.