NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WNDAP350's are constantly rebooting
WNDAP350 significant problems I have 5 of these on various network segments over a large geographical area. All are using different wiring, different network switches, nothing in common with any o...
I should point out that I believed my 350's were working fine. The users never really reported any problems other then usual “sometime slow printing” or, “my Email client required I re-authenticate to the Email server”; things that could be solved by updating out of date drivers or stop wandering between cells, etc. Most all users attributed their problems to old operating systems, not enough memory, or this is just the way the laptops run. It's the OS; just reboot and everything worked fine.
When looking at the 350's logs I would see nothing wrong. At that time I didn't really pay attention to the fact that the logs only kept about 10 minutes of data.
The way I found out that these units had problems is from my network management software. It checks to see if all the units on my network are alive by pinging them every 10 seconds. I usually do not check it's logs because I see everything in the green all the time. However, one day I did check the logs and saw that the 350's were frequently not there then reappearing in about 30 seconds or so. When looking at the 350 logs I didn't see anything because the problem had already scrolled out of the buffer. It was a cat-and-mouse game for several days until I caught a 350 going dark. I immediately checked it's log and found the “ping failure”. I saved the log. After doing a lot more legwork I picked up on the fact that the problem was more severe as the number of associations increased. And, the problem was only associated with the 350's.
So, like I said, I hadn't been made aware from my users that there were any kind of problems that I could associate with anything other then normal under provisioned hardware for the kind of heavy duty apps. they were trying to use.
It's quite possible others have this problem and never know it.
Just some thoughts.
Bob
When looking at the 350's logs I would see nothing wrong. At that time I didn't really pay attention to the fact that the logs only kept about 10 minutes of data.
The way I found out that these units had problems is from my network management software. It checks to see if all the units on my network are alive by pinging them every 10 seconds. I usually do not check it's logs because I see everything in the green all the time. However, one day I did check the logs and saw that the 350's were frequently not there then reappearing in about 30 seconds or so. When looking at the 350 logs I didn't see anything because the problem had already scrolled out of the buffer. It was a cat-and-mouse game for several days until I caught a 350 going dark. I immediately checked it's log and found the “ping failure”. I saved the log. After doing a lot more legwork I picked up on the fact that the problem was more severe as the number of associations increased. And, the problem was only associated with the 350's.
So, like I said, I hadn't been made aware from my users that there were any kind of problems that I could associate with anything other then normal under provisioned hardware for the kind of heavy duty apps. they were trying to use.
It's quite possible others have this problem and never know it.
Just some thoughts.
Bob