Windows 2000/2003 server configured as domain controller with several 2000/XP Pro desktops joined to the domain. Server takes a dump and either needs to be physically replaced or have its Windows blown out and reloaded from scratch. Windows get reloaded with the same host name, domain name, IP address, etc. as before. In situations like this, even after adding the computer and user accounts to the new domain controller, the workstations have trouble logging in. They'll log in if you enter the domain account and password as soon as the logon prompt appears but if you wait too long, it won't accept it and instead say the DC is unavailable. DNS is working fine though. Once logged on, they can access resources on the server but accessing other hosts in the domain is hit or miss. If the domain members are disjoined and rejoined to the domain after the server is replaced, they'll work fine but that means migrating all of the user's settings over to the new profile. I'm guessing that even though the old and new server have the same host and domain name, since the SID/GUID are different, the domain members recognizes it as their domain. Is there an easy way to make they part of the "new" domain without disjoining/rejoining?