That's an R7000? Look for "Model" on the product label. Firmware version? Connected to what?
> The Orbi picks up an ip address in this rage: 192.168.107.xxx
The first mystery would be from where it's getting that address. If the R7000(?) is "serving IP addresses in the 192.168.1.2-254 range" (which would be normal), then my first guess would be that you have some other DHCP server on your network, and it's operating on a "192.168.107.*" subnet. I would not bet that the DHCP server in an R7000 is granting IP addresses from some different, odd-ball subnet.
> None of these connected devices can communicate with the Internet > through the NIghthawk.
If they're using different IP subnets, then that would not amaze me.
> I can force connection of a device by fixing an IP address for the > Nighthawk and setting the device to manually assigned IP address.
I have no idea what that means. "fixing" what, exactly, how, exactly? "setting" how, exactly? Describing actual operations with standard terminology would be more helpful than vague and idiosyncratic intepretations of what you think the meaning of what you did is.
> The Orbit did not used to do this. [...]
Perhaps you didn't always have some other DHCP server on your network.
The problem was that the ADT Alarm company's gateway, a Netgear device, was assigning IP addresses. The ADT installer, some years ago, connected the LAN side of the gateway to a switch serving my whole-house CAT5 network . This served a purpose at the time of allowing cameras or other ADT-controlled and wired devices to receive an PI address from the gateway. The Orbi, in access point mode, was on the same switch. This allowed the ADT gatway to assign IP addresses to wireless devices. The only mystery is why, over the past couple of years the Orbi has been operating in this mode and configuration, was the ADT gateway not assigning addresses but instead the the Nighthawk R7000 managed to do all the wired and wireless IP assignments through the same switch.
Regardless, mystery solved.
Regardless, problem solved by disconnecting the LAN side of the ADT gateway from the physical network to which the Orbi attached.
For reference and answer to @antinode 's questions:
Yes, R7000. There is no other Nighthawk with the 7000 number.
fixing, as in the verb, "fix": "to give a permanent or final form to." A fixed (static) IP address is an IP address is a dedicated IP address. In this context, "fixing" as in "assigning" - perhaps a dated term.
Knowing what "fix" means (which I did) does not help to discover what's being fixed. "an IP address for the Nighthawk" does not say which of the two IP addresses you meant, or how, exactly, you were fixing it. A router like this has an address for each of its interfaces, WAN/Internet and LAN.
> [...] A fixed (static) IP address is an IP address is a dedicated IP > address. [...]
Not really.
Terminology: A "static" address is configured on the device itself. What you configure on a (DHCP server on a) router is a reserved dynamic address, not a static address. Either is a fixed address, but they're not equivalent for all purposes.
So, "[...] you have some other DHCP server on your network [...]"?
But it's nice that you found the offending device, whatever it is. (You might want to mark the thread as Solved.)
For reference and answer to @antinode 's questions:
Yes, R7000. There is no other Nighthawk with the 7000 number.
For future reference, there is also the D7000 Nighthawk DSL modem/router and the C7000 cable modem/router, not to mention the R7000P router.
It may seem like nit picking to want to know what we are talking about but they are all different and people have got them confused in the past.
I could also lob in the A7000, which people sometimes use that model number when posting questions about the X7000, bit that is a completely different kettle of fish.
