This computer could not authenticate with a Windows domain controller

I imaged a server running Sharepoint 2007. I powered the original down.

I copy the image to another like server and powered it up. Its been running for 3 months when accidently the other server which had the same image was powered up (and then immeadiatly down when it was discovered it was up).

Now I am getting all sorts of error:
This computer could not authenticate with \\domaincontroller.domain.org, a Windows domain controller for domain DOMAIN, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator.

I am unable to log in using any domain account - I can only log in with the administrator account.

Whenever I go into Groups in the management console, they come up as S1-2-15 etc not the actual user.

GPEDIT.msc doesnt work - Gives me "MMC Could not create the snap-in."

The original server was powered down and decommisioned.

Any ideas?
LVL 1
Dr_EgoAsked:
Who is Participating?

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

x
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.

PCHoundCommented:
I would go to your DNS and see if you have a pointer pointing to the old server. It's highly possible that the 2 IP's are in DNS as the same server with different address's. Which in the sense would be a case of mistaken identity. Hope this help's....
0
MightySWCommented:
Well, it sounds like your SID is trashed.  This usually happens when you clone things.  The next time you image something like this be sure to run a SID changer.  You can try to now, but I think that it is too late.

Delete the computer/server account from AD and join the Server back into the domain again.  After you are back in the domain, be sure to move that server object to your correct OU.

HTH
0

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
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.