WAP4410N drops the connection

Unanswered Question
Jan 19th, 2012

Hi! We have a 4410N that all the time drops the connetion. We have approx 25-30 users using wireless. But when they try to connect or are connected, the router drops the connection like a yo-yo. The firmware is updated with no difference.

The wireless connection is very unstable. It's configured with WPA2 Personal and is connected through a POE-switch with IPv4. The logs don't answer the questions why it drops the connection.

Does anyone of you have any clue?

Sent from Cisco Technical Support iPhone App

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
David.Clinton Mon, 01/23/2012 - 13:47

I'm Having the same issue. 

I did a ping test from the Wap Prior to power cycleing it (which fixes it for a day or so.) and I got this

PING 192.168.1.109 (192.168.1.109): 32 data bytes

32 bytes from 192.168.1.109: icmp_seq=0 ttl=127 time=7.2 ms

32 bytes from 192.168.1.109: icmp_seq=1 ttl=127 time=1.5 ms

32 bytes from 192.168.1.109: icmp_seq=3 ttl=127 time=2.9 ms

32 bytes from 192.168.1.109: icmp_seq=4 ttl=127 time=1.8 ms

--- 192.168.1.109 ping statistics ---

5 packets transmitted, 4 packets received, 20% packet loss

round-trip min/avg/max = 1.5/3.3/7.2 ms

Then I did one after the power cycle and got this.

PING 192.168.1.109 (192.168.1.109): 32 data bytes

32 bytes from 192.168.1.109: icmp_seq=0 ttl=127 time=1.2 ms

32 bytes from 192.168.1.109: icmp_seq=1 ttl=127 time=2.1 ms

32 bytes from 192.168.1.109: icmp_seq=2 ttl=127 time=3.3 ms

32 bytes from 192.168.1.109: icmp_seq=3 ttl=127 time=1.4 ms

32 bytes from 192.168.1.109: icmp_seq=4 ttl=127 time=2.1 ms

--- 192.168.1.109 ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max = 1.2/2.0/3.3 ms

My setup is WRVS4400N v2 with Cat6 strait to the WAP4410N.  I updated the firmware on both devices.  and the Wap is not using POE.

It is on static. IP address. and the IP address of 192.168.1.109 is my computer.

Whats Happening?

David.Clinton Mon, 02/13/2012 - 14:37

Goodspeed,

I folowed Andrew Rankin's link and read that post and what i came up with is

Dont use Channel 1.

so 1 week ago i

I Put a Power filter on the  Wap.

I changed it from Channel 1 to 11.  I havent got a call yet. 

Dave

d2ydx2day Thu, 02/16/2012 - 00:18

Hi Dave,

Don't think the change of channel will help everyone. I tried this before too. Seemed to last a few days, then the issue reappeared.

What exactly do you mean by power filter? Are you powering via PoE?

Andrew

glenngoodspeed Fri, 02/10/2012 - 15:19

I'm having the same problem with a 4410N.  It works fine for a while, then it stops accepting wireless clients.  A soft reboot from the admin screen fixes it for another while.  Haven't determined yet how long it stays up between reboots -- it's somewhere between a few hours and a few days.  Here's the strange part.  We have two older 4410N's and they work fine.  It's only this new one that malfunctions.  I called Cisco support and have returned the unit twice.  The first time it was replaced with a used Linksys-branded unit.  The latest replacement was new, still in shrink wrap.  Both replacements had the same problem as the original unit.  I guess I've had enough replacement units.  Wonder if Cisco can fix the one I have now?

All three of our 4410N's are configured in access point mode with the same SSID.  All three are plugged into an ASA5505 that has a VLAN dedicated to the wireless network.  I use NetStumbler to view competing wireless networks, and there is nothing out there causing interference.  All APs are using different channels.

More info:

PID VID:  WAP4410N-A V02 (found under Status, Local Network)

Two older units that work:

Serial: SER145200Y3

Serial: SER145200X2

New unit that has the problem:

Serial: SER153600ZW

Seems this WAP has always had this problem, judging from the many threads here about it.  Looks to me like the firmware got fixed at some point and then some new internal component broke it again.  Someone really needs to fix this.

Edit:

I was going over this again, and realized that the two WAP's that are working have firmware version 2.0.3.3, while the one that's not working has firmware 2.0.4.2.  I'm going to downgrade the new one to 2.0.3.3 and see if that helps.

glenngoodspeed Thu, 02/16/2012 - 13:07

O.K., that seems to have fixed my bad WAP.  I installed firmware 2.0.3.3 and it has been running fine for two days.  When it had 2.0.4.2 firmware, it stopped accepting wireless clients within 30 minutes.  I recommend trying 2.0.3.3 if you are having this trouble, especially if your serial numbers fall between those above.  Download is available from Cisco.  Look for the download button on this page:

David.Clinton Mon, 02/20/2012 - 13:05

Andrew,

     Power Filter =  Panamax M8EX that I plug the WAP power supply into.  So No POE.  and your correct.  1 Day after i posted that the Call Came.

Looks Like Goodspeed found our answer.  Going to inplement ASAP.

Goodspeed,

     What Range of S/N?

Thanks,
Dave

glenngoodspeed Tue, 02/21/2012 - 09:12

Serial numbers of our access points are listed in my post above.  I re-read some other threads about this problem, and some people have had the same trouble with 2.0.3.3 firmware.  So the 2.0.3.3 firmware may or may not work better in your application, but it does seem to work better than 2.0.4.2 here.  Obviously Cisco still has some work to do on this:

https://supportforums.cisco.com/thread/2054732?start=0&tstart=0

brian.sloan@gs5... Mon, 04/08/2013 - 13:25

We have the latest firmware 2.0.6.1 installed and we only seem to have the issue when using PoE for the WAP.  Once we plugged the WAP into the wall the issues went away.  I am wondering if there is an issue with their PoE implementation for the device.  Is anyone having the issue with it plugged into the wall on the latest firmware?

Actions

Login or Register to take actions

This Discussion

Posted January 19, 2012 at 2:02 AM
Stats:
Replies:9 Avg. Rating:
Views:2728 Votes:0
Shares:0
Tags: No tags.