Networks

General discussion

Changing time on 4.10 server safe ??

Hello, I have a 4.10 Netware Server and the time is about 10 minutes fast. Whenever any of the clients correct their time and reboot, it goes right back since it's being mapped to a Netware drive. I would like to correct the time, but have been told that this could cause big problems. Is this true ??

All Comments

Changing time on 4.10 server safe ??

It should be okay to set the server time to the correct time. If the server's new time is in the past and NDS has had any object updated, you will see "issuing synthetic time" messages on the console. This is okay it is NDSs way of ensuring that objects are not overwritten with bad or old information. Do it on a Friday evening and by Monday morning the error message sould be gone. To keep this from happening, set the server to get its time from a trusted source. Read Novell's articles about time synch designs and such.

Changing time on 4.10 server safe ??

Just adding to the previous answer: you should see the server's time and NDS' time separate. The server will follow the clock, while if you change that clock, NDS will adapt its own "clock" to go a little faster or slower to catch up. When going abit slower, the "Synthetic Time" message appears.Connecting to an external source, either via IP or via an antenna, is indeed a good suggestion.

Changing time on 4.10 server safe ??

Adding to what's already been said; every program could be effected by time. Your time lag is not large so I would have 2 suggestions for you. Pick a time when service to clients will not be an issue. Down the server and set the hardware clock back 10 minutes and then turn off the hardware. Wait 11 minutes then start the up / reboot the server. All issues should be resolved and no program will be effected. We solved this problem by using Timesync.nlm and connecting to 2 atomic clocks and auto synchronization is held to within 2000 milliseconds.

Changing time on 4.10 server safe ??

If you want to do it the ugly way, you could change the BIOS clock, and restart the server. You WILL get Synthetic Time warning messages, but after a short while (les than a day), they will go away. I wouldn't recommend this method of changing it,but it will work, especially if time is only out by a few minuites.

Either way, give the servers time to notice the change. DO NOT mess with the time for at least 3-5 hours after you make an adjustment. Preferably a day.

If they every get totally messed up, you can declare a new epoch in DSREPAIR. But you REALLY want to avoid it. Scheduling an adjustment, and then allowing it a few hours to happen is the recommended method of correcting it. It will work perfectly, and it is quite normal for the server's time to 'drift'.

Start or search

Create a new discussion

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

Post type

Subject title

Topic Tags

Select up to 3 tags (1 tag required)

Cloud

Piracy

Security

Apple

Microsoft

IT Employment

Google

Open Source

Mobility

Social Enterprise

Community

Smartphones

Operating Systems

Windows

Mac

Malware

Tablets

Networking

Browser

Hardware

Software

Web Developerment

Linux

Off Topic

Message Body

Track this discussion and email me when there are updates

Please note: Do not post advertisements, offensive material, profanity, or personal attacks. Please remember to be considerate of other members. If you're new to the TechRepublic Forums, please read our TechRepublic Forums FAQ. All submitted content is subject to our Terms Of Use.