<div>
Basic troubleshooting. Narrow down the cause. Right now you've listed two distinctly separate possibilities. <br />
<br />
What doesn't work: XP on the network.<br />
Wart does work: win7 vm on the hyper-v server.<br />
<br />
Is the OS the problem or the network?? Does win7 on the network work? What about XP vm on the hyper-v server? <br />
<br />
Not enough information or troubleshooting has been done to even remotely suggest a cause or solution.
</div>


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.

<div>
I made a mistake by not adding the PCs to the domain before trying to log in as a user. &nbsp;The old domain was named the same (we're just updating the server and exchange instances to something more recent). &nbsp;Perhaps that's why I skipped this step.<br />
<br />
Lesson learned....
</div>


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

<div>
<div class="content wysiwyg-content">
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.<br />
<br />
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.<br />
<br />
A Win7 VM in the Hyper-V server CAN connect without issue,<br />
<br />
Suggestions please....
</div>
</div>


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

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

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.

Windows Networking

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.