Re: Testing NTP on Win2003
- From: "Neteng" <neteng.ccie@xxxxxxxxx>
- Date: Fri, 24 Jun 2005 12:02:12 -0500
It listens on UDP port 123. With UDP you don't establish a connection
(unlike TCP), so port scanning or telnetting to the port will not work. If
you check the system event log of your client it should have a W32Time entry
with a description something like the following:
The time provider NtpClient is currently receiving valid time data from
YOURPDC(ntp.m|0x1|192.168.13.22:123->192.168.13.200:123).
<jwgoerlich@xxxxxxxxx> wrote in message
news:1119630006.539180.118450@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thank you for the reply. The DC's W32Time service is running, no
> time-related warnings or errors in the logs, and Windows computers are
> syncing their time.
>
> And yet, from a TCP/IP perspective, NTP does not appear to be running
> on the DC. How can I tell if the DC is listening and responding to NTP
> traffic?
>
> J Wolfgang Goerlich
>
.
- References:
- Testing NTP on Win2003
- From: jwgoerlich
- Re: Testing NTP on Win2003
- From: Neteng
- Re: Testing NTP on Win2003
- From: jwgoerlich
- Testing NTP on Win2003
- Prev by Date: Re: Testing NTP on Win2003
- Next by Date: Re: NTDS errors 1528 and 1373
- Previous by thread: Re: Testing NTP on Win2003
- Next by thread: Re: Testing NTP on Win2003
- Index(es):
Relevant Pages
|
Loading