Nuo Yan

Problem Solved

Recent Posts

Tags

News


  • Follow me on twitter: @nuoyan
    Make a donation to this Blog by PayPal. Thanks!






    Nuo is currently a Software Development Engineer in a Seattle-based software company.




    Locations of visitors to this page

    The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my school or employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion. All code samples are provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.


Community

Email Notifications

Archives

Add NICs to Existing Virtual PC

Virtual PC is a fantastic tool to help us build test or experimental environment of Windows Server System.

Suppose now we are building a test environment for Windows Server 2003 and its updates. The purpose is to simulate the company's real network environment and test the Service Pack and other updates.

We setup the workstations, member servers and domain controllers on Virtual PC successfully. The next step is to make the scenario as same as the real life environment. We begin to build the Network Address Translation (NAT) server. At this time, we need 2 NICs on the virtual machine. However, by default after installation, there is only one in this virtual Windows Server 2003 and there is only one real NIC in the host computer.

How can we do that? How can we add another NIC to the Windows Server 2003 virtual machine so that we could simulate the real life NAT environment?

Actually we could finish this work within a minute. First, shut down the virtual machine we need to add NICs to. Then start Virtual PC 2004, click the virtual machine we need to add NICs to.  Click “Action”, then click “Settings...”. On the new dialog box, click “Networking”. In the right pane, click the dropbox on the right of “Number of network adapters” and choose the total number of NICs we want in this system. Note, here is to choose the total number of NICs we want in this particular virtual machine, but not to choose the number of NICs we want to add to this particular virtual machine. Then we will need to set the scope of the added NIC(s). “Local only” means the particular virtual NIC could only have network connection with virtual machines on the same host computer. We could see another option is the name of the host NIC (we assumed only one NIC in the host computer), this option means the particular virtual NIC could have network connections with virtual machines on the same host computer, the host computer, and computers connectted to the host computer through the host's NIC. If we're configuring the first virtual NIC on a virtual machine, we also can see another option called “NAT”. It's almost the same meaning as the real life NAT concept. After configuring the virtual NICs, click “OK” to close the dialog box.

We've done. Turn on the particular virtual machine we've just configured, we will see another LAN interface is right there. Then we could do the simulation of the real life environment, for instance, the NAT environment, and continue testing the Service Pack and updates in the simulated environment.

To learn more about Virtual PC 2004, please visit:

http://www.microsoft.com/virtualpc 

 

Comments

Irfan said:

In Virtual PC 2007 try this:

Stop emulation. Go to settings then click network and try to increase the number of network cards to "2" and selected a new network card from the list.

Start your XP emulation. As Windows loads desktop it detects new hardware for ethernet. Check network connections there is a duplicate network connection don't worry if it shows same old brand. Just disable "OLD" connection and use the new one. It'll connect you to the network.

(Actually my case was that when I installed XP on VPC HDD I had INTEL's lan card. Later I replaced it with CNet Pro. But when I started back my VPC it showed error/warning saying "previous NIC was not found." The emulated Windows XP did'nt detected any new NIC upon loading or from hardware detection utility. The above procedure worked for me perfectly.

# December 10, 2008 2:41 AM

Patrick Mahoney said:

Hello Nuo,

I am a fellow MCP,soon to become an MCSA, I have a question: I have a dual boot server 2003, on bare metal, directly on this machine I have 1 VM Server,

hosting Serv. 2003.  I have another "PC" hosting a few more server 2003 virtuals, and a few virtual xp's.

I took your advise on creating each of these a second

NIC that connects with an actual hard NIC on eac machine.  I am attempting create a "Router" on one of the Virtual Servers, via "RRAS", so I can have each LAN segment communicate with the other. I have now only 1 physical router, a Linksys, WRT300-N, with a gateway of; 192.168.1.1, I will need an additional gateway, and a way for the 2nd LAN: 192.168.2.0 to communicate. Any thoughts?

Regards,

Patrick Mahoney, MCP, Net+, A+,

expdata_07@live.com

# March 17, 2009 9:44 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)