Yesterday one of my VMware virtual machines decided it wasn’t a good day to connect to internet and refused to use the macosx network bridge. When trying to enable the network bridge, I received the following error message:
The network bridge device on /dev/vmnet0 is not running
A quick online search revealed me multiple solutions but the most of them were targeting VMware 1.0. The error above in WMvare 2.0 or greater can be easily fixed typing the following command in the Terminal (thanks Aaron).
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart
After a few seconds your virtual machine should automatically reconnect throught your macosx network bridge.
Nice article, fixed this problem for me. One minor correction is that the parameter passed to boot.sh requires 2 dashes eg. “–restart”.
Thanks so much for this simple fix. This was quite an aggravation for me and it’s very nice when someone finds a neat and quick solution like this and posts it for everyone. Very much appreciated!
Excellent. Was having problems with my VM’s talking to the outside world and this fixed me right up. Thanks for the brief and concise answer!
Glad to be helpful! :)
Thanks! Solved the problem, that seemed to come completely out of the blue!
One thing though, as another commenter mentioned: Your blog system converts two hyphens, a required part of the command parameter, into an en or em dash, which doesn’t work in the terminal. Maybe it’ll be possible prevent this conversion in the code?
Thanks again!
Hey Andy,
I’ve fixed the issue. Thanks.
Cheers Simone,
I copy and pasted the command but had to remove the two dashes and retype them as they wouldn’t accept.
Thanks for the tip!
Thanks, I copied and pasted into Terminal and it did the trick. Thanks a lot for a quick solution!
Worked perfectly and immediately. Thanks!
Worked as a charm! Brilliant.
(VM Ware 2 OS X 10.5.7)
Wouldn’t work for me… once I put the text in it ran through looking like everything was successful but didn’t change anything. Did a Mac reboot and it did the trick.
you are star man. I was googling for such a simple solution.
thanks, you saved my life…
perfect solution. many thanks!
Grazie Simone. Funziona benissimo.
Mac OS X 10.5.7 con VM Ware 1.1.2
Worked great! Thanks
Worked like charm! I have spent a lot of time searching for the solution.
Host OS: Mac OS 10.6 Snow Leopard
Gest OS: Windows XP Pro
I too had this problem.
I tried the above, i.e.:
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
That unfortunately did not work for me.
I also found some other sites which suggested also:
/Library/Application\ Support/VMware\ Fusion/vmnet-apps.sh
Again that did not work for me.
In the end I tried something that for some unknown reason worked but I can’t see why:
1) Power Off the Guest OS.
2) Go VMware Settings – Settings
3) Go to Network
4) Untick the Connected box
5) Tick the Connected box
6) Start up the Guest OS.
Why unticking and then immediately ticking that box should fix this I don’t know.
I hope this helps someone.
Host: 10.6 Snow Leopard
Guest: Windows XP Pro
You, my friend, are a gentleman and scholar…
Hey thanks for the fix. It works great, but I have to do it every time I restart my machine. Does anyone else have the same issues or know of a way to make this permanent? I’ve only noticed this issue since installing Mac OS 10.6 (snow leopard)
Thanks!
Has nothing to do with 10.6 – i experienced it today the first time after nearly 2 years with 10.5.x and VMWare 2.0 and the tip with
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
helped me – thank you so much here!
( but nothing to do with snow leopard )
Sorry for the question bvut _where_ do you enter this command? Unfortuneatly I’m not so experienced with fusion 2.x
I have read something about a console. How do I start this?
Thx for your help…
You need to use Terminal.
Had to choose ethernet instead of auto-detect for bridged network.. Then afterwards fusion created the bridged interface and everything worked fine.
Thank you!!!
it work like a charm
Many thanks … Simone …
Thank you very much!!!!
worked perfect.
So happy. thanks!
When I execute the command it required a password what password I need to?????
The password of your account, assuming your account has administrator privileges.
Otherwise, you can’t execute the command.
Thanks for the fix.
As a side benefit it also fixed the inability to print from Windows.
Very happy now :-)
Great, that solved my issue.
Still a viable option for VMWare Fusion 3.1 w/ Snow Leopard Server (10.6). Not sure why this isn’t published by the guys who make the product, but you’re a lifesaver. THANKS!