Time issues on non-PDC domain controller

July 6, 2007

Hello,

I'm posting because Google isn't bringing me anything. I've got a DC on a

virtual server, that has been somehow freezing or being non-pingable. My

real problem is, when it comes back after two-five minutes, it's time is off

by that amount of time. It isn't a PDC nor does it hold any FSMO roles at

all, though it is a GC and DNS. But the main thing is, how often does a

non-FSMO DC check with the PDC to update its time? I have manually updated

the time at least 3 times this week, and because the DC's machine name is

first alphabetically it is the default responder for domain time, and some

apps are having problems. I need to try to understand firstly, why it's

freezing in the first place, but also, the internal processes that govern

time checking and most importantly, the frequency in which it is performed.

Any ideas on this issue will be most appreciated.

Thank you.

July 9, 2007

Re: Time issues on non-PDC domain controller

As far as I recall as long as it isn't the PDCe the defined settings should

be the same, they should follow the domain hierarchy

http://technet2.microsoft.com/windowsserver/en/library/8990703a-a197-4717-b6e5-b7406d9f91f01033.mspx?mfr=true

Troubleshooting the client (DC)

http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/maintain/opsguide/part1/adogd15.mspx

A good blog on time

http://blogs.technet.com/industry_insiders/pages/w32-tm-service.aspx

--

Paul Bergson

MVP - Directory Services

MCT, MCSE, MCSA, Security+, BS CSci

2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no rights.

<-> wrote in message news:ONHL1hAwHHA.4184@TK2MSFTNGP06.phx.gbl...

> Hello,

>

> I'm posting because Google isn't bringing me anything. I've got a DC on a

> virtual server, that has been somehow freezing or being non-pingable. My

> real problem is, when it comes back after two-five minutes, it's time is

> off by that amount of time. It isn't a PDC nor does it hold any FSMO

> roles at all, though it is a GC and DNS. But the main thing is, how often

> does a non-FSMO DC check with the PDC to update its time? I have manually

> updated the time at least 3 times this week, and because the DC's machine

> name is first alphabetically it is the default responder for domain time,

> and some apps are having problems. I need to try to understand firstly,

> why it's freezing in the first place, but also, the internal processes

> that govern time checking and most importantly, the frequency in which it

> is performed.

>

> Any ideas on this issue will be most appreciated.

>

> Thank you.

>

July 14, 2007

Re: Time issues on non-PDC domain controller

According to:

http://technet2.microsoft.com/windowsserver/en/library/71e76587-28f4-4272-a3d7-7f44ca50c0181033.mspx?mfr=true

and

http://technet2.microsoft.com/windowsserver/en/library/bc5d19f2-be8c-43fc-833e-84347dc5fe7a1033.mspx?mfr=true

and

http://technet2.microsoft.com/windowsserver/en/library/bc5d19f2-be8c-43fc-833e-84347dc5fe7a1033.mspx?mfr=true

This interval is controlled my a minimum (i.e. not more frequently than) and

maximum (i.e. not less frequently than) registry setting that is (for some

reason) 2, to the power on "n", where "n" is the registry setting. The

first article say that for DCs that the values are:

Min: 6

Max 10

Or,

Min: 64 seconds

Max: 1024 seconds (approximately 17 minutes)

The articles are at pains to say that while the time sync MUST follow the

schedule, the parent can always refuse to return time values.

Why this is so complicated, I am not sure.

Cheers,

Jeremy.