davismit
05-05-2005, 12:10 PM
Over the last couple of weeks several wireless users I support have been dropping off their networks and are not able to pass traffic even when associated with the WAP/s.
Hardware
Various desktop and laptops with Windows XP Home and Pro
Proxim AP-600s
Seems to occur after service pack updates... Nothing conclusive.
Some folks do automatic upates others manually.
Using 128 bit WEP encryption
(Can't use WPA because the wide variety of wireless adapters in use. Many users have older cards/interfaces that do not support WPA)
Symptoms:
Network shows connected good/excellent signal strength
Viewing the Wireless Network Connection status window...
Activity shows that
Packets Sent increments
Packets Received always zero (0)
(after disable re-enable to clear counters)
Properties shows that
128 bit WEP key
Network Authentication is "shared"
"Key index" matches
This has always worked... until recently
Now here is the kicker...
Incrementing the client's key index by one as compared to the WAP fixes the problem.
Example Setup:
AP WEP key 128 Bit 00112233445566778899aabbcc
Key index 1
Client WEP key same
Key index 2
This works!!! Seems a bit slow to associate and get an IP via DHCP but it works.
The Proxim site sez the key index must match. (As far as I know it always has.)
Proxim has a new knowledge base entry (5/2/04) regarding the WEP KEY index mismatch but it appears to be incorrect. (flat out wrong)
I checked my solution with three different types of cards
Linksys wireless G WPC54G
Orinco Gold Card
Sony Vaio with Intel Pro wireless LAN 2100 3b mini pci adapter
All work when the client key index is one more than the WAP key index.
This took awhile to sort out since misconfiguring something to get it to work is not a usual troubleshooting step.
Has anybody else run into this?
Has anybody else experienced the mystery 'connected but zero packets returned' after a service pack update?
Is the culprit Proxim or is it XP service packs?
Vexed,
Dave
Hardware
Various desktop and laptops with Windows XP Home and Pro
Proxim AP-600s
Seems to occur after service pack updates... Nothing conclusive.
Some folks do automatic upates others manually.
Using 128 bit WEP encryption
(Can't use WPA because the wide variety of wireless adapters in use. Many users have older cards/interfaces that do not support WPA)
Symptoms:
Network shows connected good/excellent signal strength
Viewing the Wireless Network Connection status window...
Activity shows that
Packets Sent increments
Packets Received always zero (0)
(after disable re-enable to clear counters)
Properties shows that
128 bit WEP key
Network Authentication is "shared"
"Key index" matches
This has always worked... until recently
Now here is the kicker...
Incrementing the client's key index by one as compared to the WAP fixes the problem.
Example Setup:
AP WEP key 128 Bit 00112233445566778899aabbcc
Key index 1
Client WEP key same
Key index 2
This works!!! Seems a bit slow to associate and get an IP via DHCP but it works.
The Proxim site sez the key index must match. (As far as I know it always has.)
Proxim has a new knowledge base entry (5/2/04) regarding the WEP KEY index mismatch but it appears to be incorrect. (flat out wrong)
I checked my solution with three different types of cards
Linksys wireless G WPC54G
Orinco Gold Card
Sony Vaio with Intel Pro wireless LAN 2100 3b mini pci adapter
All work when the client key index is one more than the WAP key index.
This took awhile to sort out since misconfiguring something to get it to work is not a usual troubleshooting step.
Has anybody else run into this?
Has anybody else experienced the mystery 'connected but zero packets returned' after a service pack update?
Is the culprit Proxim or is it XP service packs?
Vexed,
Dave