|
#1
|
|||
|
|||
|
Hello,
I've set up a wireless network for a small apartment building using the the WMS5316 and six WNDAP360s (will be adding additional units). My problem is that the access points constantly kick users off and go up in down in terms of connectivity. The APs have not been on in a stable state for some time. I've been working with NETGEAR support on this issue for a couple of months. They've been helpful, but I wanted to post to the forums in case someone else might have some ideas about what could be causing these issues. I have the WMS5316 up to firmware 2.1.2 and the WNDAP360s are up to firmware 2.1.1. Any help would be appreciated, Zachary Power |
|
#2
|
||||
|
||||
|
How are they setup?
__________________
. Forum Rules - Post Screenshots on ImageShack for Free - Firmware Upgrade Procedure . Online Subnet Calculator - LAN Subnets NOT to Use - SA Lifetime Guidelines - Hex/IP Converter . Free Netgear Support Online Trouble Ticket Submissions 1-888-NETGEAR 4,3 Netgear Knowledge Base . VPN Router Support, Interface Demos,and Marketing Pages: . SRX5308 S M - FVS336G S I I M - FVS318G S M - FVS318N S M - FVS338 S I I M - SRXN3205 S M - VPNG01/5L S M - FVS318 S I I M - DGFV338B S I M - FVG318 S I I M - SSL312 S I M - FVX538 S I I . FVS114 - FVS124G - FVS328 - FVL328 - FWG114P - GPL Firmware Code - MyOpenRouter - VPNC Docs . Click Here for my VPN Client and Mode Config VPN Client Tutorials . ProSecure STM/UTM Appliance User Forum - Prosecure Marketing Website . . Good Luck...ADIT FYI - I am a Reseller and not employed by Netgear |
|
#3
|
|||
|
|||
|
Log in to WMS.
Go to Configuration-system-Basic-Time and disable NTP client. It should solve the rebooting problem. I found a bug and reported it to Netgear support team. The cause of the problem: WMS is a linux appliance. When WMS boots it starts some processes that exchange some messages/heartbeats via IPC or something else. If there's no messages from processes called "WNC APPs" in 24 seconds time interval, WMS "watchdog" process "thinks" that something's wrong with WMS itself and reboots it! If you configured NTP then WMS's system clock periodically is being corrected and "watchdog" sees timeouts because it relies on system time! To check that, log into WMS console (via SSH or via serial COM). When system time is corrected by NTP or manually (remember it's Linux) you'll see message "No punch from WNC APPs for atleast 24 seconds, resetting device"... Turn off NTP and you'll never see that message and WMS reboots!
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|