Clients falling off the domain

[Joe]

When we have to reload network client PCs, we prefer to
reuse the computer names. However, we frequently have
problems adding computers to the domain, only to have
them "fall off" a short time later. Our current procedure
is to delete the computer account from the domain, allow
at least 30 minutes for full replication across all DCs in
the enterprise, then try and add the PC back to the domain
reusing the computer name. If the computer "falls off", we
just login using an admin acct, drop it back into
workgroup, then readd to domain, and usually that's the
end of it, but it is annoying and TIME CONSUMING to have
to do this little dance all the time. LAN is resistant to
having to force manual replication on the domain everytime
a client is removed (understandably so. Is there anything
else that might be causing these PCs to fall of the
domain, or anything else we can do to prevent this from
occuring in the future?

 

[ptwilliams]

If these are 'falling off' the domain, it is probably down to the secure
channel becoming seriously out of sync. Which is probably down to a DNS
issue if the machines are on the LAN.

How are the clients configured for DNS? How many DNS servers and DCs do you
have? Have you noticed any errors or warnings in the Directory Services
and/ or File Replication Service event logs (on the DCs)?

--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


When we have to reload network client PCs, we prefer to
reuse the computer names. However, we frequently have
problems adding computers to the domain, only to have
them "fall off" a short time later. Our current procedure
is to delete the computer account from the domain, allow
at least 30 minutes for full replication across all DCs in
the enterprise, then try and add the PC back to the domain
reusing the computer name. If the computer "falls off", we
just login using an admin acct, drop it back into
workgroup, then readd to domain, and usually that's the
end of it, but it is annoying and TIME CONSUMING to have
to do this little dance all the time. LAN is resistant to
having to force manual replication on the domain everytime
a client is removed (understandably so. Is there anything
else that might be causing these PCs to fall of the
domain, or anything else we can do to prevent this from
occuring in the future?

 

[Oli Restorick [MVP]]

Check the DNS settings on your domain controllers and your workstations. If
you're in any doubt as to how to configure it, post the results of
"ipconfig /all" from all your DCs and an example workstation to the group,
tell us whether you're using AD-integrated DNS and we can see if there's a
problem.

Regards

Oli