Force Time Sync on server

[Brianc2k]

I have a cluster of five NetWare 5 servers. One server is set up as primary time source (Admin server). The rest of the servers are secondary and take their time from the Admin server.

I have a server named DLT that is an hour off. It is not synchronized to the network. I have gone into DSRepair and tried to get it to sync and failed. I have also launched Monitor and under Server Parameters/Time moved RESET to on and let that run as well as Reset Start Flag on and let that run. This also failed.

From my primary time server Admin I have launched immediate synchronization and that still failed. I can't remember the switch I used last time on my MONITOR command that gave me additional options.

Any one have a suggestion as to what the Monitor switch is I use to load montitor that gives me more options, or what it is that I am missing to get DLT to resynchronize by taking time from my primary server? Any suggestions would be appreciated. Thanks.

 

[TheLad]

If the server is exactly off by one hour, I would assume that the server is not configured for the correct time zone. If you are UK based, you need to ensure that the server is in the GMT timezone rather than the BST timezone.

Anyway, from the console and to restart Timesync (and command an immediate synchronization), type:

SET TIMESYNC RESTART FLAG = ON

Once Tinesync has restarted, the flag automatically goes back to OFF -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[TheBoySmith]

on all your newtare servers check the autoexec.ncf.

Make= sure you don't have a timesync seeting that has on the line >=23 or <=23.

If you see that change it to LAST.

Reboot and time should show fine. Lee Smith
Xenon Network Services
Snr. Technical Support
LSmith@xenon-uk.co.uk

 

[Brianc2k]

The problem is not time zone. Nor a setting in any of the NCF's. Time synchronization worked fine and then one day this one server was out of step. The root of the problem was the servers hardware clock. When it was reinitializing once it did not receive it's time fast enough from the primary time server. So it took the system clock. Battery must be low as both date and time were way off.

Now I am really confused as when I key in &quot;time&quot; on the problem server it says Time synchronization is active but it also prompts that Time is not synchronized to the network.

Yet DSrepair time synchronization status prompts that all servers are synchronized. But in that same utility reporting active status the problem server shows 0 and does not reflect any time.

The key is to get this server synchronized to the network. But resetting flag, and reset within the Monitor utility or command prompt fails to get this accomplished.

Any suggestions how to establish time synchronization to active on this problem server?

 

[ladyhelp]

For time sync problems in NW 5.

Take a look at NW TID# 10060611 & 10023130.
Time sync fixes for NW 5x

 

[yvfwc]

At the console set the time to the correct time, ie: type &quot;set time 9:15:00 am pst&quot;, then see if the time synchronizes. It should synchronize in a minute or less. If it doesn't run dsrepair, unattended full repair. Check the error log after. If it does synchronize there is a setting somewhere in boot-up with a wrong time-zone or daylight-savings-time. You probably already have but, check that the time source is correct and other servers are set to the correct timesync type.

Cheers,
Mark ;-)

 

[Brianc2k]

I fixed the problem. Rather then let the server search for the primary time server I hard coded the primary time server's IP address. Now regardless what the hardware clock says it ignores everything internal. It draws its time from the primary time server just like it acquires map settings from NDS.

Setting was made in &quot;Time Sources&quot; section of Monitor/Server Parameters/Time. Make sure the problem server is set to &quot;secondary&quot; as a time source. Then just point it to the IP address of the primary time server in the time sources section.

This action fixed the problem. Thanks to everyone for their response and suggestions.

 

[TheLad]

That's how it should be set up, and by the reading of your original post I assumed that you had one Primary and the rest were Secondaries. You can also set this in SYS:SYSTEM\TIMESYNC.CFG -----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------

 

[Brianc2k]

TheLad: There are a couple of ways to set up time sync. The first is to key in an entry for your primary and then on each additional server key in secondary for type. This is the way it was set up and it was failing.

There is an additional key in area labeled as Time Sources. As I mentioned in my &quot;fixed response&quot; I also keyed in the IP for the primary server. Before it knew it was a secondary but would not find the primary on my LAN. The way it is set up now it now only knows it is a secondary but it also knows to get time from 10.26.11.104 which is also the specific IP address of the primary.

 

[TheLad]

I have always used SYS:SYSTEM\TIMESYNC.CFG without any problems. You mention that you were configuring your other servers as secondaries but they were not working - well they will not work unless they have a time source to look at - hence a primary or a reference.

Check out the following TIDS on how to configure Timesync:

http://www.novell.com/documentation/lg/nw5/docui/index.html#../usserver/time_enu/data/hdxp7z8o.html

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10061523.htm

- this one is exactly your problem

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10020147.htm

-----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------

 

[Brianc2k]

You need to read the thread. I have a primary. I had everything set up as a secondary. I posted the response that fixed the problem in case other people have problems. There are some instances where secondary servers do not read english. In those instances they have to have a specific IP address to look at rather than a server labeled as primary in the cluster.

 

[TheLad]

Brianc2k - you posted this thread because you had an issue. You are obviously not familiar with Timesync settings as Novell Standards state that you have to either have a Single, Primary/Secondary, or Reference/Primary/Secondary configuration - certainly not all Secondaries. Instead of suggesting I need to read properly, I suggest you read the TIDs I posted in my previous post which I posted there for your reference and for the reference of anyone who is less familiar with Timesync settings. For your info, I completed a Timesync project using a custom Reference/Primary/Seconary model on a network containing 165 NetWare server, 32 NT4 Servers and a selection of Unix/Aix servers. Trust me, we may have got our wires crossed but I know what I am on about. -----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------

 

[Guest_imported]

LMAO

 

[Brianc2k]

I acknowledge that you have set up vast networks. I have also. But this is the first time I had to hard code the Primary time server by its specific IP number. I am familiar with the TIDs. I also know that secondary servers take their time from the primary source. For over 5 years this system has run with secondary servers taking their time form the designated primary server in the tree.

The fix was not in the primary or secondary designations on the wan. The fix was not to disturb any settings but add the specific IP address of the Primary server in the set up screens.

I'm not sure where we got off track either. But the set up of primary and secondary sources was not the issue. The TIDs you referred to just cover primary, reference and secondary. All this was set up already. The key was hard coding the IP address of the Primary source. A CNE friend mentioned a Novell incident that was opened and solved by hard coding.

That is also why I posted the hard code fix. I posted it for people who run the circles of Primary, Secondary and Reference but still have problems. If I offended you by suggesting you read the thread I am truely sorry. But primary secondary settings were not the problem. They were set up correctly as I tried to explain. Some how I needed to get beyond that.

Thanks again for your suggestions. Enjoy a safe and happy holiday.