XP clients on network cannot connect to Windows Server 2012 running in hyper-v - help!!!

We have a Windows server 2012 running in hyper-v 2012 but our XP Pro machines on the network act like they cannot see the domain controller.

This is the case even when we log in to the local XP Pro PC and manually enter the IP address of the Windows Server 2012 Domain Controller.

A Win7 VM in the Hyper-V server CAN connect without issue,

Suggestions please....
asciiassasinAsked:
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.

Cliff GaliherCommented:
Basic troubleshooting. Narrow down the cause. Right now you've listed two distinctly separate possibilities.

What doesn't work: XP on the network.
Wart does work: win7 vm on the hyper-v server.

Is the OS the problem or the network?? Does win7 on the network work? What about XP vm on the hyper-v server?

Not enough information or troubleshooting has been done to even remotely suggest a cause or solution.
0
asciiassasinAuthor Commented:
My bad...I hadn't added the machines to the domain so there was a trust issue with the Domain Controller.  The only way I caught this was by trying to add a Windows 7 Pro PC and it showed a message stating that there was an issue with a security database.

Then, some of the machines no longer had the default local admin passwords - so we had to download a linux cd to boot into and blank out the administrator passwords before we could log in and add the machine to the domain.

After that, everything seemed to work for all PCs except one that had a WINS entry that had to be deleted before it could be joined to the domain.
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
asciiassasinAuthor Commented:
I made a mistake by not adding the PCs to the domain before trying to log in as a user.  The old domain was named the same (we're just updating the server and exchange instances to something more recent).  Perhaps that's why I skipped this step.

Lesson learned....
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
Windows Networking

From novice to tech pro — start learning today.