Simple Network Time setup on many systems 1

[stussy]

Hi

I need to setup a time server on our network, but every way I try I'm getting no joy. I suspect it's due to the upside-down setup of our network...

NT4 logon server (PDC)
Win 2000 server as file server (domain member)
Win 2003 server as file server (domain member)
Approx 12 XP pro workstations
Approx 15 Win 2000 workstations

Need to point out I can't change the network setup. The NT4 server will stay as PDC, so no suggestions about 'use the 2003 server as PDC' please! It runs a network of IP cameras.

Does anyone have any ideas of how to best setup both servers and workstations? Please bear in mind I know NOTHING about this! I'll need some very simple instructions, and I will be very generous with stars to everyone that helps! (Ends begging mode...)

Cheers

Mike

 

[markdmac]

Create a batch file with this command:
"NET TIME \\Server /set /y"

Where Server is the name of the server you want to be your authoritative time server. Put the batch in the netlogon directory of the PDC.

I hope you find this post helpful.

Regards,

Mark

 

[stussy]

Thanks for the quick reply. No joy though. Deliberately set my pc clock to 5 mins slow, and it stayed wrong after reboot and relogon. No entry in event viewer, this is the last one in there (from 2 weeks ago). Just looking at it though, do I need to set the server I want to use to use an internet time clock? Also is there any way I can check where my PC is looking to for time?

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 36
Date: 15/09/05
Time: 04:10:05
User: N/A
Computer: MIKE
Description:
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

 

[markdmac]

Which server did you use as the SNTP? Have you verified that that server is syncronizing with an authoritative source on the Internet?

Time sync does not happen all at once. It negotiates down slowly to avoid messing with file time stamps. So even when you have it working, if your clock is off by a lot do not expect it to sync up completely right away.

I hope you find this post helpful.

Regards,

Mark

 

[stussy]

Also...running NET TIME /querysntp shows:

current SNTP value is: server1,0x1

which means the server is correct, but it failed?

 

[stussy]

OK this is the current setup:

server1 (win2k) has been set to get time from time.windows.com

mike (xp pro) has been set to get time from server1

Both of these machines gave me a 'command completed correctly' when doing the setsntp command, and both show the right value when doing querysntp. I'll leave my pc on the wrong time tonight when I leave (90 mins) and see what it looks like in the morning. Thanks Mark.

 

[markdmac]

On your server you should reset the Windows Time Service after setting the SNTP value.

FYI, I have found that Win2K servers are very prone to this error and the Windows 2003 servers (which offer some new command choices) seem to work much better at it. If you can use your Win2K3 file server as the time server I think you will find you have better results.

Let me know if you want to try that and I will look up the commands for you.

I hope you find this post helpful.

Regards,

Mark

 

[stussy]

Hi Mark

No joy last night. Lets follow your idea and use the 2003 server. The 2003 server is set to use time.windows.com as well, and it errors saying could not sync with . even though the address seems correct.

If we can get this syncing happily first then I'll move onto getting the 2000 server syncing with the 2003 server.

Cheers

Mike

 

[markdmac]

OK, first off let's make sure you have port 123 open on your firewall. That is the port used for SNTP.

Next, at the server open a command prompt and try executing the following:

net stop w32time
w32tm -once
net start w32time

If this works successfully, copy the above commands to a batch file and use the scheduler service to schedule it once a day.

I hope you find this post helpful.

Regards,

Mark

 

[stussy]

Well that got us so far - port 123 is closed (running the check at shields up) on our firewall, and I can't get it open for the life of me...once I get that open I'll carry this on! Thanks for the help so far Mark.

 

[markdmac]

Glad to be of service. If that port is closed then your 2000 server may be just fine, it just needs the port open to communicate.

I hope you find this post helpful.

Regards,

Mark

 

[stussy]

Hi Mark

Well the firewall is configured correctly - all XP machines merrily getting fed the time by ntp0.uk.uu.net, and I can see the activity in the firewall logs.

BUT still no joy from the 2003 server, in fact it is servers cos I've tried it on another one now. Both of them resolutely resist being updated. Windows firewall is NOT running on either, however to satisfy myself I turned it on, allowed traffic through on NTP and it still did nothing.

Tearing my hair out now! Any ideas?

Cheers

Mike

 

[markdmac]

Halfway there then eh?

If I am understnading your post above you have configured your clients to get their time updates directly from the Internet. That would not be advisable. Have each of your machines get updates from one internal server and have that server go out on the Internet.

Do that and have your 2003 server point internally to the 2000 server. Execute the commands as stated above and let me know what you get for results.

I hope you find this post helpful.

Regards,

Mark

 

[conan3]

Just a thought does your account have change system time permission?

Seems to me NT Domain had to have "domain users" added to change system time to set workstation time with "NET TIME \\PDCServer /set /yes"

It's been a while

Windows 2000 AD does this from the first (2000) domain controller automaticaly.

You Set it on 2000 DC with net time /SETSNTP:ntp0.uk.uu.net, time.windows.com, third time server etc..


Conan3

 

[stussy]

Thanks for the replies.

Mark - I just setup the xp workstations to get their time from an internet source to prove that the firewall can't be the source of the problem - if 2 different machines can get out to an external time source, the firewall must be allowing all traffic through on 123.

Conan3 - I'm trying to update these whilst logged on as domain admin. I think some of the hassle may come from us having our NT4 PDC...

Cheers

Mike

 

[stussy]

Well lets end the week on a relative high! I should have done this earlier. There are dozens of programs out there achieving this 'simple network time protocol' without anything LIKE the rigmarole MS goes through.

So you can get a great shareware app from

http://www.kaska.demon.co.uk/

It's called Tardis (UK'ers should get the reference!) and it works on every version of Windows. All my servers and workstations are now syncing from the time source I wanted to use all along. Nice irony that I have to disable the Windows Time service to get it working.

I don't usually bash Microsoft for the sake of it, but this has justified, to me at least, why we need healthy competition in the IT world...

Thanks for all your help, it's 16:57 in the UK (exactly!) and I'm off to meet Mr Stella, Mr Shiraz, and Mr Whisky if I make it that far Have a good weekend

 

[markdmac]

Ah, but does it come with a sonic screwdriver?
And did you read the warnings regarding possible Dahlek interferrence?
;-)

(Some of us across the pond get the reference too )

Glad you got things working in the end.



I hope you find this post helpful.

Regards,

Mark