NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
stevedude
Mar 22, 2019Aspirant
Nighthawk R7000 won't recognize network devices connected through switches
Nighthawk R7000 Windows 10 Pro
latest firmware update on 3/22/2019 V1.0.9.64_10.2.64
Router recognizes about half of my network. Doesn't recognize switches or devices that would be connected t...
- Jun 01, 2019
Solved. Got a buddy to help me sort it out. The internet provider company had installed not just a gateway to the fiber optic system but a modem router combo as well. I told them that the router part needed to be off as I was using my own. They may or may not have done so but their piece of equipiment was still setting up its own subnet which is where the non-recognition problem lay. Removing that piece of equipment and hooking my router directly to their "gateway" {their term}, which apparently functions as a modem even though they don't call it that, fixed all my problems.
stevedude
Mar 23, 2019Aspirant
>"switches"? "devices"? Details? What's connected to what, how?
1. 3 computers & 2 Roku are connected to the network through Trendnet switches. each of the computers and Roku just mentioned has access to the internet and so must pass a signal through the router even though thay are not directly connected to the router by lan port. none of them are visible on Windows 10 Pro network diagram or on 10-Strike Network Scanner as being part of the network as stated above. there is a Tablo device (an OTA TV tuner) on the router that should be acessible by both of those Roku devices. it was able to connect with the Roku devices with the now dead Asus router. there is a third Roku device connected directly to one of the lan ports on the router which can connect to the Tablo device.
>Is this a new router, or a new firmware version, or what? If your
R7000 replaced some other (unspecified) "previous routers", did all your
IP addresses stay the same, or did some (or all) change?
New router with the latest firmware. I imagine that some of the IP addresses on the network itself have been reallocated by the new router. I have no way to determine that at this time.
stevedude
Mar 31, 2019Aspirant
Well, guess I'll look at other communities and forums for help. The one response I got was just criticism and not at all helpful.
- stevedudeJun 01, 2019Aspirant
Solved. Got a buddy to help me sort it out. The internet provider company had installed not just a gateway to the fiber optic system but a modem router combo as well. I told them that the router part needed to be off as I was using my own. They may or may not have done so but their piece of equipiment was still setting up its own subnet which is where the non-recognition problem lay. Removing that piece of equipment and hooking my router directly to their "gateway" {their term}, which apparently functions as a modem even though they don't call it that, fixed all my problems.