n_kerr

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-10-31
15:53
792 views
Time goes back and jumps ahead
We have approx 20 servers in our eDir tree. They are NW 6, SUSE 10,Windows 2008, and one Windows 2000. When I go into dsrepair on one of the NW 6 server and go into Time synchronization I can see that the time is not in sync. The time will jump back and forth between being -2 plus hours behind to +2 hours ahead. This is happening even on servers that do contain any replicas.
2 Replies


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-10-31
16:23
If all of the other servers change by the same amount at the same time,
I'd guess that "this" server (whichever you're on using ndsrepair) is the
one changing time. Is this box correct with regard to time, and how is it
getting its time synchronized? Is this a VM? If so, is the host reliable
with regard to time? What kind of time setup (single/primary/secondary)
do you have on the various systems?
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
I'd guess that "this" server (whichever you're on using ndsrepair) is the
one changing time. Is this box correct with regard to time, and how is it
getting its time synchronized? Is this a VM? If so, is the host reliable
with regard to time? What kind of time setup (single/primary/secondary)
do you have on the various systems?
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
ataubman

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-10-31
21:37
What is the exact timesync setup for all the NetWare servers?
What should be happening is one NW server be a SINGLE time server and all the others be SECONDARYs pointing to it by IP address. The SINGLE should in turn be pointing to a the same NTP source as all the SUSE and Windows servers are - it is vital that time comes from exactly one ultimate source for the whole tree, not diverse sources.
Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
What should be happening is one NW server be a SINGLE time server and all the others be SECONDARYs pointing to it by IP address. The SINGLE should in turn be pointing to a the same NTP source as all the SUSE and Windows servers are - it is vital that time comes from exactly one ultimate source for the whole tree, not diverse sources.
Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.