Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Repeated failure to retrieve time from NTP server
#15
OK Mauro. I can test whenever you wish. Use my normal email
for any attachments.

As for timing, in checking the Diagnostic Log, when Sync does work, the "good" response appears in the log
within the same second as the request (reply < 1000millisecs?). When there is no response (error messages),
the log shows no return during 5 seconds. I have never seen any reports between these two extreme values.

Now, although I am not familiar with current Internet architecture, I have done some more research........
Generally, Internet connection/speed here is very good. Malta is physically linked by fiberoptic cables to Palermo.
Looking at tracert, I can see we are in fact always being directed to interoute.net in Palermo (84.233.225.121).
I would then expect that data would then be switched to an internal Italian node in Palermo for onward
routing to MIX (in Milano) and distribution in north Italy.
However the tracer shows that instead of an internal Italian node in Palermo, the trace is actually routed
to 89.202.146.97 which is in NORWAY !!
The requested domain name shown in tracert (xe-2-3-0-0.mil-cal-score-1-re0.interoute.net) apparently
does not exist (according to whois), so I assume that the default node chosen by interoute.net is the Norwegian one.
Somehow, the trace makes its way back to MIX and gets to Torino.
This unusual route could have some specific security restrictions which allow the tracer, but not real data.

If my reasoning is correct, this might explain the problem, and could be due to an incorrect routing table entry in Palermo.
Does that seem likely to you?
If you agree, I can ask my ISP to get GO Datastream (the Malta International Internet gateway) to investigate.

73 Robin
Reply


Messages In This Thread

Forum Jump:


Users browsing this thread: 7 Guest(s)