On Sunday 01 July 2007 09:06:18 Erik Jakobsen wrote: > John Andersen wrote: > > reboot.
<snipped> > Starting VMware services: > Virtual machine monitor done > Virtual ethernet done > Bridged networking on /dev/vmnet0 done > Host-only networking on /dev/vmnet1 (background) done > Host-only networking on /dev/vmnet8 (background) done > NAT service on /dev/vmnet8 done > > The configuration of VMware Workstation 5.5.4 build-44386 for Linux for > this running kernel completed successfully. > > You can now run VMware Workstation by invoking the following command: > "/usr/bin/vmware". > > Enjoy, > > --the VMware team As John Andersen mentioned, this all looks pretty much correct. When you run through this script, and define the bridged network(s) - how many have you set up? How many physical ethernet devices do you have? What I've had happen is to have my wired interface (eth0) bridged and then tried to run VMware when on a wireless network. When this has been done, obviously the wired network is not available and you can get a message similar to the one you are reporting. If you want to send along the output of ifconfig -a and ps -eaf | grep vmnet-bridge that might help. > # lsmod | grep vmnet > vmnet 45484 12 > lajka3:/home/erikja # modprobe vmnet > > I still have the problem with the bridged Ethernet The above is fine - the vmnet module is already loaded, so modprobe vmnet is not necessary. Jon -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
