ntpdate[3527]: no server suitable for synchronization found

Status
Not open for further replies.
Veek M

Veek M

Inactive
Discoverer
-dv output
no -dv

Why? I've checked
serverfault.com

ntpdate -d Server dropped Strata too high

I cannot sync with a NTP source thats coming from an internal router/firewall. Anyone help ? ntppdate -d 192.168.92.82 6 Jun 11:57:30 ntpdate[5011]: ntpdate 4.1.2@1.892 Tue Feb 24 06:32:26 EST ...
serverfault.com serverfault.com
i am receiving pkts and the offset is computed BUT WHY isn't the clock set after the 1st run because on the 2nd run using -dv I get the same offset - it should reduce
 
May be totally unrelated but my windows PCs are not syncing NTP time with either time.windows.com or time.nist.gov and I have tried various troubleshooting steps off the net and the only thing I can think of is that my ISP (BSNL FTTH in Pune) has something wrong.
 
  • Like
Reactions: Veek M
fixed with -u unprivileged port so yeah could be BSNL blocking it (most certainly is - silly idiots)
 
are you also on BSNL broadband?

looks like yeah, windows 10 SNTP protocol client is opening local port 123 as well as server destination port 123. and I think BSNL is blocking local port 123 (thinking we are trying to run a server on UDP port 123).

NTP sync is working on linux distros for me and also downloaded a windows program called "NetTime" which also does NTP and that program is working.

Checked with WireShark - NetTime tool is opening a unprivileged port around 60,000 range while w32time service is opening local port 123 and that is what is likely being blocked by BSNL.
 
  • Like
Reactions: Veek M
Status
Not open for further replies.
Top Bottom