Clients freezing up

Unanswered Question
Apr 1st, 2009
User Badges:

Has anyone experienced a situation where clients freeze ? The systems in question simply freeze (not bluescreen)and will unfreeze if you remove the wireless adapter. I have listed a couple details about the symptoms below:


1. Occurs on more than one type of client adapter. Proxim a/b/g gold and Intel 2200bg


2. After freezing if you unseat the adapter it will release the operating system (WinXPSP2) and if you reseat it the wireless will re-associate.


3. We have multiple sites that are affected and different code levels on our controllers. (3.2.193.10 and 5.0)


4. The problem is very sporadic and only occurs a couple of times a day on varying clients.


I believe this to be a client issue but I need to prove it. Any help would be greatly appreciated.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Leo Laohoo Wed, 04/01/2009 - 19:55
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Get another WLAN NIC and check it out. I don't think this has anything to do with Cisco's product. More to do with firmware.

Scott Fella Thu, 04/02/2009 - 18:47
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Does this occur when the client roams to another ap or when they are just sitting there? Depending on the client device, try to upgrading to the latest driver release or comapre the driver versions of the devices that are affected the most with the devices that seem to not have any issues. Verify the settings on the client device too. On the WLC side, you can try to tweak some stuff like making sure that 1 and 2 mbps data rates are enabled, disable aironet IE, make sure dhcp required is not checked. Another thing you can try is to play around with the session timeouts on the wlan. Try to set it to the max which is something like 65535 or something like that and ses if any of these help.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode