NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
A6200 timing out Windows 10
Hi All, hope I'm not starting a new thread, surely I can't be the only one here with this issue. After upgrading (???) to WX I have found that my WiFi Network icon gets a red X on the top left hand...
Aye, I have the same problem. I think other users might be on to something with the data volume theory. I managed to go 27 hours 57 minutes and 16 seconds on my connection duration at one point before it disconnected in the same manner as you described during which I had no Livestream nor youtube video open. And of course, unplugging it, and plugging it in again fixes it. Same device, same drivers, and of course same OS. This is really starting to get old and Netgear support was of no help to me.
I also made a thread on Tomshardware to document my trials, tests, failed solutions, etc: http://www.tomshardware.com/forum/id-2746425/internet-cuts-windows.html
I need to add disabling QoS Protocol in The Network and Sharing Center properties. Apparently it's responsible for bandwidth and internet flow. I'll update you guys...if it works...so long as my net holds out. Good luck guys!
I am absolutely sure the issue has nothing to do with data. I have just downloaded WX Pro and WX Home uninterrupted. It's a timeout thing. My question is, I was using W7 for over a year with the A6200 without any issues, so why after the install of WX have I all of a sudden started having issues. It's not like WX hasn't been available for hardware companies to trial and test their devices so that a stable driver or firmware update can be downloaded. I note that the one on the Netgear site is still labelled "beta" so I'm wondering if the problem lies in the firmware of driver set and has nothing to do with WX
Sorry I forgot to mention, just as a side note, I have an ASUS Notebook connected to WX via its WiFi reciever and it has not logged off once since I installed WX and that has been three days now, Its only affecting the A6200 device...