14150.883.17 problems for wired connections

[RudiC]

For some reason, since this version, no wired device can't access a specific login page with the dansh tax system. They use an url that looks like nemlog-in.dk

If a device on the same "network" is using a WIFI connection, there is no problem.

If the device with a wired connection, changes to a wifi connection, there is no problem.

My setup is pretty simple. I have 2 nest devices. One router and one mesh. The router is connected directly to my fiber device and on the other port on the router, to my netgear switch. The netgear switch then have all the wired connections. This has been working for years without any problems. But since the last version I'm getting this very odd error, when trying to log in to the danish tax system.  But as I said, only when it's wired.

The nest is running in bridge mode, which it's supposed to do.

[GabrielaG]

Hi RudiC,

Thanks for reaching out to the community. I'm sorry to hear you're having problems with wired connections getting an odd error when trying to log in to the Danish tax system. I'm happy to assist you right now.

To get a better understanding of the situation, please help me out by answering the following questions:

• What type of Nest WiFi devices do you have?

• When did the issue start?

• What is the color light status on your Nest WiFi router?

• Have you done some troubleshooting steps? If so, can you please list them?

Any additional details you can provide will be helpful.

Regards,

Gabriela

[RudiC]

Hi,

I'm not sure what you mean, when you say which devices I have. I thought I was very clear on that. The software version in the topic is only for that hardware version of the nest series.

The problem startet sometime after the release of that version.

Colors are normal like they always are "WHITE".

I did a full reset of the wifi, which brought me back to configuring everything (default). This seemed to fix the problem. I found the solution on social media. I do find that resetting everything is a pretty big step to make, since I have to configure everything again from scratch, just to fix this weird bug. So some investigation by the software developers on this latest version would be in order.