|
-
September 21st, 2004, 03:48 PM
#3
I think that worked.
I pointed DOMCON to a Navy atomic clock, double-checked settings in both Windows Time Service and the registry settings for the time service. Then, using "net time /setsntp:DOMCON", I set the others to now point to DOMCON as they should....looks to be working so far.
But there's something wierd. If I run a simple "net time" command with no other arguments, it tells me "the time at //BAKSERV2 is" such-and-such, no matter what computer I'm on. Why is that? Now if I run a "net time /querysntp" it shows DOMCON as the time server as it should be, so I presume all is well, but the BAKSERV2 reference with the other command doesn't make sense to me. Why would it do that? Should it not report the time on DOMCON instead?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|