We are having difficulty in maintaining sychronization between the

Novell 4.11 server time and our Win98 workstations. As we run our

timesheet program from Arev3.11 this is creating a problem with

timesheet abuse. We downloaded a time standard app for win98 that

sets the exact time, but have found the workstations begin showing

discrepancies within a few days. Is there a way to force Arev running at the workstations to sync with the server time only, rather than the

workstation clock? TIA for your help, Jim

Jim,

Under Windows 95, I SUSPEN EXIT and perform the following command before doing time sensitive tasks:

NET TIME
/S /Y

This will force the workstation clock to be set to the server clock specified in

HTH,

Matt Sorrell

msorrell@movgal.com

When I try that command I get the error message:

Error 53: The computer name specified in the network path cannot be located.

Make sure you are specifying the computer name correctly, or try again later

when the remote computer is available.

SYSTIME, however, works.

If you use SYSTIME from a client connected to multiple servers, make sure you specify which server you want to synchronize to, i.e.:

SYSTIME servername

Without specifying the server, you synchronize to whichever one is mapped to the default DOS directory. If the default is a local drive, it should synchronize to the preferred server (if you know which one that is).

At this point, he might as well just add it into the login script so the workstation's almost always synchronised.

akaplan@sprezzatura.com

Sprezzatura Group

Our servers are synchronized with each other. I was more interested in why I was getting the error message. I did verify that I was indeed attached to the server I was trying to use. I did notice that there was a reference to a time server. What is that?

The synctime() subroutine from my website does what you want. A synctime.com version is also included and the source is included for Y2K purposes.

Steve

steve@state-of-the-art.com.au

We had trouble with time keeping sync on the WIN 95 work stations as well. What we found was we had to change the time zone within the control panel- time/date properties. We are in the Indiana (East)time zone but now we use (GMT) Monrovia/Casablanca time zone. This only occurs with the Novell Client from what we have found.

Tom Tadros

TOMINFW@AOL.COM

RE: Time servers

There are several Internet protocols for requesting and sending time information, thus a server can be setup up to send out this information for systems that either don't have a clock or for synchronizing clocks. Two common protocols are SNTP (RFC 1769), or

The Time protocol (RFC 868).

Most universities have Internet Time Servers as well as the atomic clocks in Boulder, Colorado and Washington, DC.

Check www.tucows.com under time synchronizers if you want to set your PC clock to one of these servers.

Kudos to Steve for the excellent solution. I plugged it into the

window pre-process and also into the field prompt hooks. Works like

a charm. Only a Rev or Novell programmer could mess with the timesheets now! Jim Dierking

View this thread on the forum...