I have my "main" windows 2003 server with these settings:
net time /setsntp:nist.gov
I can do a query and it says it is set to that, but I cannot get it to sync
time? I have the appropriate rule for allow in my ISA firewall. I can get all
computers in my lan to sync with my "main" server. I stopped and restarted
the w32 time service, but it still would not sync. Any ideas?
--
Glenn MCP A+
Network Admin
MBBC

I think you need to add a host name - eg. time-a.nist.gov:

http://tf.nist.gov/service/time-servers.html

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Glenn @ Maranatha" <GlennMaranatha@discussions.microsoft.com> wrote in
message news:EF6B5B6F-EEBC-44A4-A685-D14FC6335808@microsoft.com...

Not sure what you mean by host name? I used this command:
net time /setsntp:time-a.nist.gov
set successfully
net time /querysntp
The current SNTP value is: time-a.nist.gov

net stop /w32time
net start /w32time

net time /set
Current time at \\MAIN is 1/24/2006 3:51
....
....
I then checked my rule in ISA and made sure that the Ip address of my time
rule is set to the time-a.nist.gov site which is 129.6.15.28
My time is still off by 12 minutes.
Glenn MCP A+
Network Admin
MBBC

Time-a is the host name - ie name of the server. Nist.gov is the domain
part of the name. You first said: "net time /setsntp:nist.gov" So, I
thought you forgot to include the host name.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Glenn @ Maranatha" <GlennMaranatha@discussions.microsoft.com> wrote in
message newsC59DAF1-DFE3-488B-B1DE-97FD47C17344@microsoft.com...

You seem to be confusing two time sources and methods of syncing. As I read
what you are doing, your net time /set is getting its time from your domain,
\\MAIN, not from the SNTP source. Presumably, \\MAIN is also off. It would
seem that the reasonable thing to do is sync time on \\MAIN, probably with
w32tm /resync /computer:MAIN, and then just w32tm /resync on the local
computer.
--
Greg Stigers, MCSA
remember to vote for the answers you like

I do appreciate your responses. However, I don't think I was real clear on
what has happened. My W2003 server is named "MAIN, and that is the server I
have been trying to sync ot the time-a.nist.giv unsuccessfully. You cant
begin a resync with w32time, it says it is not recognized as an internal or
external command. I am not sure what you mean when you say you presume that
\Presumably, \\MAIN is also off.??

The problem as I see it, is that I set the sntp to time-a.nist.gov then when
I try and do a set it tells me it is pointing to itself, that is why I am
confused about all this. I have never had this problem when setting up an
external time souce, but thne again, I have only done this two other times,
sorry about sounding so newbie about it.
--
Glenn MCP A+
Network Admin
MBBC


"G" wrote:

I think I got it. I put in the ip address for the setsntp:... instead of the
wording and it seems to be synced up correctly. Now if it will jus tkeep
synched I will be a happy camper.

Thanks for all you help and for the willingness to weigh in on the matter.
--
Glenn MCP A+
Network Admin
MBBC


"G" wrote:

"Glenn @ Maranatha" wrote:
for w32tm /resync [/computer:<computer>] [/nowait] [/rediscover] [/soft].
You can begin a resync with w32tm /resync on a client. You can use
w32tm /config [/computer:<target>] [/update]
[/manualpeerlist:<peers>] [/syncfromflags:<source>]
[/LocalClockDispersion:<seconds>]
[/reliableYES|NO)]
[/largephaseoffset:<milliseconds>]
on your 2003 domain controller to configure it. Pay special attention to
manualpeerlist and reliable.

\\MAIN. I would assume it is syncing with MAIN, and that the time on MAIN is
"off by twelve minutes", which is why your clients are "off by twelve
minutes".
--
Greg Stigers, MCSA
remember to vote for the answers you like