NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
X10 r9000 wont stay connected to xbox one s
I had an Asus rt87u that worked perfectly. I upgraded to the r9000. I have kids and a very connected home with typically 8 to 10 devices on the network. All work fine wired or wireless except my xbox...
Well, I owe Netgear and the Community an apology. Turning of the Xbox Instant On feature solved it. Now I can start hounding Microsoft.
I have tried it with a reserved IP address and without. I have tried static IP on the Xbox (manual) and DHCP (automatic) in every combination. The firmware is the lastest that came out a few days ago.
Test with setting the 5Ghz radio from max Up to speed to 300Mb only.
Set WPA2 and AES only and manual channel 48 or 149.
Disable HT160 and MU-MIMO features as well if present. Maybe found under Advanced, Advanced wireless section.
Id try downloading the Beta version of the FW which has QoS UI in the FW. Factory reset the router, manually load the file using IE11 or FF browsers, factory reset once more then set up from scratch. Set up reservations again for each xbox.
I have factory reset and reloaded and built from scratch so many times. What I would like is for Netgear to fix it and not have me beta test and solve for them. A $500 router that won't connect to an Xbox should not be a problem for the end user to fix. I have never had a router (even $39 ones) NOT work with Xbox since they first came out in 2005. While I appreciate the community support, it would be nice if I could just plug it in and have it work. I have 4 kids with multiple devices. Between 10 and 20 on the network at any given time and NONE disconnect or have issues except the Xbox and we got a second Xbox One since my first post and it has the same issue.
Please try my suggestions.
I demo'd this unit earlier this year and didn't see this issue. Of course, I didn't load up to date FW.
This maybe a FW issue in resent FW so if the suggestions don't work. Try the Beta build of the FW and try again. You've been the only one to post about this particular issue so it maybe a just a bad unit or a mis-configuration.
IF you don't feel like trying the maybe you should return the router.
I may get ambitious and give it a try. Just for info it's done this since first day and every revision of firmware. It's fine and stays connected until I shut the Xbox off. Then the next time I turn it on it won't connect.
Also disable Instant ON on the xbox 1s. There is a known issue with this feature causing problems with networking. Especially NAT status.
I would get LAN wired connected at some point as well.
I will try the instant on thing, I have not tried that. I have tried a wired connection with different cables and different ports, same issue. Doesn't matter if it's wireless or wired. So the instant on may be the key. Good idea!
Try the other suggestions as well on 5Ghz or downgrade FW. IF this is happening on both wired and wireless. Could be a different issue.
Let us know how it goes.
Well, I owe Netgear and the Community an apology. Turning of the Xbox Instant On feature solved it. Now I can start hounding Microsoft.
Good luck in getting them to fix that. Been a problem since the xb1 came out. Glad yours is working now.
My Xbone is "instant on" and I STILL have the same issues. I've got the QoS turned on, and speed test done, I've got static IP, opened necessary ports for gaming, etc. It also, is hard-wired with a cat-6 cable. So, I don't thinkl you owe ANYONE an appology. THere's something odd about this SUPER expensive router, NOT doing its job. I have a feeling it wants to block our xbox from the network, thinking it's not allowed to take up bandwidth....when...well....it's the exact opposite!
Even if turning "instant on" to OFF....why would it be affected? Why would I LOSE that feature on my Xbone? That doesn't make much sense!
Sorry, you can't come out of standby mode to use this router because it's 1992!"
