Duet2-Ethernet v1.04c Can't connect to dwc

[ReVeRb]

Hi these are the error messages I get when I try to connect to DWC for the first time:

Connection delay(too long)
DNS_PROBE_FINISHED_NXDOMAIN

I'm connected to a hub/switch and I manually set my IP with the command M552 Px.x.x.x, through YAT and get a positive feedback (enabled).

I tried to connect according to the instructions (launch a web browser and enter the IP address, or enter http://duettest.local/ ). Both fail, nothing start, I just get a message "impossible to connect, blah blah"

Any ideas why it does not work ? I'm using this same hardware model as the link I provided, which is connected to my rooter and all my PC are connected to that switch. The seller told me it should work.

https://www.amazon.com/Ethernet-Splitter-Optimization-Unmanaged-TL-SG105/dp/B00A128S24/ref=sr_1_2?dchild=1&keywords=switch+tp+link&qid=1623007722&sr=8-2

[SIam]

@carl i don't think that the switch is the problem. Please post your config.g file and the result of M122

[ReVeRb]

@siam --EDITED--

here is the M122 result:

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet Ethernet 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6J1FJ-3SJ6L-T84LK
Used output buffers: 1 of 24 (2 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 92084 of which 20 recycled
Exception stack ram used: 256
Never used ram: 10732
Tasks: NETWORK(ready,1200) HEAT(blocked,1456) MAIN(running,2712) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 01:04:32 ago, cause: power up
Last software reset details not available
Error status: 0
MCU temperature: min 35.0, current 38.2, max 38.6
Supply voltage: min 1.5, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 55.24ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.3ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "m122" in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.79ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
Interface state active, link 100Mbps full duplex
ok

here is the config.g file

config.g

[ReVeRb]

I ended up installing CuteCom on my linux Desktop and followed the instruction. Configured the Duet IP to DHCP, which didn't worked from windows(I don't know why).
With linux, it worked like a charm.

Now I can connect to the DWC from the linux Desktop, windows laptop or via IPad Wifi.