[comp.protocols.time.ntp] Problem with wwvb.isi.edu

sysmanager@meevax.meediv.lanl.gov (WHITFILL_JIM_A) (03/04/91)

Does anyone know what has been wrong with wwvb.isi.edu that past few days?
As you can see below, it is WAAAAYYY off. 

---------------------------------------------------------------------------
Jim A. Whitfill    Mechanical & Electronic Eng. Division     (505) 667-9282
whitfill@meediv.lanl.gov       		     Los Alamos National Laboratory

sysmanager@meevax.meediv.lanl.gov (WHITFILL_JIM_A) (03/04/91)

In article <16614@lanl.gov>, sysmanager@meevax.meediv.lanl.gov (WHITFILL_JIM_A) writes...
>Does anyone know what has been wrong with wwvb.isi.edu that past few days?
>As you can see below, it is WAAAAYYY off. 
> 

I forgot to include the data in the previous posting.

Connected to NETCONTROL server on "LOCALHOST"
< meevax.meediv.lanl.gov Network Control 2.2(6) at Mon 4-Mar-91 8:05AM-MST
< NTP parameters:
<     Set Threshold                  =    0.512
<     Clock Disruption Way Too Big   = 4000.000
< 
< NTP peers:
<   Remote Address      Stratum Poll Reach    Delay   Offset    Disp
< =======================================================================
< + 192.43.244.9             1   64  017     0.121    0.004    0.025
< * 132.249.16.1             1   64  017     0.096    0.005    0.002
< . 128.9.2.129              1   64  017     0.072 -9146.989    0.007
< + 128.4.0.5                1   64  016     0.162    0.022    0.002
< + 192.52.70.3              2   64  016     0.023    0.024    0.008
< - 128.165.4.2              3   64  017     0.027   -0.002    0.005
< - 128.165.4.1              3   64  017     0.027    0.007    0.007

---------------------------------------------------------------------------
Jim A. Whitfill    Mechanical & Electronic Eng. Division     (505) 667-9282
whitfill@meediv.lanl.gov       		     Los Alamos National Laboratory

Mills@udel.edu (03/04/91)

Jim,

I see the warp here, too. This may be more of what was bugging it last
week. Steve Casner, its keeper, and Tom Denahur at Spectracom are aware
of the poblem. I suspect the latter will move rather quickly, since
the clock has recently been modified to align with their new product
NetClock/2. 

Dave