Domain trust lost after moving virtual machine to new box

I have moved a VM from one physical box to a new one. Seemed to go fine but after a few hours I was not longer able to access any shares on the server. When I go into a second server and into active directory trusts and domains I get an error that the PDC emulator cannot be contacted.
scokerAsked:
Who is Participating?
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.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Does the VM on the new one, have correct network access ?
0
scokerAuthor Commented:
I just moved the VM from on box to another I thought everything would be exactly the same. I can ping the box by name just can not connect to any shares other than on the local box.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The virtual hardware will always be the same possibly, but networking could be different.

I think you need to explain, how it was moved, OS, Host OS etc
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Download your Guide
scokerAuthor Commented:
The VM is a Windows 2003 Server. I used VMware converter to move it from one box to another. The issue seems to be a trust relationship issue. When I have the vm on the new physical server I get an error  and a red X over active directory and domains and trusts. When I fire up the vm on the old box no red X and everything works.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Why are you using VMware Converter, to move a VM?

Why not just shutdown the VM, and Export it ?

VMware Converter, will convert the VM, and you will need to add all the Network Settings back, also did you Convert the VM whilst it was powered up?
0
scokerAuthor Commented:
To export it would add an extra step of importing it. Using the converter allows me to just send from one VM box to another. All of the network settings transferred fine
0
scokerAuthor Commented:
This is I believe the root of my problem
trust-error.png
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
did you P2V (VMware Converter) a live virtual machine ? If you did replication is probably broken.

Turn off the VM, and then Convert or Move.
0
scokerAuthor Commented:
No V2V and it was off when I moved it.
0
scokerAuthor Commented:
I have come to the conclusion the trust relationship is a by product of the 2 DC's not able to communicate
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, so the VM was off when moved.

If the VM was off, and moved, and powered back on, it should be in the exact same state, when you power it back on.

can you ping both DCs

repadmin /replsum - what is the output

have you tried dcdiag ?

What is the VMware Product ?

Upload a screenshot of networking ?
0
scokerAuthor Commented:
You would have thought so and it did work perfectly for a few hours. I can ping both DC's.  I think the easiest thing to do is to demote my 2012 then  clean up the metadata and promote it again.  Unfortunately I can not run any diagnostics at everyone is back to work so I fired up the old VM. VMWare is Vshpere 6.0
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
Will SzymkowskiSenior Solution ArchitectCommented:
What I would recommend is that you check your DC replication. Use the following commands below...
repadmin /replsum
repadmin /showrepl
repadmin /bridgeheads
DCDiag /v
Netdom query fsmo
Netdom query dc

I would also check and make sure that your AD Sites and Service is correct as well.

Post back results.

Will.
0
scokerAuthor Commented:
Easiest thing to do is just demote then promote.  Thanks contributors
0
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
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.