Fixed - Intermittent connection in eno1 with eno2 working correctly

Hi, I've been having an issue with the IOT2050, I got my IOT connected to a PLC network on the port P1 with a static IP and P2 tis connected to a router with internet with a dynamic IP.

My problem is that while the connection to the internet is working as intended and stable, the connection to the PLC network is having intermittence issues, it connects for about 3 to 4 minutes and then disconnect from 7 to 10 minutes, then it connects again and drops again and again.

I've still haven't discarded this to be an issue with the ethernet cable, so I've already commissioned another to discard the problem, but one of the question that I have is:

¿If the cable is defective, would it lead to intermittence in the connection? because to my understanding, it would simply not connect altogether.

If anybody had a similar issue, I would appreciate any tip you may have, it may very well be a configuration issue, I've attached a screenshot from the "edit connection" menu from the "iot2050setup" command.

Also not seen om the screenshot, the options "Automatically connect" and "Available to all users" are marked.

 Thank you for your time reading this.

Found the solution: had to change the IP4 configuration from "Automatic" to "Manual" and eno1 began working properly, I still find this weird, because when I used the “Manual” config on my office it returned the error "Error: send ENETUNREACH 255.255.255.255:44818" and it was solved by using the “Automatic” config.

However, the IOT began working differently on my client's network and now this config fixes it instead of breaking it.

I also tried to manually activate the connection during one of these connection-down cycles and got this message.

What does NetworkManager report during those phases (journalctl -u NetworkManager)? Does the kernel report any link up/down changes (dmesg)?