Dear @luxor84,

luxor84 wrote

I have tried for many months, but unsuccessfully to set the NTP server.

No matter the configuration, the IP of the server.... the log says: 

Sntp

WARNING

Time renew failed, connecting NTP server timeout.

The issue may be caused by high network latency.

To locate the problem, you may capture the packets via Wireshark to check the NTP interaction.

About how to capture packets, you may refer to the guide below.

How to capture packets using Wireshark on SMB router

Dear @luxor84,

luxor84 wrote

The IP of the NTP server is always on the destination but I no see any traffic as a source... Is it the reason why there is in the log "Time renew failed, connecting NTP server timeout"?

It seems that the router didn't receive a response from the NTP Server.

Have you tried the Google Public NTP like time.google.com? Would it make any difference?

Dear @luxor84,

luxor84 wrote

What I find a little bit strange is the source port from the ER605... Is it normal that it changes like that for the NTP protocol?

I think it's normal as the source port is random.

Do you have other devices that can be configured to obtain the time from NTP Server?

You may check if your ISP blocks the NTP port so that the router cannot renew time from NTP Server in your network.

Dear @luxor84,

luxor84 wrote

The ISP has confirmed that IS NOT blocking any port.

 

As a demonstration of it, my Mac Mini inside the network is able to get the NTP answer from the NTP Apple server! So the ER605 sends the request from the Mac Mini to the Apple server and he receives the answer!

The issue you are experiencing sounds unusual, I'd like to escalate your case to the TP-Link support team for further investigation.

They will reach you via your registered email address shortly, please pay attention to your email box later.

Once the issue is addressed or resolved, I'd encourage you to share it with the community.

Thank you so much for your cooperation and support!