Wireless and XP

[Dave Opalenik]

We're seeing a problem that has occurred on two
machines. Both are running Windows XP; one runs XP
Home, the other XP Professional.

We have a Linksys wireless router in our home. Each of
these machines was successfully configured to be on the
wireless LAN. When the wireless card was removed, and a
second (different brand) card was installed, the
connection was never established. No encryption is
used. We've double-checked the obvious, like SSID, etc.

I've replicated this problem in the field by trying to
connect to a Cisco wireless access point. My Linksys card
works just fine, but when I install and configure a Cisco
Aironet 350 card, it can't find the wireless network.

Could this be a bug in XP when you instal a second
wireless adapter?

 

[Raf]

-----Original Message-----
We're seeing a problem that has occurred on two
machines. Both are running Windows XP; one runs XP
Home, the other XP Professional.

We have a Linksys wireless router in our home. Each of
these machines was successfully configured to be on the
wireless LAN. When the wireless card was removed, and a
second (different brand) card was installed, the
connection was never established. No encryption is
used. We've double-checked the obvious, like SSID, etc.

I've replicated this problem in the field by trying to
connect to a Cisco wireless access point. My Linksys card
works just fine, but when I install and configure a Cisco
Aironet 350 card, it can't find the wireless network.

Could this be a bug in XP when you instal a second
wireless adapter?

.

This would not be a defect in windows xp. One suggestion
I have for you is to make sure the card is showing in
devmgr, ipconfig and network connections.
You may want to try setting the SSID and Channel ID in
the advanced settings of the card (device manager). That
would be one reason for the card not seeing the SSID.


Raf

 

[Barb Bowman [MVP-Windows]]

can you duplicate this using WEP? is the SSID being broadcast?
what happens if you disable and enable the card when it gets in this state?
what happens if you release - renew with ipconfig?
is there anything in the event log?
does this happen if you assign static IP's to the cards?

I've seen some similar weirdness on one machine here with multiple broadcom
based 802.11g pccards installed connecting to some, but not all g routers.