Welcome to WebmasterWorld Guest from 54.159.50.111

Forum Moderators: open

Message Too Old, No Replies

Timeserver problems

     
6:12 pm on Jun 6, 2014 (gmt 0)

Senior Member

WebmasterWorld Senior Member 5+ Year Member

joined:May 6, 2008
posts:2011
votes: 0


I've got three computers. One is a timeserver, one is a Windows Server connected to that timeserver, and one is a Level 2 computer connected to the Windows Server machine but NOT to the timeserver.

How would I get the Level 2 computer to use the timeserver? I thought setting up the Windows Server machine like it was the timeserver would work, but it doesn't.
10:43 pm on June 6, 2014 (gmt 0)

Preferred Member

10+ Year Member Top Contributors Of The Month

joined:May 27, 2005
posts:428
votes: 3


For a time server you can use a website and query a page to get a timestamp that can be easier to work with when using expiration to the hour and minute... delivered as YYYY-MM-DD HH-MM.

But then which time zone do you want to use?
2:43 am on June 7, 2014 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member

joined:Jan 30, 2006
posts:1599
votes: 1


NET TIME

[\\computername | /DOMAIN[:domainname] | /RTSDOMAIN[:domainname]] [/SET]


use that command to tell your computer 3 to use computer 1 as the time server.

but if the win server is hooked to the time server why not just use the server to push time to the connected clients?
3:43 am on June 7, 2014 (gmt 0)

Senior Member from KZ 

WebmasterWorld Senior Member lammert is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Jan 10, 2005
posts: 2886
votes: 1


What is the time resolution you want to use and what are the operating systems on the time server and your level 2 computer? Windows cannot reliably synchronize time with other computers at a sub-second level. When accuracy and reliability is an issue using an NTP client would be the right way to go and NTP client software is available for several operating systems.
1:47 pm on June 9, 2014 (gmt 0)

Senior Member

WebmasterWorld Senior Member 5+ Year Member

joined:May 6, 2008
posts:2011
votes: 0


Computer A: Company timeserver with unknown OS. I don't own it, but am told to use it.
Computer B: Windows Server '03 with two LANs; Level 1 ( where timeserver is) and Level 2(operations).
Computer C,D,E,etc: Windows XP / Windows 7. All on Level 2 LAN, can't connect to Computer A.

What I was hoping to do is connect Computer B to Computer A, then connect all the other computer to Computer B. Times don't need to be exact, just within a 5 minute window. However, when I set up Computers C, D, E, etc to connect to Computer B, they do not get a time back, as if I need to do something to Computer B.

I know how to connect clients to a timeserver, but it appears I don't know what steps I need to take to tell a server (one that is a client of a timeserver) it needs to be a timeserver.
2:58 pm on June 9, 2014 (gmt 0)

Senior Member from KZ 

WebmasterWorld Senior Member lammert is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Jan 10, 2005
posts: 2886
votes: 1


As computers B to E are Windows based, you may want to use the w32tm tool to see what the current status is of the time service on each computer. w32tm is a powerful command line tool which allows you to switch the time service on and off, change the configuration and set the debug level for logging.

Without parameters the tool gives you a list of command line options. More information is available in this Microsoft Technet document [technet.microsoft.com].