<div>
Looks like something's wrong with your xp vm, since you should be able to ping from it with either an internal or private network (firewall on, integration services not installed, bad tcp/ip config, bad virtual network config, using vlans, etc.?).
</div>


Looks like something's wrong with your xp vm, since you should be able to ping from it with either an internal or private network (firewall on, integration services not installed, bad tcp/ip config, bad virtual network config, using vlans, etc.?).

<div>
<div class="content wysiwyg-content">
I have a server 2012 host with hyper-v role enabled. There are 3 physical nic on the host. I assigned1 dedicated for the host. one for domain controller, and the other one for XP VM.<br />
<br />
I created another test windows xp VM, just wanted to see the difference between internal and private network. with private network, I cannot ping from the xp and cannot ping from the host. I then assigned the test xp machine to Internal network, and I got the same result!<br />
isn't it supposed to be able to ping the machine from the host?? the host has static ip 192.168.10.130 and the test xp machine has static ip 192.168.10.5<br />
<br />
I changed the virtual switch to external and I can ping right away. so what is wrong here?
</div>
</div>


I have a server 2012 host with hyper-v role enabled. There are 3 physical nic on the host. I assigned1 dedicated for the host. one for domain controller, and the other one for XP VM.

I created another test windows xp VM, just wanted to see the difference between internal and private network. with private network, I cannot ping from the xp and cannot ping from the host. I then assigned the test xp machine to Internal network, and I got the same result!
isn't it supposed to be able to ping the machine from the host?? the host has static ip 192.168.10.130 and the test xp machine has static ip 192.168.10.5

I changed the virtual switch to external and I can ping right away. so what is wrong here?

Hyper-v: difference between private and internal network

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Virtual machines are created and managed through a web-based interface that relies on Internet Information Services (IIS) or through a Windows client application tool called VMRCplus. Features included Linux guest operating system support, Virtual Disk Precompactor, symmetric multiprocessing (SMP), x64 host operating system support, the ability to mount virtual hard drives on the host machine and additional operating systems support, including Windows Vista, and a volume shadow copy writer.

Microsoft Virtual Server

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.

VMware

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.