DHCP not issuing valid IP address sometimes?? No internet

[Soss]

Nest Wifi intermintantly picks a device at random and wont issue the correct ip address. The device is connected to the wifi but with no internet,  soon as you go into the settings on the said device the issue is obvious.   DHCP hasn't assign an IP address....  and it has 172.16.1.___   instead of the usualy 192.168.86.____

There are periods where there are no issues though,  sometimes a few weeks can pass trouble free. Having said that no previously connected device seems to be immune from the random issue. Its has happend to iPads, Samsung tablets, samsung phones, 2 different TCL google TVs etc ( having said that, The Xbox, PCs and Sony TV haven't had the issue yet.  The only thing that resolves this issue for me imediately is to assign a static IP address with the correct prefix 192.168.86.___ and the correct gateway 192.168.86.1  on the DEVICE, and suprise suprise everything instantly connects to the internet.

Having to do this is very frustrating all the time.

I have troubleshooted and done everything i possibly can to resolve this.

Factory resets, restarts, restarts and connecting devices in sequence you name it,  I even investigated an date a time issue that it could have possibly been......

Network Devices I have in my network bellow

TP-Link Archer VR600v, Netgear Switch GS724Tv4, Nest Wifi x 3 ( 1xrouter 2xaps ) and are connected in the following order bellow

TP-link ( in bridge mode) --->  Nest Wifi Router ----> Netgear Switch (dhcp disabled recieves ip from nest router) ----> wired devices (PC, Printer, Laptops, NVR etc)  All other devices in my house are wireless and theres about 20 or more, they range from TVs, phones, tablets, toys, xbox's etc.

Like i said, this issue is random,  and intermittant,  which ever device it decides it wont issue an ip address to, is a device that would have been previously succesfully connnected to the network with flewless internet functionallity.

So why is the Nest Router doing this from time to time????

PS: Assigning every single device in my network with a static IP address is not a solution, and VERY ANNOYING. 

Anyone out there got some insight here?

[macali]

Did you figure this out? I am having the same problem, changed DNS, the rogue scan is pointing to google wifi router. 

[NeoMeir]

Repost: I've now been just using bridge mode with the Nest WIFI router with forced IP assignment 
Primary Server 8.8.8.8
Secondary Server 8.8.4.4
IPV6 Server 2001:4860:4860::48
I have had zero issues with IP's since then.

[Maserlaser]

The only thing that seems to help was I shut off ipv6 and upnp.  Seems to have cleared it up for a while now

[nested666]

I am now experiencing the same issue. I have a Mac so I can’t run the rogue detection software (am also very unfamiliar with all of the terminology anyway.)

using the guest network works for me but I’d obviously like to resolve the issue still

earlier this week I was using a raspberry pi to run pihole and pivpn but when this issue started, I shut down the pi and reverted the settings I had touched in the google home app (dhcp reservation, port forwarding, dns setting). The only thing that won’t delete is dhcp address pool. Not sure if this even has anything to do with the issue

[NeoMeir]

Repost: I've now been just using bridge mode with the Nest WIFI router with forced IP assignment 
Primary Server 8.8.8.8
Secondary Server 8.8.4.4
IPV6 Server 2001:4860:4860::48
I have had zero issues with IP's since then.

Everything beyond bridge mode can be set in the WIFI settings in the home app.

[nested666]

Feedback I got from support

———

You can clear some cache on the cloud server by disabling-enabling the Nest Wifi cloud services.

Home app > Wifi icon > Settings > Privacy settings > toggle off and on the Nest Wifi cloud services.

also pause and unpause family wifi group

———

[UncleBabyBilly]

Same issue for me but I dont have any rogue dns servers I run pi-hole for DNS and set Google wifi to DHCP range of one IP address.  That IP is assigned to HD Homerun and uses a .99 address.   My DHCP range is 100-150 on my primary dns server and 151-200 on secondary.  Occasionally that device it will fall off that .99 address into the DHCP range.  Rebooting that device usually fixes the issue.  But not sure why it's happening honestly and continues to be an ongoing issue.

[LovelyM]

Hello everyone, 

Thanks for posting and I'm sorry for the delayed response. Let’s see what’s going on.

A few questions: was this working fine before? If yes, when did the issue start? What's your network topology? Aside from the reboot, what troubleshooting steps have you taken?

Looking forward to your response. 

Best,
Lovely

[LovelyM]

Hi there UncleBabyBilly,

I want to ensure you are good to go. Please reply to this thread with the information asked above if you still need assistance so I can give you a helping hand.

Cheers,
Lovely

[LovelyM]

Hey UncleBabyBilly,

It's me again. I'll be locking this thread in the next 24 hours. If you have new issues, updates or discussion topics, feel free to start a new thread here in the Community.

Many thanks,
Lovely