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?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MichaelBalackAuthor Commented:
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?
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.)
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.
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

On the problem DC you could demote it... Make sure AD is clear of all metadata then pro-mot the server again
What is this server, demoting as a means of repair could result in loss of data, I.e. Changes requested by users while logged in to that DC will be lost.
Identifying the cause for the system being out if sync, might identify some other issues.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MichaelBalackAuthor Commented:
Hi Arnold,

Let's me take some time to read through all suggestions. I'll get back to you.
MichaelBalackAuthor Commented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.