NTP test - possible reasons for BAD status

[JuergenF]

Dear all,

I've a problem with a NTP test.
We use an internal Timeserver. (in the local LAN)

Sometimes the test goes to BAD for several cycles and nothing is displayed in the Reply field.
What can be possible reasons for that ?
- Server not available (no connection possible) ? - But Server is working fine. Ping works
- Server does not respond to NTP request within Timeout periode ?
- Other reasons ?

What can I do to troubleshoot that ?

Many thanks

Method = NTP
;--- Common properties ---
Title = NTP: timeserver.de.dcc.emea
Comment = NTP: timeserver.de.dcc.emea
RelatedURL =
ScheduleMode= Regular
Schedule = 7 Days, 24 Hours
Interval = 900
Alerts = Gen.HTML report-Retest-Alarm after 10
ReverseAlert= No
UnknownIsBad= No
UseCommonLog= Yes
PrivLogMode = Default
CommLogMode = Default
;--- Test specific properties ---
Server = timeserver.de.dcc.emea
Port = 123
Timeout = 5
Retries = 3
DisplayMode = DifferenceInTime
DifferenceLimit = 10

[KS-Soft]

Empty Reply field and "bad" Status means either
1) HostMonitor received incomplete reply
2) server replied with "leap indicator" = 3 (alarm condition)
3) server replied with "time" = 0
http://www.rfc-archive.org/getrfc.php?rfc=1361

Regards
Alex

[JuergenF]

Empty Reply field and "bad" Status means either
1) HostMonitor received incomplete reply
2) server replied with "leap indicator" = 3 (alarm condition)
3) server replied with "time" = 0
http://www.rfc-archive.org/getrfc.php?rfc=1361

Regards
Alex

Many thanks Alex,

any hints or logfiles to find out, what exactly is the reason ?

[KS-Soft]

Sorry, no such logs. I doubt about 1st reason (incomplete reply). Most likely server sets alarm condition and/or time=0 bytes.

Regards
Alex