NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
HansHeintz
Dec 30, 2017Aspirant
NightHawk X8 R8500 wifi 2.4 Ghz collaps 1 week after purchase
Nighthawk R8500 V1.0.2.106
Hi,
Bougth NightHawk X8 R8500 a week ago. Did all I wanted to for a week.
Suddenly iphone cannot connect, wants me to reenter 5Ghz-ssid password, again and again.
2.4Ghz not visible anymore.
Restarted the router. Now it seems 5GHz is working, also at the right speed.
2.4GHz is unreliable, sometimes it works, sometimes iphone needs password, sometimes "no internet connection", speeds if working 1.17 Mbps down, was 81.27 Mpps at some point last week (speedtest app iphone). 5Ghz speeds are usually between 180-200.
My network:
Lan with 2 extra switches, DS1812 NAS, 2 window pcs
Wireless: various 2.4Ghz devices (philips hue, homewizard domotica,2 chromecasts, logitech ultimate hub)
No fiddling with any settings between happy and deplorable.
What could it be?
- Replacement installed. Configuration backup from former device restored. All is functioning without problems.
5 Replies
- JamesGLMaster
Hi HansHeintz,
Did it happen after the update?
Have you tried to reset the router to factory default after the firmware update?
- JamesGLMaster
Hi HansHeintz,
Let us know if the replacement works.
- HansHeintzAspirantReplacement installed. Configuration backup from former device restored. All is functioning without problems.
- HansHeintzAspirantIt was before the update. I did a normal and a 30-30-30 reset without improvement. At some point I even could not login over UTP anymore. After contacting netgear netherlands the device has an RMA number. I hope I am just unlucky. Usually I avoid expensive versions of products because in my experience they are less reliable (smaller production, less feedback / testing, experimental features, more problems) so at this point it feels like i fell for the old “the more expensive, the better” illusion. But we’ll see how the replacement fares.
- HansHeintzAspirantPowering down all 2.4ghz devices had already been part of my troubleshooting.