Windows Time service to use an external time source issue

[Guest stargaten]

Hello all,

 

Well, I followed the KB article: http://support.microsoft.com/kb/816042 to

use an external time source for my domain. I thought the procedure went well

until I ran the following: w32tm /resync /rediscover and I received the

following message:

 

Sending resync command to local computer...

The computer did not resync because no time data was available.

 

I have used time.windows.com and my ISPs NTP server same issue.

 

Also, I'm receiving Event ID 38 in the System event logs.

 

I have also checked my GPOs Default and DC policy and the items pertaining

to windows time are not configured.

 

Any ideas or suggestions?

 

Thanks

[Guest Bruce Sanderson]

Re: Windows Time service to use an external time source issue

 

My personal opinion, for what it is worth, is that the KB article you

referenced is unfortunate - everything needed can be done simply with the

w32tm command - there is no need to edit the registry directly, which is

unnecessarily dangerous.

 

If you're interested, you might find the thread "time sync from NTP in win

2003" in the newsgroup "microsoft.public.windows.server.active_directory"

and the thread "domain controller time service" in this newsgroup

(microsoft.public.windows.server.general) informative. There are several

references to reasonably good Microsoft documentation in those threads.

 

See also http://support.microsoft.com/kb/830092.

 

Try again using the following set of commands on the domain controller you

want to be the root of your time synchronization hierarchy (usually, but not

always, the one with the PDC Emulator FSMO Role).

 

w32tm /config /syncfromflags:manual /manualpeerlist:time.nist.com

/reliable:yes /update

w32tm /resync /rediscover

 

In the first command, instead of time.nist.com, you can specify any NTP

server you prefer - see http://support.ntp.org/bin/view/Servers/WebHome for

a fairly comprehensive list. Use the nslookup command to make sure the

computer can resolve the DNS name of the server you choose; if it can't, you

need to resolve the DNS problem first.

 

It might be useful to use the following command on the other domain

controllers so that they will synchronize with the root of the time

synchronization heirarchy (the Domain controller that you ran the above

commands on):

 

w32tm /config /syncfromflags:domhier /reliable:no /update

w32tm /resync /rediscover

 

If that doesn't solve the problem, please post copies of the Event Log

entries that have "Time-Service" as the Source (System Event Log) from the

one configured as "reliable" and I (we) will try to help some more.

 

--

Bruce Sanderson

http://members.shaw.ca/bsanders

 

It is perfectly useless to know the right answer to the wrong question.

 

 

 

"stargaten" <stargaten@discussions.microsoft.com> wrote in message

news:27ACA45C-7D7C-4821-A064-702AEEAE1969@microsoft.com...

> Hello all,

>

> Well, I followed the KB article: http://support.microsoft.com/kb/816042 to

> use an external time source for my domain. I thought the procedure went

> well

> until I ran the following: w32tm /resync /rediscover and I received the

> following message:

>

> Sending resync command to local computer...

> The computer did not resync because no time data was available.

>

> I have used time.windows.com and my ISPs NTP server same issue.

>

> Also, I'm receiving Event ID 38 in the System event logs.

>

> I have also checked my GPOs Default and DC policy and the items pertaining

> to windows time are not configured.

>

> Any ideas or suggestions?

>

> Thanks

>

[Guest stargaten]

Re: Windows Time service to use an external time source issue

 

I appreciate your opinion and your word of caution in regards to editing

directly.

 

I am still having the issue I described. The only event entry I'm receiving

is Event ID 38 on the PDCE. I have checked our FW policy for UDP port 123

and we are good.

 

I ran net time /querysntp and receive the following: The current sntp value

is: time.nist.com,0x1 I have also tried time.windows.com and the same result.

 

Thanks in advance.

 

"Bruce Sanderson" wrote:

> My personal opinion, for what it is worth, is that the KB article you

> referenced is unfortunate - everything needed can be done simply with the

> w32tm command - there is no need to edit the registry directly, which is

> unnecessarily dangerous.

>

> If you're interested, you might find the thread "time sync from NTP in win

> 2003" in the newsgroup "microsoft.public.windows.server.active_directory"

> and the thread "domain controller time service" in this newsgroup

> (microsoft.public.windows.server.general) informative. There are several

> references to reasonably good Microsoft documentation in those threads.

>

> See also http://support.microsoft.com/kb/830092.

>

> Try again using the following set of commands on the domain controller you

> want to be the root of your time synchronization hierarchy (usually, but not

> always, the one with the PDC Emulator FSMO Role).

>

> w32tm /config /syncfromflags:manual /manualpeerlist:time.nist.com

> /reliable:yes /update

> w32tm /resync /rediscover

>

> In the first command, instead of time.nist.com, you can specify any NTP

> server you prefer - see http://support.ntp.org/bin/view/Servers/WebHome for

> a fairly comprehensive list. Use the nslookup command to make sure the

> computer can resolve the DNS name of the server you choose; if it can't, you

> need to resolve the DNS problem first.

>

> It might be useful to use the following command on the other domain

> controllers so that they will synchronize with the root of the time

> synchronization heirarchy (the Domain controller that you ran the above

> commands on):

>

> w32tm /config /syncfromflags:domhier /reliable:no /update

> w32tm /resync /rediscover

>

> If that doesn't solve the problem, please post copies of the Event Log

> entries that have "Time-Service" as the Source (System Event Log) from the

> one configured as "reliable" and I (we) will try to help some more.

>

> --

> Bruce Sanderson

> http://members.shaw.ca/bsanders

>

> It is perfectly useless to know the right answer to the wrong question.

>

>

>

> "stargaten" <stargaten@discussions.microsoft.com> wrote in message

> news:27ACA45C-7D7C-4821-A064-702AEEAE1969@microsoft.com...

> > Hello all,

> >

> > Well, I followed the KB article: http://support.microsoft.com/kb/816042 to

> > use an external time source for my domain. I thought the procedure went

> > well

> > until I ran the following: w32tm /resync /rediscover and I received the

> > following message:

> >

> > Sending resync command to local computer...

> > The computer did not resync because no time data was available.

> >

> > I have used time.windows.com and my ISPs NTP server same issue.

> >

> > Also, I'm receiving Event ID 38 in the System event logs.

> >

> > I have also checked my GPOs Default and DC policy and the items pertaining

> > to windows time are not configured.

> >

> > Any ideas or suggestions?

> >

> > Thanks

> >

>

>

[Guest stargaten]

Re: Windows Time service to use an external time source issue

 

Hello Bruce,

 

I just wanted to update you on my issue. I have found my error. I was

using time.nist.com. Not good. I'm using time-a.nist.gov now and everyone

is playing nice now.

 

Thanks again for your help and direction.

 

"Bruce Sanderson" wrote:

> My personal opinion, for what it is worth, is that the KB article you

> referenced is unfortunate - everything needed can be done simply with the

> w32tm command - there is no need to edit the registry directly, which is

> unnecessarily dangerous.

>

> If you're interested, you might find the thread "time sync from NTP in win

> 2003" in the newsgroup "microsoft.public.windows.server.active_directory"

> and the thread "domain controller time service" in this newsgroup

> (microsoft.public.windows.server.general) informative. There are several

> references to reasonably good Microsoft documentation in those threads.

>

> See also http://support.microsoft.com/kb/830092.

>

> Try again using the following set of commands on the domain controller you

> want to be the root of your time synchronization hierarchy (usually, but not

> always, the one with the PDC Emulator FSMO Role).

>

> w32tm /config /syncfromflags:manual /manualpeerlist:time.nist.com

> /reliable:yes /update

> w32tm /resync /rediscover

>

> In the first command, instead of time.nist.com, you can specify any NTP

> server you prefer - see http://support.ntp.org/bin/view/Servers/WebHome for

> a fairly comprehensive list. Use the nslookup command to make sure the

> computer can resolve the DNS name of the server you choose; if it can't, you

> need to resolve the DNS problem first.

>

> It might be useful to use the following command on the other domain

> controllers so that they will synchronize with the root of the time

> synchronization heirarchy (the Domain controller that you ran the above

> commands on):

>

> w32tm /config /syncfromflags:domhier /reliable:no /update

> w32tm /resync /rediscover

>

> If that doesn't solve the problem, please post copies of the Event Log

> entries that have "Time-Service" as the Source (System Event Log) from the

> one configured as "reliable" and I (we) will try to help some more.

>

> --

> Bruce Sanderson

> http://members.shaw.ca/bsanders

>

> It is perfectly useless to know the right answer to the wrong question.

>

>

>

> "stargaten" <stargaten@discussions.microsoft.com> wrote in message

> news:27ACA45C-7D7C-4821-A064-702AEEAE1969@microsoft.com...

> > Hello all,

> >

> > Well, I followed the KB article: http://support.microsoft.com/kb/816042 to

> > use an external time source for my domain. I thought the procedure went

> > well

> > until I ran the following: w32tm /resync /rediscover and I received the

> > following message:

> >

> > Sending resync command to local computer...

> > The computer did not resync because no time data was available.

> >

> > I have used time.windows.com and my ISPs NTP server same issue.

> >

> > Also, I'm receiving Event ID 38 in the System event logs.

> >

> > I have also checked my GPOs Default and DC policy and the items pertaining

> > to windows time are not configured.

> >

> > Any ideas or suggestions?

> >

> > Thanks

> >

>

>