Hi,
The virtual machine may not be able to communicate with the host or with other machines on your network.
I am running Windows server 2003 32 bit STD operating system as a virtual machine in my Laptop. I am not able to communicate with my base machine (running WIN 7 OS). I have set the Virtual adapter as Bridged, Eventhough i am notable to commuicate
When i am powering on my Virtual machine its prompting me a message as "The Network bridge on device VMnet0 is temporarily down because the bridged ethernet interface is down
Could anyone assist me 🙂
Thanks in advance
Regards,
Mohan
Who needs to access the VM? Only the host or other (external) machines in the network?
Does the VM need access to the network (e.g. Internet)?
Did you assign a dedicated NIC (physical NIC, WLAN) to the Bridged network in the "Virtual Network Editor" or is it set to automatic?
André
1.Who needs to access the VM? Only the host or other (external) machines in the network?
Only the Host
2.Does the VM need access to the network (e.g. Internet)?
Yes, I wanted to connect the VM to internet
3.Did you assign a dedicated NIC (physical NIC, WLAN) to the Bridged network in the "Virtual Network Editor" or is it set to automatic?
I set it as automatic
I have attached the screenshot of the settings - FYI
Mohan
With the requirements you describe, NAT would be the best choice. Bridged may work too, if you are connected to a network.
Regarding support: Workstation 6.x is only supported up to Windows Vista.
André
Automatic bridging does NOT work on hosts with two network cards - or in case where you change between local LAN and WLAN
set vmnet0 to bridged to your local LAN networkcard
set vmnet2 to bridged to your WKAN nic
then you can in future simply switch from vmnet0 to vmnet2 in case vmnet0 is not connected