Correct - I have had this happen on a couple of occasions, when I have to shutdown the host system hard due to host software lockup, not associated with VMware.<br><br>Re-running the config script will not blow out your config, as it asks if you want to keep it the same for networking, and wha-la - your VM hosts will be talking to the network again. I have not done any further research to see if this is a defect in VMware Server, or if it's host dependent(*nix, osx, win). If you find there is a defect, please let us know as well.<br><br>Hope this helped.<br><br>Thanks<br><br>Daniel Parraz<br><br><b><i>Bryan O'Neal &lt;BONeal@cornerstonehome.com&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> This happens to me from time to time on my PC's.  I just rerun the<br>configuration script and it has always worked.  Usually some upgrade or<br>configuration change on the host OS is the culprit
 though.<br><br>-----Original Message-----<br>From: plug-discuss-bounces@lists.plug.phoenix.az.us<br>[mailto:plug-discuss-bounces@lists.plug.phoenix.az.us] On Behalf Of Lynn<br>David Newton<br>Sent: Friday, April 27, 2007 9:16 AM<br>To: PLUG<br>Subject: virtual machines not on the net<br><br><br>I'm sure there are some VMware experts out there.<br><br>I'm running VMware Fusion Beta on my Macbook Pro. I<br>have three virtual machines: Ubuntu 7.04, openSUSE<br>10.2, and Windows XP, all working fine, or they were.<br><br>Yesterday something the external drive on my iMac<br>(which mostly sits idle) briefly went south for some<br>unknown reason. I had stuff shared off that system,<br>e.g., my iTunes library and the main disk drive, so<br>this caused correspondingly bogus behavior on my MBP,<br>noticed at first within two of my virtual machines.<br><br>Eventually the only thing I could do was to kill VMware<br>from a command line, since it became inoperable. Things<br>remained
 sluggish until I finally realized that the<br>real culprit was (evidently) the iMac, which I was only<br>able to recover by pulling the plug out of the socket.<br><br>After that, I brought up all three virtual machines two<br>or three times, but have been unable to get a network<br>connection on any of them.<br><br>On one VM (Ubuntu), ifup keeps fetching me addresses<br>like 169.254.2.158 rather than a 192.168.N.N. On the<br>SUSE VM it tells me that DHCP is running in the<br>background looking for leases, but never finds one.<br><br>Windows is no better, but I know almost nothing about<br>Windows or how to fix it. In any case, I don't believe<br>that the VMs themselves are the problem, but that<br>VMware itself is confused. I've tinkered with the<br>Settings to no avail.<br><br>Any ideas where to go from here? All of my machines are<br>useless to me in that condition. My real machines are<br>all fine.<br><br>-- <br>Lynn David Newton<br>Phoenix,
 AZ<br><br>---------------------------------------------------<br>PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us<br>To subscribe, unsubscribe, or to change  you mail settings:<br>http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss<br>---------------------------------------------------<br>PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us<br>To subscribe, unsubscribe, or to change  you mail settings:<br>http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss<br></blockquote><br><p>&#32;



      <hr size=1>Ahhh...imagining that irresistible "new car" smell?<br> Check out
<a href="http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-">new cars at Yahoo! Autos.</a>