Recently I was assigned to create an application that takes its input via HTTP from an application that has been cultivated to operate with the latest Windows operating system release that is available within the developers section of my employer's business: XP. Since my computer runs Windows 7 Ultimate, and only with great difficulty anything earlier, I decided to use Windows Virtual PC and run XP under it. This is termed Windows XP Mode under Windows 7. In this way I am able to run the application that supplies my application with its input via their application's Web Server. Out of the box, Windows Virtual PC does not play nicely with the other computers on my LAN. The default Windows XP Mode setting was, in my humble opinion, ill-chosen. How to configure the problem away should be prominently stated but isn't. So here I am to give you the low down. Others have tried and failed to give the correct answer (see Google). Dell's premiere support service guy in a city 300 km south of Bangalore didn't give the correct answer either.
Configuring Windows XP Mode Networking to Be a Presence on Your LAN
If you logon under James then using Windows Explorer, open the folder
on the real machine (the one that hosts the virtual machine). Right click on the shortcut to the VM and click on Settings. Find Networking/Network Adapters in the table and change the setting on the virtual NIC to the name that matches the NIC hardware (e.g. RealTek) in the real (host) machine. Reboot and perform IPCONFIG /ALL on the VM to see that the VM has been assigned an IP address on the same network as the real machine. (11/12/10)
@earnshaw: By default XP mode is configured for NAT, if your require incoming access to the VM then you need to do as you say. XP mode is primarily for software compat, and most software only needs outgoing access, so the default NAT'ed configuration is well chosen in my opinion, it is the most likely to work for outgoing access in all situations.
This is the first search hit for 'xp mode networking' btw.
Emmm... I thought I know about that since VPC 2004... Nothing really new...
And to add to the solution said, if your network card do not show up in the VM settings screen, you should check the network adapter setting and see if the NIC you want to share have something like "Virtual PC Network Filter Driver" installed and selected.
For the "Default to use NAT" thing, I think this might have something related to ISPs.
There's some ISPs that support direct internet connection (i.e.: connect without need to sign in). If the default connection type is "bridged" connection, the local DHCP server would just assign a public IP to the VM too. Since most DHCP in building's network control room have only assigned public IP numbers near to the actual subscribers, if each user have 1 VPC instance running (wthut boardband sharing router in between) the local IP pool would soon be exhausted.
Of course, hiding behind NAT has firewalled like effect is another advantage,
Quite a lot of ISPs have MAC address restrictions, in which case they wouldn't let the VM get an IP at all.
Anything other than NAT as the default would lead to VMs without Internet connectivity in a lot of situations. NAT really is the only safe default.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.