asked on

AD computer object is missing suddenly, why?

This is using mixed Windows 2003 and 2008 AD Domain. There are 1 W2K3 and 2 W2K8 DCs. However, a computer object of one of the newly-created file server that created 2 months ago was found missing. It can't be find in AD Users and computers MMC of any of the 3 DCs. But, if i type "net view" in any PC, I managed to see the filesvr, and I still able to browse to any file shares on the server.

I did tried to dis-join this fileserver from the domain, reboot, and then re-join it back to the domain without problem. However, still can't find the computer object in the AD, why? What is went wrong with the server? How can I get back the computer object?

Thanks.

MichaelBalack

ASKER

I typed "set" and found that this server is contacting one of the DC called filesvr2 as logonserver. This server has replication problem to the rest of the 2 DCs - mail1 & dc01. Replication between mail1 & DC01 is working fine. Should I change the logonserver to DC01 or mail1? One thing bothers me is the primary and secondary dns for this server are pointing to mail1 & dc01, respectively. But, why it still contacting filesvr2 as logonserver?

arnold

enumerate all computers in the AD, it likely was moved to a sub OU..
dsquery computer | find /i "computer name"
depending on how many you have, it might be that it was attached to a differently named object.

Try this, use the system you can not find to access another systems admin share that is commonly not used as a fileserver with a share, then see how this system is reflected on that system's share accessing interface (compmgmt.msc sharing/fileserver role.)

arnold

you can not control the logon server, it is determined by a dns query on the local server locating available DCs using a srv record lookup.

Your best bet is to identify and resolve the issues causing the replication issues.

compdigit44

On the problem DC you could demote it... Make sure AD is clear of all metadata then pro-mot the server again

ASKER CERTIFIED SOLUTION

arnold

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

MichaelBalack

ASKER

Hi Arnold,

Let's me take some time to read through all suggestions. I'll get back to you.

MichaelBalack

ASKER

Eventually, I demoted the DC because this DC having ad replications failure with other 2 DCs. Thanks for Arnold's explanation and pointed the correct culprit.