Re: Servers just doen't work (after following the troubleshooting page)

Danny Mayer wrote: 
Per Hedeland wrote:


Well, if you've not munged the output *selectively* here, I believe it
shows that you've run into the bug that Danny mentioned recently: The
client sends a query to ntp2.<mydomain>, but gets the response from
server2.<mydomain>, i.e. presumably a different IP address on the same
host. The client will not (and should not) be interested in responses
coming from what it sees as "someone else". The same effect will apply
to the intra-server/peer queries.


No, that's not it at all. If ntpq -p is showing the two servers listed
(there should always be more than two, BTW) then it's receiving packets
from those servers. The fact that they are both showing stratum 16 on
the scoreboard indicates that neither are able to serve a valid time
because they themselves are not synchronized.


From the original post:

[root@server1 /]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+ntp-0.gw.uiuc.e truechimer.cso.  2 -   55 1024  377   26.019    1.585   2.253
*ntp3.tamu.edu   ntp1.tamu.edu    2 -   20 1024  377   44.892    1.253   1.445
+cisco1-mhk.kans navobs1.wustl.e  2 -   57 1024  377   47.829    3.943   2.297
 ntp2.<mydomain> 0.0.0.0         16 u    -  256    0    0.000    0.000 4000.00


[root@server2 /]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*ntp-1.gw.uiuc.e truechimer.cso.  2 u  146 1024  377   96.335  -166.48  64.986
+ntp3.tamu.edu   ntp1.tamu.edu    2 u  268 1024  377   68.509  -129.28  30.480
+cisco1-mhk.kans navobs1.wustl.e  2 u  229 1024  377   44.214  -126.14  33.813
 ntp1.<mydomain> 0.0.0.0         16 u    -  256    0    0.000    0.000 4000.00

Looks synchronized to me.
.

Relevant Pages

  • Re: Servers just doent work (after following the troubleshooting page)
    ... shows that you've run into the bug that Danny mentioned recently: The client sends a query to ntp2., but gets the response from server2., i.e. presumably a different IP address on the same host. ... The client will not be interested in responses coming from what it sees as "someone else". ...
    (comp.protocols.time.ntp)
  • Re: Servers just doent work (after following the troubleshooting page)
    ... shows that you've run into the bug that Danny mentioned recently: The client sends a query to ntp2., but gets the response from server2., i.e. presumably a different IP address on the same host. ... The client will not be interested in responses coming from what it sees as "someone else". ...
    (comp.protocols.time.ntp)
  • Re: No DSN Server Reply
    ... Make sure the primary DNS server ... > my SBS2003 set to use my ISP's DNS server and DHCP for all my client ... > query again and we do get a response from the DNS server. ...
    (microsoft.public.windows.server.sbs)
  • No DNS Server Reply
    ... my SBS2003 set to use my ISP's DNS server and DHCP for all my client ... I did some network monitoring and I can see the query going from the ... then the server to the ISP DNS server. ... retry of the query and we do get a response from the DNS server. ...
    (microsoft.public.windows.server.sbs)
  • No DSN Server Reply
    ... my SBS2003 set to use my ISP's DNS server and DHCP for all my client ... I did some network monitoring and I can see the query going from the ... then the server to the ISP DNS server. ... query again and we do get a response from the DNS server. ...
    (microsoft.public.windows.server.sbs)