Login or Sign Up to become a member!
LessThanDot Sit Logo

LessThanDot

System Admins

Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.

LTD Social Sitings

Lessthandot twitter Lessthandot Linkedin Lessthandot friendfeed Lessthandot facebook Lessthandot rss

Note: Watch for social icons on posts by your favorite authors to follow their postings on these and other social sites.

Your profile

    Search

    XML Feeds

    Google Ads

    « Converting a VMWare 7 VM to run on ESXiTh QNap TS-419P Turbo NAS »
    comments

    I kinda like my VMWare Workstation 6.5 (soon to be 7.0). I always have at least 3 VM's running. But I seemed to have some intermittent network problems. I use Bridged networking because that's what I need. Most of my VM's have a static ip so no problems there.
    The problem usually happens after I force a close on a VM because sometimes they crash without asking me. And then a weird thing happens. The machine looses its outgoing connection. I can start the machine (albeit a bit slower than usual) and I can ping the machine. I can see the network connection is alive and well and I can ping my host machine. But nothing beyond that. The first couple of times this happened I googled and googled and tried a myriad of things to fix it but I never found a solution. The only solution was to reinstall the VM or use the backup. Not a very fun thing to do.
    Anyway, I finally found the solution. Apparently when it crashes it might think that your bridged adapter is no longer any good and choose another one (no idea which or how to find out which (not an expert).

    First of all, on an unrelated note, when using bridged networking you can disable the 2 VMNet adapters on your host. And while you are at it disable all the others you don't use too. This should prevent it from choosing the wrong adapter to begin with.

    Now to the solution I found worked best for me. In the edit menu of your Workstation click on Virtual network editor. And then go to the tab Host Virtual Network Mapping. Change it from "Bridged to an automatically chosen adapter".

    To the adapter of your choice.

    And then I restarted the VM and everything was nice and cheery in chrissieland again.

    About the Author

    User bio imageChris is awesome.
    Social SitingsTwitterHomePageLTD RSS Feed
    InstapaperVote on HN

    1 comment

    Comment from: ad [Visitor]
    ad im a newbie with vmware workstn 6.5 and im kinda having trouble pinging my team mates (xp pro, windows2003) in my network.


    -i tried using vmnet4 with and without dhcp
    - also lan segment

    what am i missing
    nothing works please help.

    my goal is to create a mcse lab.

    thanks a lot
    04/06/10 @ 09:09

    Leave a comment


    Your email address will not be revealed on this site.

    To mislead the spambots.

    Your URL will be displayed.
    (Line breaks become <br />)
    (Name, email & website)
    (Allow users to contact you through a message form (your email will not be revealed.)