11-04-2009 09:17 AM
One of my customers just installed a WAP610N. They were doing initial testing of connecting to the wireless network and it was inconsistent at best. It would connect and then say "limited or no connectivity". I logged into the web administration page and clicked on the status page. Here it showed an IP address and subnet mask, but no default gateway...which is very strange since it definitely has a default gateway manually set. So I went to the primary setup page and verified it did have the proper gateway information set. Without making any changes, I clicked on the Save Settings button. I then went to the Status page and now the default gateway is showing. I had the customer disable the wireless on the laptop and then turn it back on again. Now everything is working fine.
Now here's the strange part. I've rebooted the access point twice, and after each reboot the default gateway does not show on the Status page. It shows it's configured properly on the main setup page, but it's not showing on the Status page. Again I simply have to click the Save Settings button and then go back to the Status page for it to show up. So for some reason when the WAP610N is rebooted, it doesn't assign the default gateway that it's given. Laptops can connect to it but cannot route anywhere due to the missing default gateway on the access point. (Note that the laptop itself DOES in fact get a proper default gateway since it pulls the info from the DHCP server, but since the default gateway isn't set on the access point it still doesn't route properly).
It looks like there are no firmware upgrades available for this device. Any ideas/suggestions? Is there a new firmware release due soon?
11-05-2009 10:52 AM
08-24-2010 09:30 AM
I'm having the same problem. Although network connectivity works for a few days, then stops. Sometimes the WAP and the router need to be restarted to get it to work. Was there ever a solid fix for this?
09-28-2010 10:05 AM
I am also experiencing this issue. I lose the default gateway on the status page, which ultimately prevents wireless clients from getting a dhcp address from the server. Restarting the device does not fix it. The only way to get it back is to click on save settings on the basic setup page. Any help would be appreciated.
09-28-2010 08:09 PM
I have had the same issue since I purchased this device.
Has there ever been a fix other than the firmware mentioned in the earlier post?
Or should I just give up on this thing.
09-30-2010 06:38 PM
The WAP610n seems to be defective and either a firmware upgrade should be provided, or purchasers should be invited to exchange it for hardware that actually works. I have spent hours with and without Cisco support (useless), to no avail. For this money, and in this day and age, this thing should be plug-and-play. Very frustrating.
10-22-2010 04:49 AM
I guess I am not the only one having these isues. It seems that every couple of days the unit needs to be rebooted in order for users to connect. Users are able to pick up the device but it will not allow then to connect to it. Once the unit is rebooted, all is well for a couple of days.
11-16-2010 03:43 AM
we just found out about this problem right after we ordered 20 WAP610N's to function as AP's on our sites...
only solution for now is to put the unit on DHCP, when you enter a manual ip+gateway the gateway is lost after a reboot.
I'm thinking of returning them all if there's no quick fix for this.