Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Time server
- Thread starter Superd04
- Start date
It will by default provide the time for all of your clients on your domain, you don't have to configure anything. You should configure your DC to point to a time server out on the web though to ensure it has the right time.
I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
The poster formerly known as lander215
I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
The poster formerly known as lander215
Usually you would point the DC that maintains the PDC emulator role (which provides time services on the domain) to an Internet time server (as per Davetoo). From there all other DCs and clients will pick up the time from this DC. Hope this helps.
- Thread starter
- #4
cheers guys.. i am using this in a lab enviroment so wont be pointing to internet.. ive added a new DC to domain and its giving me the following message on second machine when i try access AD user and computers;
'Naming info cannot be located:
The clocks on the client and server machines are skewed!'
'Naming info cannot be located:
The clocks on the client and server machines are skewed!'
- Thread starter
- #5
Cheers for replies guys.. i have gone throught all the windows provided support i.e commands, editing registry, and still having issues 
i have a seperate client machine running w2k which i have 'time sync'ed' fine.. the problems seem to be with my 2nd client machine running win server 2003 sync'ing, which will be another DC (when i solve this issue). Obviously my main DC is working as a time server in some form or other, considering my w2k machine is sync'ed.
When i type the command; w32tm /resync on my second win server 2003 machine- it actually says the command was successful but clock doesnt sync, i have edited the registry and ran all commands as requested and still wont sync.. sometimes i get an 'interface error' message aswell when typing w32 /resync, cant understand whats going on??
I cant understand this as its really frustrating at this stage, is there some setting on a server 2003 OS (acting as a client) , that needs to be set for it to sync from DC time server?? Really appreciate any help on subject
i have a seperate client machine running w2k which i have 'time sync'ed' fine.. the problems seem to be with my 2nd client machine running win server 2003 sync'ing, which will be another DC (when i solve this issue). Obviously my main DC is working as a time server in some form or other, considering my w2k machine is sync'ed.
When i type the command; w32tm /resync on my second win server 2003 machine- it actually says the command was successful but clock doesnt sync, i have edited the registry and ran all commands as requested and still wont sync.. sometimes i get an 'interface error' message aswell when typing w32 /resync, cant understand whats going on??
I cant understand this as its really frustrating at this stage, is there some setting on a server 2003 OS (acting as a client) , that needs to be set for it to sync from DC time server?? Really appreciate any help on subject
- Thread starter
- #7
Cheers mate, Its just a lab setup for training purposes, 3 laptops and a switch.. does win server 2003 have FW in-built, or something else that may be blocking ports, the fact my w2k machine is sync'ed ok would that not eliminate that idea?
- Status
Similar threads
- Locked
- Question