04-17-2022 06:27 AM
For the last 3 or 4 weeks now I have been getting random internet connectivity issues on my Nest Wifi device.
These seem to occur in bursts, it will seem fine for a while then disconnect, reconnect, disconnect, reconnect and so on a few times, before running OK for a few hours and doing it again.
This is horrible for things such as work calls as I work from home.
Having a look at various threads here I can see many other people are having the same issue.
My device seems to be on version 14150.43.80 but still has this issue...
04-17-2022 09:43 AM - edited 04-17-2022 09:51 AM
Have you added any wireless equipment that is not neccessarily Wi-Fi lately? Like a home theater, sorround system, bluetooth or similar? Could be interference.
It could help to factory reset the network (https://support.google.com/googlenest/answer/6246619?hl=en) and set it up from scratch (https://support.google.com/googlenest/answer/9548301?hl=en). Use the same network name (SSID) and password, then your devices should reconnect automagically.
For greater speeds and reliability, you could consider to use a wired backhaul.
Other troubleshooting tips:
04-19-2022 05:58 AM
I have tried reset factory 3 times, still having the same issue
Has tried with DHCP WAN ( behind ISP's router ), also PPPoE WAN ( ISP is briding ), all same unstability issue
04-19-2022 12:41 PM
Create a new thread so your issue can be escalated separatly.
04-20-2022 04:33 AM
This is the exact same issue, you're suggesting that doing factory reset, I said I've done that three times
And I also explain multiple WAN methods, that descibes that whatever the WAN mode is, the issue persists
Then tell me which part I'm saying that this is an unrelated issue that I need to start another thread ?
04-20-2022 04:48 AM
Try setting the DNS on your google wifi to Custom and point it to the google DNS servers. It seems to have worked for me so far...
04-21-2022 10:29 AM
Hi, gorip96.
deathkraiser's suggestion of using the Google DNS servers is definitely helpful. Give that a try and see if you are able to see better results at that point. Let me know if you have any questions about that.
Thanks.
04-21-2022 05:52 PM
Hi Jeff
I’ve tried the workaround, and it works, but you must not input the IPv6 DNS as well
IPv6 seems totally broken on 14150.43.80 , even only set the IPv6 DNS, the router keeps losing connection, until I remove them, and just leave them with IPv4 DNS servers only
04-27-2022 10:27 AM
Hey, gorip96.
We're actually looking into possible IPv6 issues on the new release. Have you seen any error messages, or it simply just an unstable connection?
Thanks.
04-27-2022 08:11 PM
Hi @Jeff
i don’t see any error message, because the Nest isn’t providing any kind of way to view the system log messages
but the system starts to stabilize once I disable IPv6, and using IPv4 only DNS on the system settings
04-28-2022 01:36 PM
Thanks, gorip96. I replied to your other thread. That post had a lot of helpful details, thanks for sharing all that! We're looking closer into the issue now.
Thanks.
06-08-2022 02:26 PM
Hey, all.
We haven't had much movement here for a while, so I want to check in to see if anyone was still looking for help here or if we've managed to sort out the issues. Let me know if you're still looking for help.
Thanks.
06-15-2022 11:48 AM
Hi, everyone.
Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.
Thanks,
- Jeff
04-19-2022 05:57 AM
i'm having the exact same issue, now my network is almost useless
04-19-2022 03:38 PM
Hey, deathkraiser.
I just wanted to jump in real fast to see if you saw olavrb's reply and to see if you still needed some help on this or if you were able to get it sorted out. If you are still needing some help, just let us know and we'll be happy to continue helping. Thanks for all the helpful info there, olavrb!
Thanks.
04-19-2022 05:28 PM
Because this is an intermittent issue, it's hard to say whether it has been properly fixed yet.
I ignored all the support provided so far as it hadn't helped anyone else with this problem (just check this forum or do a quick google).
One thing I did see was someone mentioned switching to custom DNS (still pointing to Google DNS, just custom instead of automatic). So I have applied that a few days ago and it hasn't dropped yet, however it wasn't an every day occurance so it may still occur at some point in the near future.