Windows Mobile emulators in Hyper-V internal network Win2008 R2

  • Article

 2 items that will help WM emulators on Hyper V clients in Win2k8 R2…

 

1. upgrade the HyperV integration services

2. enable MAC address spoofing on the VM in network adapter settings

 

Here’s the details:

 

I just upgraded my VMs from Win2k8 to Win2k8 R2 RTM. I have my lab environments running in private networks to not interfere with our primary network. I haven’t confirmed if this same symptom affects VMs on the External virtual network connection type. My emulators were working fine before the upgrade, but after I was unable to get DNS proxies to GCs in the internal network.

 

The first part I needed to do was in the upgrade documentation. You need to rerun the Integration Services Setup from the virtual machine connection. There are helpful event ids 27 and 6 on the Sys log of the parent partition that help clue in this resolution.

 

Log Name: System

Source: VMSMP

Date: 8/10/2009 8:40:29 PM

Event ID: 27

Task Category: None

Level: Warning

Keywords: Classic

User: N/A

Computer: mcCSIlab

Description:

Networking driver on '01XP' loaded but has a different version from the server. Server version 3.2 Client version 0.2 (Virtual machine ID 8AF758FA-CA92-4583-BAE0-45360776EEDA). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

 

The second portion to fix was a bit more difficult to find. I saw ARP requests in Netmon that were never answered. This clued me in that the problem was with MAC addresses.

I’ve confirmed the resolution was to enable this setting –

 

MAC address spoofing

 

So, it appears native security for the Win2k8 R2 Hyper-V clients is heightened to prevent MAC spoofing by default – MAC spoofing is exactly what the WM emulator does with the VPC network drivers to use the Hosts network card [which in this case is a client partition in Hyper-V].

 

I hope this helps!