VMWare, VMWare Player, virtualbox, Windows Virtual PC and other virtual machine software are provided
Network Address Translation (NAT) and
Virtual machines cannot connect to external networks.
Quasi-network.
After virtualbox is installed, only one host-only virtual network card is created. Both the bridge and Nat functions properly.
After windows Virtual PC (XP mode in win7) is installed, no virtual network adapter exists, except for bridging
The network type and the host cannot access the services of the XP Virtual Machine through the IP address. Of course, the ping fails, and the Network Function
Relatively weak.
VMware is normal.
After VMWare Player is installed, only two virtual NICs, vmnet1 and vmnet8, are available.
Adapter vmnet0, that is, the bridge network cannot be used. The following is a description of the VMware Virtual NIC:
Network type network adapter name
Bridged vmnet0
Nat vmnet8
Host-only vmnet1
At present, the system uses a variety of Virtual Machine Software, how can we make VMWare, VMWare Player, virtualbox,
Windows Virtual PC and other virtual machine systems can access each other? Only Bridging networks can be used.
In the above Virtual Machine Software, only VMWare Player cannot use the bridge network normally. How can this problem be solved?
Do not consider bridging as adding a vmnet0 virtual network card! The solution is to add a network service,
Taking Windows 7 as an example, [Control Panel \ network and Internet \ Network Connection]
Right-click "Local Connection", "properties -- Network -- installation -- service -- add -- install from disk
-- Browse ", then go to the installation directory of VMWare Player, and select the netbridge. inf file, such
C: \ Program Files (x86) \ VMware Player \ netbridge. inf
After confirming, the "select Network Service" window appears. Select the network service "VMware Bridge Protocol"
After confirming again, confirm that the network service is selected. After the system is restarted
Commonly used virtual machine settings -- hardware -- network adapter --
Network connection -- bridged: connected directly to the physical network ).
Note: add the network service VMware bridge to any physical NIC (local connection or wireless network connection ).
All protocols are supported.
Because VMWare Player cannot specify a physical Nic for bridging, an error occurs when the network is switched.
For example, if the wireless network adapter is changed to wired and disabled, replicate is used for bridging or record the network adapter in the previous status.
Replicate indicates that vmnet0 is not started. Therefore, when switching a physical network, you do not need to disable the NIC.
If you do not select "VMware Bridge Protocol" in the NIC attributes, it is a little troublesome!
Original solution address:
Http://communities.vmware.com/thread/37514? Start = 15 & tstart = 0
Problem:
Network Bridge on device vmnet0 is not running
After installing VMWare Player, and starting the player I get
Following message:
The Network Bridge on device vmnet0 is not running. The Virtual Machine
Will not be able to communicate with the host or with other machines on
Your network. Virtual Device ethernet0 will start disconnected.
I have attempted to renew the IP address by running ifdown, and IFUP,
But do not get a response. Any suggestions?
Solution:
As for the other person still having trouble (?) You might note that when
You go into your local area connection properties, and click "Install ..."
It's actually a "service" that you want to install, (not a Protocol) and
You shoshould see "VMware" there and just be able to select it on the left,
And select "VMware Bridge Protocol" on the right... (as in, you shouldn't
Have to browse for an. inf) Then reboot.
Address: http://oicu.cc.blog.163.com/blog/static/12303947120117174842427/