Windows 2008 R2 server loses connection to Active Directory

active-directorywindows-server-2008-r2

One of our many 2008R2 servers constantly loses connection to the domain, meaning that users cannot login to shares etc on the server, and it basically becomes useless.

The event sometimes generated by the server when this happens is 3210 with the error code 0xC0000022.

This does however not always happen.

Running NETDOM RESETPWD /Server:AD01 /UserD:domainadmin /PasswordD:domainadminpassword makes it work again until it dies again. Sometimes minutes after, sometimes days after.

We have also tried the usual unjoin/rejoin domain on the server, without success.

This is happening 4-6 times a day at the moment, so it is quite a big issue.

The only services run by the server are file sharing and printing services.

Best Answer

I have been experiencing this problem as well. The stop gap solution I have found is restarting the SERVER service from the Services Control Manager. Obviously it's not a solution, but it keeps me from having to reboot servers every few days.

Related Solutions

Windows Active Directory – Command Line to List Users in a Group

try

dsget group "CN=GroupName,DC=domain,DC=name,DC=com" -members

Active Directory Naming – Best Practices for Windows Active Directory Naming

This has been a fun topic of discussion on Server Fault. There appear to be varying "religious views" on the topic.

I agree with Microsoft's recommendation: Use a sub-domain of the company's already-registered Internet domain name.

So, if you own foo.com, use ad.foo.com or some such.

The most vile thing, as I see it, is using the registered Internet domain name, verbatim, for the Active Directory domain name. This causes you to be forced to manually copy records from the Internet DNS (like www) into the Active Directory DNS zone to allow "external" names to resolve. I've seen utterly silly things like IIS installed on every DC in an organization running a web site that does a redirect such that someone entering foo.com into their browser would be redirected to www.foo.com by these IIS installations. Utter silliness!

Using the Internet domain name gains you no advantages, but creates "make work" every time you change the IP addresses that external host names refer to. (Try using geographically load-balanced DNS for the external hosts and integrating that with such a "split DNS" situation, too! Gee-- that would be fun...)

Using such a subdomain has no effect on things like Exchange email delivery or User Principal Name (UPN) suffixes, BTW. (I often see those both cited as excuses for using the Internet domain name as the AD domain name.)

I also see the excuse "lots of big companies do it". Large companies can make boneheaded decisions as easily (if not moreso) than small companies. I don't buy that just because a large company makes a bad decision that somehow causes it to be a good decision.

Best Answer

Related Solutions

Windows Active Directory – Command Line to List Users in a Group

Active Directory Naming – Best Practices for Windows Active Directory Naming

Related Topic