Re: Time Server - synching with an external source
From: Stefan Buchman (stefan2002b_at_yahoo.com)
Date: 04/23/04
- Next message: John Woodward: "Client Machine Account replication delays"
- Previous message: Stefan Buchman: "Re: logon failures - system's computer account in it's primary domain is missing"
- In reply to: Microsoft NewsGroups: "Time Server - synching with an external source"
- Next in thread: Rick Chisholm: "Re: Time Server - synching with an external source"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 23 Apr 2004 12:37:14 -0400
There is no real risk doing this. Since you are initiating the call you
can manage it using a pinhole rule on your router for the NTP port
(TCP/123) just don't allow outbound initiated connections to that server
for NTP.
- Stefan
Microsoft NewsGroups wrote:
> Seems like I remember reading somewhere that there was a "security risk"
> involved when synching with an external time server source such as a atomic
> time service on the Internet. Is this true, and what is the risk?
>
> What do others do to keep their internal time server accurate?
> Thanks
>
>
- Next message: John Woodward: "Client Machine Account replication delays"
- Previous message: Stefan Buchman: "Re: logon failures - system's computer account in it's primary domain is missing"
- In reply to: Microsoft NewsGroups: "Time Server - synching with an external source"
- Next in thread: Rick Chisholm: "Re: Time Server - synching with an external source"
- Messages sorted by: [ date ] [ thread ]