NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
XR 500 Network map not showing wired xbox one x
I have tried to reach out to a couple others forums on here without any solutions. The only way I can get the xbox one x to show up is either rebooting, unplugging or flushing cloud. This issue has s...
I started this thread in January. Still not fixed. There is nothing that can be said on my disappointment with this issue. A gaming router that can see consoles and will not fix it. That is the issue. Also you lost a costumer. Once this thing breaks I am not going to get a netgear again.
Some of the devices have a static ip. My laptop for example. Also dhcp on my tplink is disabled so it shouldnt be giving ips out right? Its an archer c7. I just ordered a newer A20 router to use as AP so maybe it will fix my issue
Be sure the TP Link is configured for LAN to LAN AP mode. Connect the LAN cable from the XR router to the LAN port of the TPLink, not the WAN port on the TPLink. Possible the TPLink doesn't work well in AP mode configuration.
Let us know if the new AP fixes this.
- It currently is LAN to LAN. The a20 should have ap mode feature. The archer c7 is done manually so yeah im sure its the c7 causing issues. For sure. Ill update
:smileywink:
I'm running the .40 firmware and seeing the same issues with wired xbox and other devices. After the router is rebooted everything seems to work just fine for a period of time (I haven't taken the time to see if turning xbox off or whatever triggers problem) then I'll notice that xbox traffic is shown in the network monitor with a different device's name, or not at all, while the QoS screen shows that "High Priority Traffic Detected" xbox traffic is being handled. Other devices also sometimes are shown with the wrong name or not at all. I.E. the other day (router had been up for 5 days and showing xbox anomaly) I fired up my pellet grill, that has 2.7 wireless connectivity. The pellet grill functioned correctly and I could see it and control it with my phone app so It was on the 2.7 network of my router, but it did not show up ANYPLACE on the network monitor screen. The next day I notice a new device in the Offline area of the network map and on checking the MAC address it was my pellet grill. A reboot of the router and everything will work fine again for a while. Functionally everything connected to my network seems to be working correctly with no problems. The only problem I see is that DUMAOS seems to stop talking correctly to the router about what is connected. Seeing other comments about downgrading to .32 fixing Network Map issues makes me think that the .40 firmware update is causing DUMAOS some minor problems.
Not having any functionality problems I'm going to wait for another update to see if it fixes these problems. Should I want to try the .32 firmware I am wondering if the downgrade would require setting up things like reserved IPs again or if all current settings would be retained?
Thanks!
Todd