Windows 2003 Server Computer name disapprered, Netlogon error Event 5721

Our file server running windows 2003 standard OS becomes inaccessble since today.
we are getting Netlogon error 5721,
The data on file server is available but its not accessible, gives trust relationship error
We checked in DC and found that the computer name is not present, we check in Deleted Objects container but its not found there.
We checked and found that SPN entries are also missing
We have windows 2012 R2 AD server with domain functional level 2008 R2

Pls advice
Haris KhanAsked:
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.

Chris MillardCommented:
If the trust relationship has failed, can you attempt to re-join the server to the domain?
Haris KhanAuthor Commented:
HI Chris,
Its a File server and have shared folder with security permission defined on it.
If i will disjoined it will loose the permission.
any other solution pls
Chris MillardCommented:
I'm not suggesting you dis-join it first, just re-run the process of joining to the domain to get the trust back. Also, why will it lose the permissions on the shared folders? However, just in case, you can follow this article in order to backup and restore the share and NTFS permissions first:-
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
What you need to do is the following to ensure no rights are changed:

- Go to computer properties, click on Change Settings, click on Change...
- If the domain is displayed in FQDN (i.e. mydomain.local) then change it to NetBIOS domain name (i.e. mydomain).  Do the reverse if it shows just the NetBIOS domain name
- As you never leave the domain, all permission rights should stay intact (I have done it on MS SQL Server as well as IIS server)

Most likely the issue in your case is that someone inadvertently deleted the computer account.  After following steps above, you need to run setspn and created required SPNs.  Once the computer is created in AD, you should move it out of Computers OU if the server was in a different OU.

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
INstead of disjoing the computer from the domain why not Create the Computer Account In AD the run netdom on the file server to resyn its computer account password with the new AD computer object
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
What compdigit44 is saying is true, however, what I have recommended has worked for us flawlessly whereas we have had issues with running NetDom.
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 2003

From novice to tech pro — start learning today.