Windows 2000 as a NTP Server?

Hi,


We've all our domain (Win2K Servers and WinXp Wkst) sinchronized with an
external NTP server.

I'd like to use the PDC (that synchs his time with an external source) as a
NTP Server. The purpose of this is to use it for synchronizing the time of
all the devices (not PCs, just electronci devices like routers, etc..)
we've in our network.

I don't know if this is possible since Windows uses SNTP instead of standard
NTP.


Thanks in advance for your answer.

Domain Members *already* sync their clocks with the DC. Undo what you did to
make them sync with an external source. You should have left them alone the
way they started out. The only machine that should sync with an external
source is the DCs.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"NO_MSC_NO_MSCP_NO_MSENGINEER" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
>
> We've all our domain (Win2K Servers and WinXp Wkst) sinchronized with an
> external NTP server.
>
> I'd like to use the PDC (that synchs his time with an external source) as
a
> NTP Server. The purpose of this is to use it for synchronizing the time of
> all the devices (not PCs, just electronci devices like routers, etc..)
> we've in our network.
>
> I don't know if this is possible since Windows uses SNTP instead of
standard
> NTP.
>
>
> Thanks in advance for your answer.
>
>

Phillip,

thanks for your answer.

Beeing more concrete,

I want to synch a router via NTP with my DC's.

Is it possible?


"Phillip Windell" <@.> escribió en el mensaje
news:(E-Mail Removed)...
> Domain Members *already* sync their clocks with the DC. Undo what you did
> to
> make them sync with an external source. You should have left them alone
> the
> way they started out. The only machine that should sync with an external
> source is the DCs.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> "NO_MSC_NO_MSCP_NO_MSENGINEER" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi,
>>
>>
>> We've all our domain (Win2K Servers and WinXp Wkst) sinchronized with an
>> external NTP server.
>>
>> I'd like to use the PDC (that synchs his time with an external source) as
> a
>> NTP Server. The purpose of this is to use it for synchronizing the time
>> of
>> all the devices (not PCs, just electronci devices like routers, etc..)
>> we've in our network.
>>
>> I don't know if this is possible since Windows uses SNTP instead of
> standard
>> NTP.
>>
>>
>> Thanks in advance for your answer.
>>
>>
>
>

"NO_MSC_NO_MSCP_NO_MSENGINEER" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Beeing more concrete,
>
> I want to synch a router via NTP with my DC's.

I'm not sure. I suspect it would if the server follows normal "time server"
standards. I don't know, I have never had to "create" a time server,....the
DCs just naturally function as time servers for the member machines so you
never have to "do" anything.

I searched MS's site for "Time Service" and "Time Server" but didn't find
anything I thought would closely apply. Everything seems to only assume you
are dealing with a windows machine vs another windows machine,...not a
router syncing to a windows machine.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Yes..


Perhaps a third party solution will be better...

What a classic MS problem :-D

"Phillip Windell" <@.> escribió en el mensaje
news:eV48$(E-Mail Removed)...
> "NO_MSC_NO_MSCP_NO_MSENGINEER" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Beeing more concrete,
>>
>> I want to synch a router via NTP with my DC's.
>
> I'm not sure. I suspect it would if the server follows normal "time
> server"
> standards. I don't know, I have never had to "create" a time
> server,....the
> DCs just naturally function as time servers for the member machines so you
> never have to "do" anything.
>
> I searched MS's site for "Time Service" and "Time Server" but didn't find
> anything I thought would closely apply. Everything seems to only assume
> you
> are dealing with a windows machine vs another windows machine,...not a
> router syncing to a windows machine.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

"NO_MSC_NO_MSCP_NO_MSENGINEER" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Perhaps a third party solution will be better...
>
> What a classic MS problem :-D

No, I consider it a problem with the router. All the router companies are
more than fully aware of the prominence of Windows Systems and the way
Active Directory Domains work. It is their fault if they didn't build the
equivalent of a "Net Time /set" command into the router OS that could be
repeated at least once a day.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

What? IS this a joke or what?

There is a standard that has been working for years and years, without known
problems. MS decides to use a different system for HIS systems, and you say
that all the devices of the world should now change the way they synch theyr
clocks because MS decided (like allways he did) to use his own standard?

Oh please...




"Phillip Windell" <@.> escribió en el mensaje
news:%(E-Mail Removed)...
> "NO_MSC_NO_MSCP_NO_MSENGINEER" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Perhaps a third party solution will be better...
>>
>> What a classic MS problem :-D
>
> No, I consider it a problem with the router. All the router companies are
> more than fully aware of the prominence of Windows Systems and the way
> Active Directory Domains work. It is their fault if they didn't build the
> equivalent of a "Net Time /set" command into the router OS that could be
> repeated at least once a day.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>

"NO_MSC_NO_MSCP_NO_MSENGINEER" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> What? IS this a joke or what?
>
> There is a standard that has been working for years and years, without
known > problems. MS decides to use a different system for HIS systems, and
you say > that all the devices of the world should now change the way they
synch theyr
> clocks because MS decided (like allways he did) to use his own standard?
>
> Oh please...

Rubbing two sticks together to start a fire was a "standard" among
cave-dwellers for years and years,...I'm glad someone cam along and created
a new standard for that. Then there were oil lamps before
electricity,...bloodletting before medicine.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

On 2004-10-13 10:11:16 -0400, "Phillip Windell" <@.> said:

> Domain Members *already* sync their clocks with the DC. Undo what you did to
> make them sync with an external source. You should have left them alone the
> way they started out. The only machine that should sync with an external
> source is the DCs.

In certain industries, the "loose" synchronization provided by SNTP
isn't sufficient to meet regulatory or legal guidelines. In such
cases, it is necessary to use an external NTP solution instead of
relying upon Microsoft's built-in SNTP solution. In these cases, the
use of an external NTP solution does not in any way invalidate the
stability of the overall implementation, since the purpose of time
synchronization (in AD, specifically) is to support Kerberos
authentication. As long as time is being synchronized (via Microsoft's
SNTP solution or via an external NTP solution), then that requirement
is being met.

Just a few extra thoughts for consideration...

--
Scott Lowe

Thanks for your thoughts.

In fact, I need this time syncronizing for an electronic device that needs
to be validated (you know, pharmaceutical industry...).

It wouldn't be a problem if it was synchronized to a DC (i really dont care
too much for the 'loss' synch of SNTP) but I think that my NTP device wil
not be able to synch with a WIn2k SNTP server because it is not NTP
compliant...

Am I wrong?

"Scott Lowe" <(E-Mail Removed)> escribió en el mensaje
news:(E-Mail Removed)...
> On 2004-10-13 10:11:16 -0400, "Phillip Windell" <@.> said:
>
>> Domain Members *already* sync their clocks with the DC. Undo what you did
>> to
>> make them sync with an external source. You should have left them alone
>> the
>> way they started out. The only machine that should sync with an external
>> source is the DCs.
>
> In certain industries, the "loose" synchronization provided by SNTP isn't
> sufficient to meet regulatory or legal guidelines. In such cases, it is
> necessary to use an external NTP solution instead of relying upon
> Microsoft's built-in SNTP solution. In these cases, the use of an
> external NTP solution does not in any way invalidate the stability of the
> overall implementation, since the purpose of time synchronization (in AD,
> specifically) is to support Kerberos authentication. As long as time is
> being synchronized (via Microsoft's SNTP solution or via an external NTP
> solution), then that requirement is being met.
>
> Just a few extra thoughts for consideration...
>
> --
> Scott Lowe
>