Re: W2K client logonserver in the wrong site (native w2003 domain)

Tech-Archive recommends: Fix windows errors by optimizing your registry


> How were they 'moved'

Installed in Site1 . (where the IT & Field Service Engineers are located)
Put in a lorry and transported to site2.
There was a DC configured for site2 (subnets, dns, dhcp settings modified,
....)

> If the site was wrong it should have been reconfigured. Clients will then
> pickup the new info at next boot (when they perform a lookup).

Some of the clients windows2000 found their "local" domain controller, other
clients are still conecting to the DC of site1.

a real headbreaker is that we have 14 sites in total, an they are not
contacted.
So it seems that these clients are keeping the DC of site1 in their cache or
someting like that? Is it possible that these clients need several boots
before they will find the dc of site2? Can i enable some kind of logging on
the windows2000 clients that logs the logon process of the computer$ account?


.

Relevant Pages