Can't set time server in Windows 2000 domain

I have a parent/child domain here and the parent domain controller/PDC
emulator is the time source for the parent. Then in the child domain there is
a DC in Michigan, we are in Utah that is the default time server for the
child domain. For instance if I do a net time on my machine in Utah it tells
me current time is \\baycity-dc1 is whatever time it is. Bay City being in
Michigan.

From what I read the time servers should be pointing to the parent PDC
emulator. When I tried to change the time by doing a net time \\parentdc /set
/y it defaulted to the dc in Bay City.

How can I change this to point to the parent?

Thanks

"John McCoy" <(E-Mail Removed)> wrote...
I have a parent/child domain here and the parent domain controller/PDC
emulator is the time source for the parent. Then in the child domain there
is a DC in Michigan, we are in Utah that is the default time server for the
child domain. For instance if I do a net time on my machine in Utah it tells
me current time is \\baycity-dc1 is whatever time it is. Bay City being in
Michigan.

From what I read the time servers should be pointing to the parent PDC
emulator. When I tried to change the time by doing a net time \\parentdc
/set /y it defaulted to the dc in Bay City.

I see nothing wrong with your setup.

First, the net time command is a legacy command. You should be using w32tm
command to make any changes in a Windows 2000+ environment.

1) All client desktop computers and member servers use their authenticating
domain controller as their Time server.
2) Domain controllers themselves by default look to the PDCe in their domain
as their Time server.
3) The PDCe in each domain of a multi-domain forest looks to the PDCe of the
forest root domain as it's Time Server.
4) Following this hierarchy, the PDC operations master at the root of the
forest becomes authoritative for the organization.

http://www.jsiinc.com/SUBS/tip9000/rh9006.htm

Configuring an Authoritative Time Server:
http://www.winnetmag.com/Web/Article...Web_22123.html

Time Service, Setup - good "how to" article:
http://www.windowsnetworking.com/art...e-Service.html

Windows Time Service Technical Reference:
http://www.microsoft.com/resources/d...imes_intro.asp

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Thank you for the references but that still doesn't answer my question. If I
do a net time on a DC or any workstation it points to a dc that is not the
PDC emulator. This being a parent/child domain I want the time server to be
the PDC emulator on the parent domain.

The PDC emulator on the parent domain is the time server for that domain but
not the child which is the problem.

Thanks

"Todd J Heron" wrote:

> "John McCoy" <(E-Mail Removed)> wrote...
> I have a parent/child domain here and the parent domain controller/PDC
> emulator is the time source for the parent. Then in the child domain there
> is a DC in Michigan, we are in Utah that is the default time server for the
> child domain. For instance if I do a net time on my machine in Utah it tells
> me current time is \\baycity-dc1 is whatever time it is. Bay City being in
> Michigan.
>
> From what I read the time servers should be pointing to the parent PDC
> emulator. When I tried to change the time by doing a net time \\parentdc
> /set /y it defaulted to the dc in Bay City.
>
> I see nothing wrong with your setup.
>
> First, the net time command is a legacy command. You should be using w32tm
> command to make any changes in a Windows 2000+ environment.
>
> 1) All client desktop computers and member servers use their authenticating
> domain controller as their Time server.
> 2) Domain controllers themselves by default look to the PDCe in their domain
> as their Time server.
> 3) The PDCe in each domain of a multi-domain forest looks to the PDCe of the
> forest root domain as it's Time Server.
> 4) Following this hierarchy, the PDC operations master at the root of the
> forest becomes authoritative for the organization.
>
> http://www.jsiinc.com/SUBS/tip9000/rh9006.htm
>
> Configuring an Authoritative Time Server:
> http://www.winnetmag.com/Web/Article...Web_22123.html
>
> Time Service, Setup - good "how to" article:
> http://www.windowsnetworking.com/art...e-Service.html
>
> Windows Time Service Technical Reference:
> http://www.microsoft.com/resources/d...imes_intro.asp
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
>