Clients sync to wrong NTP DC

[Guest johnisccp]

I have three W2K DCs. One is in the remote site and the other two DCs are in

the Corp office. I setup the FSMO DC at corp office to get its time from the

router. For some reason all the clients are getting its time from the remote

DC. I compare the two DCs registry entry for W32Time. Everything looks the

same except the registry entry "type". The remote DC has a the "type REG_SZ

Nt5DS" and the FSMO DC has a "type REG_SZ NTP". Does it matter what the type

is in the registry? I am trying to make sure the clients are sync their time

to the FSMO DC and not the remote DC. I ran net time on my machine and it is

show:

C:\>net time

Current time at \\AUSTINFS1 is 2/12/2008 11:07 AM

 

Local time (GMT-06:00) at \\AUSTINFS1 is 2/12/2008 10:07 AM

 

The command completed successfully.

[Guest Newell White]

RE: Clients sync to wrong NTP DC

 

 

"johnisccp" wrote:

> I have three W2K DCs. One is in the remote site and the other two DCs are in

> the Corp office. I setup the FSMO DC at corp office to get its time from the

> router. For some reason all the clients are getting its time from the remote

> DC. I compare the two DCs registry entry for W32Time. Everything looks the

> same except the registry entry "type". The remote DC has a the "type REG_SZ

> Nt5DS" and the FSMO DC has a "type REG_SZ NTP". Does it matter what the type

> is in the registry? I am trying to make sure the clients are sync their time

> to the FSMO DC and not the remote DC. I ran net time on my machine and it is

> show:

> C:\>net time

> Current time at \\AUSTINFS1 is 2/12/2008 11:07 AM

>

> Local time (GMT-06:00) at \\AUSTINFS1 is 2/12/2008 10:07 AM

>

> The command completed successfully.

>

>

Yes, the registry controls wat syncs with what.

 

The types available are:

NT5DS = sync with a DC higher up the order (PDC emulator in our LAN)

NTP = sync with the NTP provider whose URL is specified in the registry

entry about 3 lines up the page

NoSync = free run

 

So remote DC should be NT5DS, and FSMO should be NTP if synced to external

provider or LAN time source, or free run if you don't care about the time in

the rest of the universe.

 

--

Regards,

Newell White

[Guest johnisccp]

RE: Clients sync to wrong NTP DC

 

Newell,

 

Is that is the case, then how can I make all the clients to sync with the

FSMO DC and not the remote DC?

 

Thanks

 

John

 

"Newell White" wrote:

>

> "johnisccp" wrote:

>

> > I have three W2K DCs. One is in the remote site and the other two DCs are in

> > the Corp office. I setup the FSMO DC at corp office to get its time from the

> > router. For some reason all the clients are getting its time from the remote

> > DC. I compare the two DCs registry entry for W32Time. Everything looks the

> > same except the registry entry "type". The remote DC has a the "type REG_SZ

> > Nt5DS" and the FSMO DC has a "type REG_SZ NTP". Does it matter what the type

> > is in the registry? I am trying to make sure the clients are sync their time

> > to the FSMO DC and not the remote DC. I ran net time on my machine and it is

> > show:

> > C:\>net time

> > Current time at \\AUSTINFS1 is 2/12/2008 11:07 AM

> >

> > Local time (GMT-06:00) at \\AUSTINFS1 is 2/12/2008 10:07 AM

> >

> > The command completed successfully.

> >

> >

> Yes, the registry controls wat syncs with what.

>

> The types available are:

> NT5DS = sync with a DC higher up the order (PDC emulator in our LAN)

> NTP = sync with the NTP provider whose URL is specified in the registry

> entry about 3 lines up the page

> NoSync = free run

>

> So remote DC should be NT5DS, and FSMO should be NTP if synced to external

> provider or LAN time source, or free run if you don't care about the time in

> the rest of the universe.

>

> --

> Regards,

> Newell White

[Guest thomville]

Re: Clients sync to wrong NTP DC

 

As long as the clients are using type "NT5DS," which is the default

setting, the will authenticate on login against (in this order), the

DC holding the PDC Emulator role, the DC they logged in against,

another server, another workstation.

 

Thom

 

 

 

 

On Feb 12, 11:43 am, johnisccp <johnis...@discussions.microsoft.com>

wrote:

> Newell,

>

> Is that is the case, then how can I make all the clients to sync with the

> FSMO DC and not the remote DC?

>

> Thanks

>

> John

>

> "Newell White" wrote:

>

> > "johnisccp" wrote:

>

> > > I have three W2K DCs. One is in the remote site and the other two DCs are in

> > > the Corp office. I setup the FSMO DC at corp office to get its time from the

> > > router. For some reason all the clients are getting its time from the remote

> > > DC. I compare the two DCs registry entry for W32Time. Everything looks the

> > > same except the registry entry "type". The remote DC has a the "type REG_SZ

> > > Nt5DS" and the FSMO DC has a "type REG_SZ NTP". Does it matter what the type

> > > is in the registry? I am trying to make sure the clients are sync their time

> > > to the FSMO DC and not the remote DC. I ran net time on my machine and it is

> > > show:

> > > C:\>net time

> > > Current time at \\AUSTINFS1 is 2/12/2008 11:07 AM

>

> > > Local time (GMT-06:00) at \\AUSTINFS1 is 2/12/2008 10:07 AM

>

> > > The command completed successfully.

>

> > Yes, the registry controls wat syncs with what.

>

> > The types available are:

> > NT5DS = sync with a DC higher up the order (PDC emulator in our LAN)

> > NTP = sync with the NTP provider whose URL is specified in the registry

> > entry about 3 lines up the page

> > NoSync = free run

>

> > So remote DC should be NT5DS, and FSMO should be NTP if synced to external

> > provider or LAN time source, or free run if you don't care about the time in

> > the rest of the universe.

>

> > --

> > Regards,

> > Newell White