08.08.2020»»суббота

Ntpdate No Server Suitable For Synchronization Found Macos

08.08.2020
Ntpdate No Server Suitable For Synchronization Found Macos Average ratng: 8,1/10 2503 votes
  • When using the command ntpdate to set the date and time via NTP, an error 'no server suitable for synchronization found' is returned.
  • Apr 17, 2018 Symptom: Messages log file will print multiple errors like the following every minute: Nov 18 11:25:01 user 4 ntpRunningStatus.sh: Response from 'ntpdate -q': server x.x.x.x, stratum 3, offset 0.000000, delay 0.8 Nov 11:25:01 ntpdate9568: no server suitable for synchronization found.
  • $ sudo ntpdate ntp.ubuntu.com 4 Mar 13:06:16 ntpdate4361: no server suitable for synchronization found Even with the -u option, which tells ntpdate to use an unprivileged port for syncing (instead of port 123) which is certainly not blocked from my work place.
  1. Ntpdate No Server Suitable For Synchronization Found Macos X
Ntpdate No Server Suitable For Synchronization Found Macos
Followed your instructions, here's the output:
Looking for host time.apple.com and service ntp
host found : time2.apple.com
Looking for host time.apple.com and service ntp
host found : time.apple.com
13 Apr 18:18:42 ntpdate[229]: no server suitable for
synchronization found

How do you connect to the Internet?
From looking around the Internet, it sounds like your problem is a blocked port. Make sure the firewall is turned off on your computer. And make sure that if you have a router/firewall for Internet sharing, that its firewall is allowing UDP packets through. It should connect to the time server (at Apple) on port 123. The connection back will be to a higher number port, it was around 55900 on my iMac just now.
Here's how I figured how which port: I opened Terminal again, but this time opened two windows. I the first one, I typed this:
<pre>sudo tcpdump -i en0 port 123</pre>Again, I had to give my admin password. I get a couple of lines, then it just sits and waits:
<pre>tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on en0, link-type EN10MB (Ethernet), capture size 96 bytes</pre>Then, I switched to another Terminal window and entered a slightly different command:
<pre>ntpdate -d -q time.apple.com</pre>The options here are this: -d gives enhanced debug output and -q just queries the server but doesn't actually set the time (so I don't need to use sudo). When I run that command, I get a bunch of lines in the other window where tcpdump is waiting:
<pre>19:29:26.551255 IP iMacName.local.55915 > time0.apple.com.ntp: NTPv4, Client, length 48
19:29:26.590860 IP time0.apple.com.ntp > iMacName.local.55915: NTPv4, Server, length 48
19:29:26.591003 IP iMacName.local.55915 > time0.apple.com.ntp: NTPv4, Client, length 48
19:29:26.628405 IP time0.apple.com.ntp > iMacName.local.55915: NTPv4, Server, length 48
19:29:26.628509 IP iMacName.local.55915 > time0.apple.com.ntp: NTPv4, Client, length 48
19:29:26.661951 IP time0.apple.com.ntp > iMacName.local.55915: NTPv4, Server, length 48
19:29:26.662055 IP iMacName.local.55915 > time0.apple.com.ntp: NTPv4, Client, length 48
19:29:26.697510 IP time0.apple.com.ntp > iMacName.local.55915: NTPv4, Server, length 48
19:29:26.751198 IP iMacName.local.55915 > time0.apple.com.ntp: NTPv4, Client, length 48
19:29:26.786127 IP time0.apple.com.ntp > iMacName.local.55915: NTPv4, Server, length 48
19:29:27.751223 IP iMacName.local.55915 > time0.apple.com.ntp: NTPv4, Client, length 48
19:29:27.784616 IP time0.apple.com.ntp > iMacName.local.55915: NTPv4, Server, length 48
19:29:28.751239 IP iMacName.local.55915 > time0.apple.com.ntp: NTPv4, Client, length 48
19:29:28.785549 IP time0.apple.com.ntp > iMacName.local.55915: NTPv4, Server, length 48
19:29:29.751219 IP iMacName.local.55915 > time0.apple.com.ntp: NTPv4, Client, length 48
19:29:29.784047 IP time0.apple.com.ntp > iMacName.local.55915: NTPv4, Server, length 48</pre>You can see in that example that it actually connected to the NTP server at apple on the NTP port time0.apple.com.ntp. But it connected back to my computer on port 55915: iMacName.local.55915. It would be interesting to see what your computer says. (Just rename the local computer's name if you want, but make sure the port number is still there).
To stop tcpdump waiting for network traffic, just hit the control-'c' key combination.
Finally, one more suggestion, try adding a longer timeout to the ntpdate command you tried earlier:
<pre>sudo ntpdate -t 4 time.apple.com</pre>The default timeout on OS X is 1 second, so maybe setting to a higher value will help.
charlie

Ntpdate No Server Suitable For Synchronization Found Macos X

I've got a system that is not running ntpd on which I'm attempting to update the clock using ntpdate. The system is an appliance that appears to be CentOS 6 based. When I run ntpdate 0.pool.ntp.org, I get: 8 Sep 17:52:05 ntpdate7445: no server suitable for synchronization found However, when I do ntpdate -d 0.pool.ntp.org, I get.

Broadcom 43xx driver for mac os x. Jan 22, 2018  I read and recognized that the latest Broadcom 802.11ac drivers for my MacBook Air (early 2014) are making wlan very slow (I think I got that driver update automatically through Windows Update). I had around only 5 MB/s (and jumping up and down a lot) when copying files over wlan.

Safari for mac os x 10.5 8 free download Insert your Mac OS X 10.5 DVD and try performing a custom installation of it; if that component doesn’t appear in the list, use Pacifist to extract it manually. In either case, run the Mac OS X 10.5.8 combo updater as well as all applicable Safari and security updates afterwards.