Re: Time sync problems

On 2006-08-09 15:28:58 +0100, "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> said:



In news:4jtn2dF9d78uU1@xxxxxxxxxxxxxx,
Martin Smith <nospam.redsmartie@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> typed:
I have a problem accessing network resources. When I try to access a
computer on the network from other computers I get an error message
that ends "This server's clock is not synchronized with the primary
domain controller's clock".

I have had a similar problem to this when one of the users changed
their clients clock to do some month end accounting and couldn't
access any network resources until she manually returned her clock to
the correct time.

How can I resolve this. Is there a sync that is failing and whet
should be the typical configuration.

If anyone can quickly push me in the right direction it would be
appreciated as I'm currently in the office in question.

What is the client workstation OS? Win2k and XP should sync with the time server (generally your SBS box) automatically. Do you see errors in the event log? How about on the server? On the PC that you can't reach over the network, log in as an admin and go to a command line, and type in net time <enter> to see what it says. You can also do net time \\servername /set

Users shouldn't be able to change the time. They shouldn't have local admin rights anyway (and then they can't change the time). If this accounting program can't deal with its own internal time/clock, get another one or put this user on a standalone computer that isn't joined to the domain.

The clients are XP and they were installed from new at the same time as the SBS server. Any configuration is as they were out of the box and following any changes that SBS made when introducing the computer/user to the network.

I did a few commands on reading a number of support articles in the knowledge base and got a message that there was no time server. I found Windows Time on the server that was disabled. I enabled it and did the commands again which sync'd up the client time and solved the immediate problem.

Should this service be enabled? The clients aren't being sync'd on boot previously. Will they now with this service enabled or should I add the sync command to a login script?

As for local admin rights, this is something that the SBS client connect did when setting up the client computers and adding a user. Is this not best practice and if not why does it do this?

It is not possible to change the accounts package but I think that the users have only had problems when they have forgot to change the clock back. Now that they know the cause and effect they can work around the problem and if they have resource access problems it will prompt them to check their clock. It is unlikely to be a problem though if the clocks are sync'd on boot.

.

Relevant Pages

  • Re: What doesnt lend itself to OO?
    ... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
    (comp.object)
  • Re: What doesnt lend itself to OO?
    ... >> service on the internet and simply accessed a clock, ... > single, resource-limited server. ... If the clock service has identity then the client looks like... ... >> because there is no temptation to use implementation inheritance to ...
    (comp.object)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • Re: Time clock on SBS 2003
    ... give your laptop an ip one number higher than the time clock. ... If the device was on the network and it was getting an ip using the ... guess that I would have to find the device in the server first to make it ... In the end we had to install the user interface on the server and RDP ...
    (microsoft.public.windows.server.sbs)
  • Re: ref clock for network POP locations
    ... I would still like to have a very accurate time source. ... I was thinking that it might be possible to get an oscillator to provide a PPS signal, and then use a very well connected (possibly even a dedicated network link with no router/switch) network peer as the preferred peer. ... a GPS based reference clock By the time you get to the computer's clock that degrades to a microsecond or two. ... The problem with networks is that they introduce random "phase noise"; e.g. if you set up a server in New York that sends packets at EXACT one second intervals, those packets will not arrive in Los Angeles at anything like one second intervals. ...
    (comp.protocols.time.ntp)