@elmoret
M552 S0
ok<LF>
M552
Network is disabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0<LF>ok<LF>

@phaedrux M122
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet Ethernet 1.02 or later + DueX5<LF>Board ID: 0JD0M-9P6B2-NJ4S8-6J9FD-3S06R-9B62M<LF>Used output buffers: 1 of 24 (12 max)<LF>=== RTOS ===<LF>Static ram: 23876<LF>Dynamic ram: 69516 of which 0 recycled<LF>Never used RAM 21024, free system stack 193 words<LF>Tasks: NETWORK(ready,6.2%,565) HEAT(suspended,0.0%,386) DUEX(notifyWait,0.0%,24) MAIN(running,93.8%,439) IDLE(ready,0.0%,29), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 02:06:11 ago, cause: reset button or watchdog<LF>Last software reset at 2022-03-08 15:07, reason: User, GCodes spinning, available RAM 18380, slot 2<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>Step timer max interval 0<LF>MCU temperature: min 39.3, current 39.3, max 39.3<LF>Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: [Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.]
M552
Network is disabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0<LF>ok<LF>

@t3p3tony Everything works on diagnostics but the ethernet connection cannot be established

@t3p3tony The original WIFI board didn't work in our environment therefore we needed to change to a Ethernet board which worked fine for about 6 weeks and than lost the connection with our server which we have checked and tested that is working properly. For what I see the Duet 2 Ethernet board is defective.

@elmoret The original board was a Wifi board. We needed an Ethernet one which works better for our structure.

after less than 2 months running through this board our Modix 180x it stopped working. Tried unsuccessfully troubleshooting by changing cable and using verified working ports. Looks like board is unresponsive.
Please help