>>> In article <[EMAIL PROTECTED]>, "Richard B. Gilbert" <[EMAIL PROTECTED]>
>>> writes:
Richard> Danny Mayer wrote:
>> Somebody wrote:
>>> Before starting 'ntpd' use 'ntpdate' at the clients to nullify this
>>> initial high offset.
>> No, just add -g to the ntpd startup command line. There is n
Danny Mayer wrote:
> venu gopal wrote:
>
>>Hi,
>>
>>As per the ntpq output given, the initial offset is too high (in bold
>>below).
>>
>>ntpq> rv 12516
>>status=9014 reach, conf, 1 event, event_reach,
>>srcadr=MAIL, srcport=123, dstadr=192.168.4.18, dstport=123, leap=00,
>>stratum=2, precision=-6,
venu gopal wrote:
> Hi,
>
> As per the ntpq output given, the initial offset is too high (in bold
> below).
>
> ntpq> rv 12516
> status=9014 reach, conf, 1 event, event_reach,
> srcadr=MAIL, srcport=123, dstadr=192.168.4.18, dstport=123, leap=00,
> stratum=2, precision=-6, rootdelay=31.250, rootd
noosh wrote:
> how can i synchronize my server. i have set the server(anothor PC as a
> server) to Local clock but and set my time if pc to GMT, but again
> nothing is synchronized
The PC should be set to show the correct time for the timezone for which
you have configured it. I suspect you hav
noosh wrote:
> ntpq> rv 12516
> status=9014 reach, conf, 1 event, event_reach,
> srcadr=MAIL, srcport=123, dstadr=192.168.4.18, dstport=123, leap=00,
> stratum=2, precision=-6, rootdelay=31.250, rootdispersion=10932.175,
stratum 2 is inconsistent with your claim that the server is
synchronized to
noosh wrote:
> Hi
>
> i have a GPS which is connected to the PC1 via serial port , PC1 can
> synchronize itself with GPS, now i want other PCs be synchronized with
> PC1 by LAN. i have no restriction on ntp.conf.but they doesn't
> synchronzie with PC1.
> ntp.conf- on cl
Noosh,
You need to set the time on the client to within 1000s
of the time on the server before you start NTP
on the client.
This is documented here:
http://www.eecis.udel.edu/~mills/ntp/html/ntpd.html#op
(How NTP Operates, second paragraph).
BTW: Did you get NTP running with your Hopf 6842?
Are
Hi,
As per the ntpq output given, the initial offset is too high (in bold
below).
ntpq> rv 12516
status=9014 reach, conf, 1 event, event_reach,
srcadr=MAIL, srcport=123, dstadr=192.168.4.18, dstport=123, leap=00,
stratum=2, precision=-6, rootdelay=31.250, rootdispersion=10932.175,
refid=DC1, reac
On Feb 12, 11:43 am, [EMAIL PROTECTED] wrote:
> Noosh,
>
> Your server is not synchronised. You can see that from the ntpq> ass
> printout: condition=reject.
> Also, the ntpq> pe printout will show an asterisk in the left column
> when NTP is synchronised.
> There's no asterisk, so NTP is not synch
Noosh,
Your server is not synchronised. You can see that from the ntpq> ass
printout: condition=reject.
Also, the ntpq> pe printout will show an asterisk in the left column
when NTP is synchronised.
There's no asterisk, so NTP is not synchronised.
You have an offset of around 3,600,000 millisecon
Hi
i have a GPS which is connected to the PC1 via serial port , PC1 can
synchronize itself with GPS, now i want other PCs be synchronized with
PC1 by LAN. i have no restriction on ntp.conf.but they doesn't
synchronzie with PC1.
ntp.conf- on client
server 192.168.5.30 pr
11 matches
Mail list logo
