Performed another experiment.

Began WAN/LAN packet capture on Orbi debug page.

Closed lid on laptop (put to sleep).

Plugged power into Nest Mini. Took a minute, but it came alive and told me the time. (Hey Google, what time is it?)

Connected Linux laptop to Orbi WiFi. Entered password. Opened up web pages. Connection working.

Opened lid on Win 10 laptop. Woke up. Entered password. "Unidentified Network." Funny round icon.

Waited about 90 seconds.

Started Network troubleshooter. Selected ethernet port.

Now network shows as ORBI80 (which is what it is). Laptop has IP address.

Logged into Orbi debug page and saved debug log.

Use Wireshark to display DHCP packets.

Clearly shows the Nest Mini and the Linux laptop doing exactly what the DHCP protocol says to do:

Device broadcasts "Discover"

DHCP server responds "Offer"

Device sends "Request"

DHCP responds "ACK"

The Win 10 laptop, however did NOT follow the protocol:

Laptop broadcasts "Discover"

DHCP server responds "Offer"

Laptop broadcasts "Discover"

DHCP server responds "Offer"

This went on for 114 seconds until I the Network troubleshooter kicked in.

Finally, the Win 10 laptop followed the protocol. Discover->Offer->Request->ACK.

I remain convinced that although there are definite issues with the way Netgear handled DHCP in the context of IP assignments, the DHCP process follows the protocol. My Windows 10 laptop does not. Why? No idea. It's a major pain in the nether region. I have searched for "Unidentified network" and got nothing helpful.

Forum Discussion

Where to buy CBK43