NTP Client triggers max permanent peer count message

Hi, I have hAP ax^3 with ROS 7.16.1. Enabling NTP client in router affects warning message in logs:

WARNING: max permanent peer count reached

I tried few common NTP servers as time.google.com, pool.ntp.org, time.apple.com, time.windows.com but it is always same warning message appears in logs. Deactivation of NTP client resolve the issue.
Any clue how to solve the issue?

Not sure, but the following might help.

You often need to src-nat the port from your ntp-client (So it looks like it’s coming from a high port rather than port 123)
As ISP’s, ntp servers will often block ntp from port 123, (which Mikrotik’s ntp client uses).

Something like:

/ip firewall nat
add action=src-nat chain=srcnat out-interface={YOURWAN} protocol=udp src-port=123 to-ports=12300-12400

How many NTP servers are configured in /system/ntp/client? I don’t know if there’s a limit in RouterOS’s NTP implementation, but I don’t think more than 3 quality servers are necessary (3 is kind of a minimum to form a meaningful quorum).

SOLVED!
Reduced NTP Server to one (1).

My ROS installations generally have 2 servers configured and up to 7.18.2 I never saw such error logged.