cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
2363
Views
5
Helpful
1
Replies

Client keeps disconnecting on regular intervals

holzhirt1
Level 1
Level 1

Dear community,

We are running  WLAN using WPA2-enterprise with AES & IAS server.

Mostly we are using AP's 1131 and Cisco WLC 4400.

I added on a new location 2 AP 1142G and since the installation I got 3-4 clients having regular disconnections...

Basically they are connected immediately to the infrastructure but after a certain amount of time the Win7 icon is having this yellow exclamation sign, and we can see that the connectivity is gone (however the IP settings seems to be still in place, but ping or network browsing is not possible).

Stopping the WLAN and starting it again solve immediately the issue (via software or via the notebook switch). Normally the problem doesn't resolve by itself.

I was working beside the laptop having the problem with (my own laptop) during the person got 3 disconnections, mine was running like a charm...

I really suspecting a Laptop issue...

We have 85% of the people there working errors free...

Just to summarize what I did :

  • Checked the 1142 AP for any logs or errors, interfaces status etc...
  • Checked the switches behind, interfaces seems running smoothly
  • Checked IAS / WLC / WCS for any logs that can indicate an issue
  • Compared WLAN adapter settings of the faulty laptop with mine, discovered some differences and adapted it.
  • Compare the WLAN SSID config in Win7 with mine and adapted the slighty differences found.
  • Used WCS troubleshooting client tool

What I will do again :

  • Verify if the persons having the issue have the same laptop model
  • Verify settings in the BIOS
  • Verify WLAN adapter driver version
  • Verify BIOS version
  • Use WCS troubleshooting client tool on my own laptop at this place

So do you know this problem? do you have an idea how to solve it?

Thanks for your help

Regards

1 Reply 1

holzhirt1
Level 1
Level 1

To help some that could have same issue :

It was related to a network card driver version,

In my case it was a known Intel bug,

Regards