Testing NTP on Win2003

We have a Win2003 Active Directory. The DC hosting the PDC FSMO is the
primary NTP time source for both the Windows network (by default) and
the non-Windows servers. We are troubleshootin a few minor problems on
the non-Windows side.

How can we confirm that NTP is active on the DC? Port scans show that
port 123 is not listening. Also, telnet'ing into port 123 fails to
connect. Any suggestions?

J Wolfgang Goerlich

.

Relevant Pages

  • Re: Testing NTP on Win2003
    ... > We have a Win2003 Active Directory. ... > primary NTP time source for both the Windows network and ... > the non-Windows servers. ... > port 123 is not listening. ...
    (microsoft.public.windows.server.networking)
  • One way AD replication problem (Continued)
    ... both domain controllers. ... Used ldap to look at the GC through port 3269. ... Set the primarydc to be a global catalog server again. ... Using active directory Users and computers I deleted the computer ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADAMs LDAP ports configuration
    ... SDE, Active Directory Core ... > to assign the LDAP port numbers through Active Directories ... > 2003 server but not in Windows 2000 server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: RDP w/ Local Network Printer on Remote Client
    ... doing so I could list my printers in the active directory but no one could ... standard tcp/ip port along with a few other printers. ... client setup to allow the remote client to print to the local printers. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: RDP w/ Local Network Printer on Remote Client
    ... After doing so I could list my printers in the active directory but no one could install them or even view their properties. ... we have a network printer that is connected via a standard tcp/ip port along with a few other printers. ... We have the RDP client setup to allow the remote client to print to the local printers. ...
    (microsoft.public.windowsxp.work_remotely)