sync'ing time on Windows 2000 server

[Guest]

I have a server that the Event Log reports: The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The difference might be caused by synchronization with low-accuracy time sources.........the time service is no longer synch'd and cannot provide the time to other clients or update the system time.

How do I point my server to receive the correct time from a valid source

Thanks in advance!

 

[Frank S]

How do I point my server to receive the correct time

from a valid source?

Thanks in advance!

Sit at the server in question (should normally be the FSMO domain
controller, but not completely necessary) and type the following at a
command line window.

net time /set /setsntp:time.nist.gov

close command line window.

There are many free Internet time servers, but the one above will work fine.

That computer will now hold that time sync host setting even through
reboots. If it is a domain controller, all your W2K clients will
automatically sync their time with that FSMO domain controller. Although,
if you really want to, you could set each and every computer to do this. It
is much better to have only the FSMO domain controller do this.

-Frank

 

[Jisha]

http://www.worldtimeserver.com/atomic-clock/

Simple, no spyware, ad banners, etc... and $free

 

[Frank S]

I think you missed the point. Time synch is BUILT INTO W2K. There is NO
NEED for any "utility" like you provided a link to below.

-Frank

 

[Jisha]

I probably did ...

....but I tried your "net time..." command and received something like "time
server not found".
Assumed it wasn't available in w2k pro... just server edition.

Should it have worked in w2kpro?
If not, I just discoverd another system boo-boo.

Chris

 

[Frank S]

Well, you DO have to be able to reach the time server "Time Server Not
Found" means that you cannot reach the time server. couple of things...

1st: Ping it, should get something like below...

----------------------------------
U:\>ping time.nist.gov

Pinging time.nist.gov [192.43.244.18] with 32 bytes of data:

Reply from 192.43.244.18: bytes=32 time=110ms TTL=49
Reply from 192.43.244.18: bytes=32 time=110ms TTL=49
Reply from 192.43.244.18: bytes=32 time=100ms TTL=49
Reply from 192.43.244.18: bytes=32 time=100ms TTL=49

Ping statistics for 192.43.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 110ms, Average = 105ms

U:\>
-------------------------------------

2nd: Make sure UDP port port 123 is not blocked on your firewall. The RFC
STANDARD SNTP protocol uses this port. W2K supports this standard SNTP time
protocol.

3rd: Yes, W2K pro should work fine as well.

-Frank

 

[Frank S]

One more thing.... I did a booboo.... I'm sorry!

I (MIS)typed... net time /set /setsntp:time.nist.gov

I MEANT... net time /setsntp:time.nist.gov

-Frank

 

[Jisha]

I MEANT... net time /setsntp:time.nist.gov

Ahh... That worked perfectly

Funny... I was just going through your check-list when your PS: BooBoo
showed up :]

LOL, Thanks...
Chris