cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

"It looks like there's an unknown server on your network."

bananaslug79
Community Member

This message starting showing up in the Google Home app at the top of the "updates" list (right icon at the bottom). Tapping it takes you to https://support.google.com/googlenest/answer/9193085

Network background: two Nest Wi-Fi routers wired together in a supported configuration (have had this for 6 to 12 months without issue). There are no other messages in the Home app to indicate any problems so far this week despite the above message sticking itself to the top of my updates list, and I haven't noticed any network problems otherwise.

Being an old network guy, I can tell you the last thing that changed was a Midea Wi-Fi enabled air conditioner unit added on the day this message starting showing, plus two TP-Link Kasa smart bulbs and at least one or two mini smart plugs added. None of the added devices give any indication of issues with Wi-Fi (despite the horrendous app setup and Wi-Fi configuration of the Midea unit) but I suppose I can't rule out one or more of these behaving badly since they were the last things added to our network. With no way to dig further into the message in the Home app (that I know of) it may be difficult to narrow down unless anyone has any other ideas.

An odd thing about the message (besides the fact that it isn't true, I'm not running any rogue server I know of) is that it "sticks" to the top of the Home app updates list: meaning, it's always there when I open the app (on multiple Android devices that can access our Google Home) with the updated time in the upper left, almost like it was "just" reported. I find this a little odd, though I suppose it could just be the behavior of such a message in the Home app (first time I've ever encountered something like this).

Any thoughts? Ideas? Help?

Thanks!

1 Recommended Answer

MichaelP
Diamond Product Expert
Diamond Product Expert

Hello @bananaslug79 

It sure sounds like that Midea device is acting as a DHCP server, given the timing. I have a bunch of TP-Link Kasa gear around here as well, and it's never had a problem. That, combined with the timing of the error showing up coinciding with the addition of the Midea device, makes me suspect it the most. I would investigate the settings for that device more closely to see if it has a feature that sounds like "DHCP". In any case, at this point, I'm not sure I'd trust a device that poorly implemented. If I had an old WiFi router, I'd consider connecting it via Ethernet to put that device on a dedicated network behind a firewall. 

The error message being "sticky" is an indication of the degree of concern about the issue – it's not something I would ignore.

View Recommended Answer in original post

7 REPLIES 7

MichaelP
Diamond Product Expert
Diamond Product Expert

Hello @bananaslug79 

It sure sounds like that Midea device is acting as a DHCP server, given the timing. I have a bunch of TP-Link Kasa gear around here as well, and it's never had a problem. That, combined with the timing of the error showing up coinciding with the addition of the Midea device, makes me suspect it the most. I would investigate the settings for that device more closely to see if it has a feature that sounds like "DHCP". In any case, at this point, I'm not sure I'd trust a device that poorly implemented. If I had an old WiFi router, I'd consider connecting it via Ethernet to put that device on a dedicated network behind a firewall. 

The error message being "sticky" is an indication of the degree of concern about the issue – it's not something I would ignore.

Well, as usual you're a stone cold genius, @MichaelP . I unplugged the Midea units today (for a different reason, but figured it would rule them out as culprits) and the sticky message went away. I'm quite happy with the Midea units as air conditioners, but the Wi-Fi clearly leaves something to be desired. I will be complaining loudly about these as far as their networking, thanks again.

Another question with your suggestion: supposing I did set up a spare router to isolate the Midea units, wouldn't Google WiFi see that as the exact symptom for what I'm trying to fix? (It vaguely starts to sound like a Richard Matheson story: He tried to remove the unknown server from his network, and in doing so he created the very thing he was trying to destroy...)

Maybe it's simpler than I'm thinking or I'm missing something easy here.

Incidentally, since powering off the Midea units, I've reenabled them and have not gotten the unknown server message. It's possible this was only during setup that Google Home flagged the bad behavior? I have one more unit left to install so may end up finding out for sure. Thanks.

MichaelP
Diamond Product Expert
Diamond Product Expert

So, the idea is that a a spare router would also be a NAT firewall. You'd connect it's external/WAN port to your Google WiFi internal network (the LAN port, or a port on a switched Ethernet network built from it). That way, that other router would be creating a new network inside your existing network. Since it's a firewall, nothing from your Google WiFi network would be able to connect directly to anything on it (without a port map), but devices on that network would still be able to connect out to the internet. I'm assuming your Midea systems only need an internet connection, and don't need to be on the same LAN segment to talk to a smart phone app – that's a big assumption, though, and if they do need that, my suggestion wouldn't work. All of that said, it sounds like they are working for you now without causing this issue, so as long as that continues to be the case, I wouldn't complicate your setup any more than you have to.

Jeff
Community Specialist
Community Specialist

Hey, bananaslug79.

It looks like MichaelP was able to drop in a lot of helpful info here. I just wanted to check in to see if you needed any more input on this or if you had everything you needed to move forward. If you're still needing some help, just let me know.

Thanks,

- Jeff

Thanks, Jeff. I've got everything squared away in here, you can close the thread.

Jeff
Community Specialist
Community Specialist

Thanks for the update, bananaslug79. I'm happy to hear things got worked out for you. If you need anything else going forward, feel free to open up a new discussion.

Thanks,

- Jeff