RE: time difference, cannot log on

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: S.J.Haribabu (sjhari_at_microsoft.com)
Date: 06/21/04 

Date: Mon, 21 Jun 2004 21:14:38 GMT

Hi,

Try this solution

Troubleshooting Time-Related Errors
===================================

Unable to Log On to the Network
=============================
When you attempt to log on to the network you might receive the following
error message:

The system cannot log you on due to the following error:
There is a time difference between the Client and Server.
Please try again or consult your system administrator.

This behavior can occur if the time or date is not synchronized between
your computer and the domain to which you are attempting to log on. If the
time or date on a client is not synchronized with the authenticating domain
controller, Kerberos validation does not succeed.

Because Kerberos is the only form of logon authentication between two
Windows 2000-based computers, the logon attempt does not succeed.

To resolve this issue, log on to your computer locally by using an account
with administrative privileges and set the time and date to match the time
and date on the domain controller that validates your logon process.

To see more time-related errors look at
http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/operat
e/wintime.mspx#XSLTsection130121120120

For example, you can use Microsoft's time server (time.windows.com) for
this function. After you set the SNTP time server as authoritative, run
either of the following commands on a computer other than the domain
controller to reset the local computer's time against the authoritative
time server:
net time /your domain name /set
Type the following commands, pressing ENTER after each command:
net stop w32time
w32tm –once
net start w32time

More information about the net time command is available at a command
prompt if you type the following command:
net time /?

SNTP defaults to using User Datagram Protocol (UDP) port 123. If this port
is not open to the Internet, you cannot synchronize your server to Internet
SNTP servers.

NOTE: Administrators can also configure an internal time server as
authoritative by using the net time command. If the administrator directs
the command to the operations master, it may be necessary to reboot the
server for the changes to take effect.

Thanks,

sjhari@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

 

Relevant Pages

  • Re: AD 2k8
    ... I suggest not using the net time command for diagnostic purposes - use the w32tm command instead (w32tm /? ... 0x01 Always time server ...
    (microsoft.public.windows.server.active_directory)
  • Re: Authoritative Time Server Setup
    ... The net time /setsntp command is not required on member workstation/servers because they will auto-magically configure themselves to participate in acquiring time thru domain hierarchy. ... Therefore the only time you should have to use the net time /setsntp command is when moving around the PDC FSMO role. ... net time /setsntp:<external time server> on a DC? ...
    (microsoft.public.win2000.general)
  • Net Time
    ... If your network is not connected to the internet, ... use the net time /setsntp:ip address command to set the ... time server to itself? ...
    (microsoft.public.win2000.advanced_server)
  • Re: time sync on a windows 2000 server
    ... >From the command line ... net time /setsntp:time.windows.com ... Or use another time server of your choice. ... > Can anyone tell me how to set up a windows 2000 server to ...
    (microsoft.public.win2000.networking)
  • Re: time synch problem
    ... Type the following command and then press ENTER: ... net start w32time ... Should look similar like this,a the end you see the actual time server: ... the "reliable" time source instead of assuming its the PDC? ...
    (microsoft.public.windows.server.active_directory)