Archived from groups: microsoft.public.win2000.active_directory (More info?)
Hi,
We have single w2k domain with three sites. When the third site was created
the guys at the time took one of the DC from the main office and dumped it in
the remote site(2Mb leased line). They did not create separate site in AD
sites and services etc.
I have now created the site and subnet and move that DC. AD repl.mon. show
all OK. when I type SET in a command prompt on the exchange server in the
head office I see that logon server is a local DC.
Having said that if I type "net time" in a command prompt on my pc in the
head office - I get reply the current time is \\<name of the machine in the
remote office>. Also if that DC in the remote office crashes exchange starts
to behave erraticaly although RUS are not using that remote DC.
Any idea why those services are still depending on that remote DC?
--
George
Hi,
We have single w2k domain with three sites. When the third site was created
the guys at the time took one of the DC from the main office and dumped it in
the remote site(2Mb leased line). They did not create separate site in AD
sites and services etc.
I have now created the site and subnet and move that DC. AD repl.mon. show
all OK. when I type SET in a command prompt on the exchange server in the
head office I see that logon server is a local DC.
Having said that if I type "net time" in a command prompt on my pc in the
head office - I get reply the current time is \\<name of the machine in the
remote office>. Also if that DC in the remote office crashes exchange starts
to behave erraticaly although RUS are not using that remote DC.
Any idea why those services are still depending on that remote DC?
--
George