NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Troubleshooting
19780 TopicsFVS114 Router Login Took Too Long to Respond
When I attempt to login to the FVS114, I get the error message "www.routerlogin.com took too long to respond". I have removed/re-inserted power and tried to login (nothing), did a hard factory reset and tried to login (nothing), cleared Win Edge browser cache (nothing), switched Edge to IE mode (nothing). I have used a different ethernet cable for FVS114 to computer & gateway (nothing). Am I to the point of accepting this device is pooched and I have to move on? Any advice is appreciated. Thanks, Kym.51Views0likes5CommentsWAX210 Firmware 1.1.0.34 Bug – SSID Password Complexity Incorrectly Enforced
Hi everyone — I’m seeing what looks like a firmware regression on the WAX210 after updating to v1.1.0.34, and I want to report it in case others are affected. After updating, the AP now refuses to save any configuration changes (even unrelated ones like just renaming the Access Point). The UI throws this error: SSID1: SSID passphrase length must be between 8 and 63 characters, and contain at least one uppercase letter, one lowercase letter, one number, and one special symbol. This happens even when the SSID password is not edited at all. The AP loads the existing (valid) WPA2/WPA3 passphrase and flags it as invalid due to a complexity requirement that didn’t exist before. This appears to be the AP Login Password complexity policy being mistakenly applied to SSID passphrases, which contradicts the official manual. SSID passwords for WPA2/WPA3 should only require 8–63 characters. Reproduction Steps Update WAX210 to firmware 1.1.0.34 Log into the web interface Make any change (example: AP Name only) Click Apply The SSID password complexity error appears, even though SSID settings were untouched Impact. The AP cannot accept any configuration changes unless the SSID password is replaced with a much more complex passphrase. This forces a complete re-key of all connected devices. Expected Behavior Per the WAX210 User Manual, SSID passphrases should be valid with: 8 to 63 characters No requirements for uppercase/lowercase/digits/symbols Those rules worked correctly in previous firmware versions. Current Workaround Rolling back to firmware 1.1.0.25 or 1.1.0.20 fully resolves the issue. Request Can Netgear please confirm whether this is a regression in 1.1.0.34 and escalate to the firmware engineering team? This issue effectively prevents configuration of the device. I can provide: Screenshots of the error dialog A configuration backup A short video showing the issue Exact hardware revision and serial if needed Thanks in advance.586Views4likes16CommentsGS110TP V2 Firmware 5.4.2.36
The Release Notes for the GS110TP V2 firmware version 5.4.2.36 say only: Security Fixes: Various security vulnerability fixes and enhancements. https://kb.netgear.com/000064041 How does that help us understand what will behave differently with this firmware? It doesn't! The developers might as well have said "We've changed some stuff, but we aren't going to tell you what." Very disappointing Please do better.Old ReadyNAS 212 won't boot up
So, many, MANY, years ago, my workplace merged with another company, and as part of that merger, I took over their IT system, which consisted of a few peer-to-peer PCs and a central storage system consisting of two ReadyNAS devices, one primary and one backup. Some time later, the backup NAS failed. Rather than fix or replace it, I opted to move to a cloud storage backup system instead, and the old unit was shelved. Fast forward to the modern day, amid a bunch of other IT problems cropping up (mainly, the current state of Microsoft OneDrive causing a cascade of problems with the cloud backup), the question of the the longevity of our current NAS device was raised. By my best estimation, that NAS has been going strong for upwards of 11 years now, and while it's performance has been incredible, it's at a point where it could fail at any moment. As part of the disaster recovery planning, the decision was made to try to refurbish the old backup NAS, just in case an immediate replacement is necessary before a full replacement can be purchased and implmented. That brings me to my current issue. The old NAS is able to power up, but then all the lights go out and it doesn't load anything. I have probed the Hard Drives on my PC, and while I haven't been able to access the files directly, the disks themselves seem to be fully functional. Most worryingly, attempting to access the Boot Menu with the reset button has failed entirely. Any advice of how I can get this old thing functional again? Preserving the data doesn't matter, they're just outdated backups, I just need to get the NAS Enclosure itself functional and active.SXR30
Hello, Use a Orbi SXR30 with 4 satellites for my home network. Previous to recent Insight update (4.3.4.300) phone app listed all connected devices and allowed blocking access through the app. Now when clicking "connected devices" the app shows "no connected clients available". On the "about" tab of the app, it shows 38 connected clients. Thanks for any assistanceWAX610 cannot be added to Insight - ownership release required
Hello, I have a NETGEAR WAX610 that I cannot add to Insight. Error message: "This device was previously added to a different account." I have already factory reset the device multiple times. Serial number: 6KE10C280023E I understand this device was previously used at another location and I do not have access to the original account. Could you please assist with ownership release so I can use the device with Insight? Thank you.318Views1like8CommentsWAX210 iPhone WPA3 Incorrect Password isBSSIDDenylisted 1
Hi I've been using a WAX210 as my home access point for a few months and every few days my iPhone is banned from the network. It won't auto-connect and if I manually connect it fails with "Incorrect password" I enabled iOS Wi-Fi diagnostics and it shows the BSSID has been banned for connections, with isBSSIDDenylisted 1. WAX210 running latest Firmware V1.1.0.34 released 25th July 2025 iPhone 16 Pro running latest iOS 26.3.1 5Ghz network WPA3 password I have also submitted feedback to apple as FB22209711 in case it is their bug. I believe it's either a bug in the WAX210 that is getting it banned by the iPhone or the iPhone's banning logic is too restrictive. Relevant log lines below: 03/12/2026 9:02:39.181 __WiFiDeviceManagerKnownNetworkSuitabilityCheck: Network 'agate', isFilteringAJCandidates 0, isSSIDTemporarilyDenylisted 0, isBSSIDDenylisted 1, isTDDenylisted 0 03/12/2026 9:02:39.181 __WiFiDeviceManagerKnownNetworkSuitabilityCheck: Not considering problematic Network agate isSSIDTemporarilyDenylisted 0 isBSSIDDenylisted 1 isFilteringAJCandidates 0 isTDDenylisted 0419Views0likes15CommentsGS110EMX: 10G ports throttle uploads to 250-300 Mbps
I've been going back and forth with Netgear support for over a week about this and I'm honestly at a loss. I'm hoping someone here can tell me if I'm crazy or if what they're telling me doesn't make sense, because it really doesn't add up to me. My Setup Switch: Netgear GS110EMX (firmware 1.0.2.8) Port 1: Internet uplink (1G, connected to router — standard fiber ISP) Port 9: Mac Pro via OWC Thunderbolt 4 to 10G Ethernet Adapter Port 10: Asustor AS6508T NAS (10G) Cables: Cat6A throughout This is exactly why I bought this switch — two 10G ports for my computer and NAS, with everything else on the 1G ports. Pretty standard home prosumer setup. The Problem Internet uploads are throttled to about 250-300 Mbps when my computer is on a 10G port. Downloads are fine at 830-880 Mbps. When I move the same computer to a 1G port with the exact same cable, uploads jump to 708 Mbps. That's more than double the speed on a port that's supposedly 10x slower. What I've Tested (at Netgear's request) I ran every test their L3 support team asked for. Here are the results: Internet Speed Tests (computer on 10G port 9): Flow Control Download Upload OFF 865 Mbps 306 Mbps ON (port 9 only) 879 Mbps 169 Mbps ON (both 9 & 10) 820 Mbps 137 Mbps Internet Speed Test — computer on 1G port (same cable, same everything): Download Upload 884 Mbps 708 Mbps iPerf3 between Mac and NAS (local, 10G ↔ 10G): Direction Speed Mac → NAS 3.73 Gbps NAS → Mac 9.40 Gbps Local 10G performance is excellent. The ports, cables, and NIC all work fine. What Netgear Says After all this testing, support came back and told me: This is "working as expected" and "within the design limitations of the switch" The 10G ports are "intended to be used as uplinks" — not for client devices A replacement would behave the same way My configuration is "not the intended use case" Why I'm Confused I don't understand how any of this is "expected behavior." Specifically: How does a 1G port give me faster uploads than a 10G port? If the 1G uplink is the bottleneck, moving to a slower port should give me equal or worse speeds. Not more than double. Nobody has explained this. Why are only uploads affected? Downloads through the 10G port hit 865 Mbps — nearly saturating the 1G uplink. The traffic crosses the same 10G/1G speed boundary in both directions. Why would only one direction have "buffer overflow" problems? Flow Control made things WORSE. They asked me to enable it. It dropped uploads from 306 Mbps to 137 Mbps. How is that a fix? The product page says "No Network Bottlenecks thanks to the 2 10-Gigabit/Multi-Gigabit Uplinks." Now support says those ports are only meant to be uplinks and my setup is unsupported. The user manual literally shows 10G client devices connected to ports 9 and 10 in its network diagrams. This switch used to work. I used the exact same setup with fiber in Chicago for years with no issues. I only noticed the problem after switching to fiber here in LA recently. Something changed. What I'm Asking Has anyone else seen this? Am I wrong to think a managed switch should be able to handle 10G devices sending traffic through a 1G uplink without losing 70% of the uplink's capacity? I've seen a couple other threads about similar issues with the GS110EMX and I'm starting to think this is a known design flaw that Netgear just doesn't want to acknowledge. At this point I just want to know if I should keep fighting for a replacement or just give up and buy a different switch. Any insight would be really appreciated. I've spent way too many hours on this already.