NTP servers

Can I set the scope option in DHCP to hand out a public NTP time server to
clients without any additional config on the client side? I have a single
forest, single domain Windows Server 2003 AD environment. All clients are XP
Pro.

Sean

obnetadmin <(E-Mail Removed)> wrote:
> Can I set the scope option in DHCP to hand out a public NTP time
> server to clients without any additional config on the client side? I
> have a single forest, single domain Windows Server 2003 AD
> environment. All clients are XP Pro.
>
> Sean

Hmm - but your clients should *not* specify a public time server with which
to sync. They should be syncing only with your DC (the PDC emulator role) if
you want AD to work right. If you're having a problem with this config
perhaps you could post the details so someone can help you address them.

Hello obnetadmin,

Clients in a domain need the time from the PDCEmulator in your domain, this
is a automatic configuration to ensure that the clients can correctly work
in the domain, so NEVER change this.

Time syncronization in a domain works that the DC which has the PDCEmulator
role is the time server for the domain, all other DC's syncs with this one
and all member servers and workstations syncs with one of the available DC's.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Can I set the scope option in DHCP to hand out a public NTP time
> server to clients without any additional config on the client side? I
> have a single forest, single domain Windows Server 2003 AD
> environment. All clients are XP Pro.
>
> Sean
>

The only problem we have seen lately is that clients are 8 minutes fast for
some reason. In my environment, we have 20 DC's. Should the PDC Emulator role
only be dedicated to one DC (the first installed in the domain)?

"Lanwench [MVP - Exchange]" wrote:

> obnetadmin <(E-Mail Removed)> wrote:
> > Can I set the scope option in DHCP to hand out a public NTP time
> > server to clients without any additional config on the client side? I
> > have a single forest, single domain Windows Server 2003 AD
> > environment. All clients are XP Pro.
> >
> > Sean
>
> Hmm - but your clients should *not* specify a public time server with which
> to sync. They should be syncing only with your DC (the PDC emulator role) if
> you want AD to work right. If you're having a problem with this config
> perhaps you could post the details so someone can help you address them.
>
>
>

Hello obnetadmin,

Single forest, single domain? The you only have one PDCEmulator.

See here about some documentation:
FSMO roles
http://support.microsoft.com/kb/223346/en-us

PDCEmulator
http://technet2.microsoft.com/Window....mspx?mfr=true

Client time config
http://technet2.microsoft.com/Window...f91f01033.mspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> The only problem we have seen lately is that clients are 8 minutes
> fast for some reason. In my environment, we have 20 DC's. Should the
> PDC Emulator role only be dedicated to one DC (the first installed in
> the domain)?
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> obnetadmin <(E-Mail Removed)> wrote:
>>
>>> Can I set the scope option in DHCP to hand out a public NTP time
>>> server to clients without any additional config on the client side?
>>> I have a single forest, single domain Windows Server 2003 AD
>>> environment. All clients are XP Pro.
>>>
>>> Sean
>>>
>> Hmm - but your clients should *not* specify a public time server with
>> which to sync. They should be syncing only with your DC (the PDC
>> emulator role) if you want AD to work right. If you're having a
>> problem with this config perhaps you could post the details so
>> someone can help you address them.
>>

obnetadmin <(E-Mail Removed)> wrote:
> The only problem we have seen lately is that clients are 8 minutes
> fast for some reason.

Then you've got larger problems.

> In my environment, we have 20 DC's. Should the
> PDC Emulator role only be dedicated to one DC (the first installed in
> the domain)?

As Meinolf wrote, there can be only one. Check the time on *that* and make
sure it's set up to sync with a good public timeserver.


>
> "Lanwench [MVP - Exchange]" wrote:
>
>> obnetadmin <(E-Mail Removed)> wrote:
>>> Can I set the scope option in DHCP to hand out a public NTP time
>>> server to clients without any additional config on the client side?
>>> I have a single forest, single domain Windows Server 2003 AD
>>> environment. All clients are XP Pro.
>>>
>>> Sean
>>
>> Hmm - but your clients should *not* specify a public time server
>> with which to sync. They should be syncing only with your DC (the
>> PDC emulator role) if you want AD to work right. If you're having a
>> problem with this config perhaps you could post the details so
>> someone can help you address them.

> Can I set the scope option in DHCP to hand out a public NTP time server to
> clients without any additional config on the client side?

Don't think this has anything to do with DHCP at all. But...

This is an automatic config. The workstations need to get their time from
the PDCemulator DC. Set the PDCemulator DC to a reliable time source. You
should not do anything to the XP workstations on the domain. They will
automatically go to the PDCemulator for the time.

When typing "net time /querysntp" on the XP client, you should see this...

---------------------
C:\Users\frank>net time /querysntp
This computer is not currently configured to use a specific SNTP server.

The command completed successfully.

C:\Users\frank>
-----------------------

If you do not see this, but instead, see that the workstations have been set
to a specific time server, you should do this...

net time /setsntp: [enter]

This will eliminate any previously set time server and allow the workstation
to automatically sync to the PDCemulator.

-Frank

I have three DC's at my main site:
(ADMINROOTDC01,ADMINROOTDC02,ADMINROOTDC03). ADMINROOTDC01 holds all but two
of the FSMO roles. DC03 is the PDC Emulator; DC02 is the Infrastructure
Master. Does this present any problems?

"Meinolf Weber" wrote:

> Hello obnetadmin,
>
> Single forest, single domain? The you only have one PDCEmulator.
>
> See here about some documentation:
> FSMO roles
> http://support.microsoft.com/kb/223346/en-us
>
> PDCEmulator
> http://technet2.microsoft.com/Window....mspx?mfr=true
>
> Client time config
> http://technet2.microsoft.com/Window...f91f01033.mspx
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > The only problem we have seen lately is that clients are 8 minutes
> > fast for some reason. In my environment, we have 20 DC's. Should the
> > PDC Emulator role only be dedicated to one DC (the first installed in
> > the domain)?
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> obnetadmin <(E-Mail Removed)> wrote:
> >>
> >>> Can I set the scope option in DHCP to hand out a public NTP time
> >>> server to clients without any additional config on the client side?
> >>> I have a single forest, single domain Windows Server 2003 AD
> >>> environment. All clients are XP Pro.
> >>>
> >>> Sean
> >>>
> >> Hmm - but your clients should *not* specify a public time server with
> >> which to sync. They should be syncing only with your DC (the PDC
> >> emulator role) if you want AD to work right. If you're having a
> >> problem with this config perhaps you could post the details so
> >> someone can help you address them.
> >>
>
>
>

Hello obnetadmin,

No, the domain time source is your DC03, here you have to set an external
time source for the complete domain time, see the documentation link. All
other DC's have to sync with this one. If you use firewalls on the servers
and clients make sure that on all machines port 123 is open for outgoing
and incoming traffic.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I have three DC's at my main site:
> (ADMINROOTDC01,ADMINROOTDC02,ADMINROOTDC03). ADMINROOTDC01 holds all
> but two of the FSMO roles. DC03 is the PDC Emulator; DC02 is the
> Infrastructure Master. Does this present any problems?
>
> "Meinolf Weber" wrote:
>
>> Hello obnetadmin,
>>
>> Single forest, single domain? The you only have one PDCEmulator.
>>
>> See here about some documentation:
>> FSMO roles
>> http://support.microsoft.com/kb/223346/en-us
>> PDCEmulator
>> http://technet2.microsoft.com/Window...ce8890cf-ef46-
>> 4931-8e4a-2fc5b4ddb0471033.mspx?mfr=true
>> Client time config
>> http://technet2.microsoft.com/Window...ry/8990703a-a1
>> 97-4717-b6e5-b7406d9f91f01033.mspx
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> The only problem we have seen lately is that clients are 8 minutes
>>> fast for some reason. In my environment, we have 20 DC's. Should the
>>> PDC Emulator role only be dedicated to one DC (the first installed
>>> in the domain)?
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> obnetadmin <(E-Mail Removed)> wrote:
>>>>
>>>>> Can I set the scope option in DHCP to hand out a public NTP time
>>>>> server to clients without any additional config on the client
>>>>> side? I have a single forest, single domain Windows Server 2003 AD
>>>>> environment. All clients are XP Pro.
>>>>>
>>>>> Sean
>>>>>
>>>> Hmm - but your clients should *not* specify a public time server
>>>> with which to sync. They should be syncing only with your DC (the
>>>> PDC emulator role) if you want AD to work right. If you're having a
>>>> problem with this config perhaps you could post the details so
>>>> someone can help you address them.
>>>>

Thanks to everyone for your help.

"Frankster" wrote:

> > Can I set the scope option in DHCP to hand out a public NTP time server to
> > clients without any additional config on the client side?
>
> Don't think this has anything to do with DHCP at all. But...
>
> This is an automatic config. The workstations need to get their time from
> the PDCemulator DC. Set the PDCemulator DC to a reliable time source. You
> should not do anything to the XP workstations on the domain. They will
> automatically go to the PDCemulator for the time.
>
> When typing "net time /querysntp" on the XP client, you should see this...
>
> ---------------------
> C:\Users\frank>net time /querysntp
> This computer is not currently configured to use a specific SNTP server.
>
> The command completed successfully.
>
> C:\Users\frank>
> -----------------------
>
> If you do not see this, but instead, see that the workstations have been set
> to a specific time server, you should do this...
>
> net time /setsntp: [enter]
>
> This will eliminate any previously set time server and allow the workstation
> to automatically sync to the PDCemulator.
>
> -Frank
>
>