Time server

I wonder if anyone can help. I have 2 DC's in an windows 2000 active
directory forest, both DC's have different times, 7 minutes apart. I am
unable to get them to synchronise. The DC that holds the PDC fsmo has the
incorrect time, as do all pc's on the domain. The other DC, which is holding
no roles has the correct time.
I have set the incorrect Dc to get it's time from the net using the following
net time \\dc-name /setsntp :ntp.cs.tcd.ie
This runs succesfully but the time does not correct itself,

I have tried to syncronise the DC with the correct time, to the other DC by
using the w32tm but it keeps the correct times.
The DC with the PDC role is giving the following error


Because of repeated network problems, the time service has not been able to
find a domain controller to synchronize with for a long time. To reduce
network traffic, the time service will wait 960 minutes before trying again.
No synchronization will take place during this interval, even if network
connectivity is restored. Accumulated time errors may cause certain network
operations to fail. To tell the time service that network connectivity has
been restored and that it should resynchronize, execute "w32tm /s" from the
command line.

The DC with the PDC role is giving the following error


any help would be much appreciated
.

Relevant Pages

  • Re: NT PDC can no longer administer users it its own domain but can in others.
    ... >> The network in question has been up and running for many years..... ... >> The PDC also had the NT Gateway for Netware service installed, ... >> However I get the same error message every time I try to select the PDC's ... >> I can go to the BDC and try to bring ...
    (microsoft.public.windows.server.general)
  • Re: ADMT TcpipClientSupport registry key NT 4.0 to AD
    ... I would take a network trace of the failure and see where it fails. ... > but I keep getting this error message "Either the source> domain's primary domain controller (PDC) has not been re-> started after setting the tcpipClientSupport registry key> to 1 or the PDC could not be contacted." ... > I have discarded the communication problem between the NT> 4.0 server and the Windows 2003 server because when I do> not select "Migrate user SIDs to target domain" the> migration is successful. ...
    (microsoft.public.win2000.active_directory)
  • workstations have problem with login after upgrading nt4 to w2k with AD and DNS
    ... We have a pretty small network that had a NT4 PDC and about 30 client ... To perform the 2k AD upgrade, I bought a server and installed NT4. ... I synchronized the new BDC with the PDC successfully. ... Now the problem is when I try to login from a client machine, ...
    (microsoft.public.windows.server.migration)
  • Re: Cant join domain: Network path was not found
    ... trying to join the domain 'hq.infotouchsys.com': Network path not ... I have a single server running as the primary domain controller (PDC) ... the registry tweaked to allow joining a domain.) ...
    (microsoft.public.win2000.active_directory)
  • Re: New PDC...
    ... Thank you, yeah the old PDC is pretty badly jacked up for one, and two, ... The network is very small. ... > working, create duplicate user accounts, and then add the XP systems in ... > manually at the workstations themselves. ...
    (microsoft.public.windows.server.general)
Loading