1. The follow-up window will contain setting parameters related to the network conditions. With questions about the way you’d like to setup your network, if at all. The options are fairly clear - you can “Use bridged networking”, run your host as a NAT, create a virtual network between your host and a starting system via “Use host-only networking” or cut off your virtual machine from a network with the “Do not use network connection” option.
2. Networking: If you want the virtual machine to be part of the same network than the server itself, select bridged networking.
If you want to use a virtual NAT, select Network address translation.
(1 and 2 equate or resolve to the same thing) and Both of those fall under "creation of a new virtual machine" at above url's
At 2nd url above it shows how to prep the host OS for vmware server (1. host OS must have a static IP, and 2. the IP itself of the vmware server into /etc/hosts and more -- note: I think 1 and 2 are different IP addresses -- IOW host OS has an unique IP and vmware server has a unique IP)
I'm guessing slightly on some of this -- I currently run Qemu is EZ to do with its default user mode network stack, has its own built in Samba server, nat ,dhcp sever and all.
qemu -boot c sda3 ~/images/win2k.qcow -m 1000 -smb ~/ntp -localtime
that means my smb shared folder (between Win 2K guest and Slack 12 host) is /home/al/ntp
In Win I had to map a network drive in order to get it to work. Oh, but does it ever work! And reliable. never breaks! Ez file sharing between host and guest.
Oh but did I ever scratch my head for a while until I eventually got it working. But then I saw how easy it was (I had been trying to overcomplicate -- and also a thing or two I had not yet grasped).
For my next proj., I haven't yet decided if it will be Xen or if it will be Vmware Server (or Virtual Box for that matter).
I've run Vmware Player too (on Slack 11). But I had to run my own Samba server there (no built in)
Slack 12 I used Eric Hameleer's Qemu and gcc "compatability" build scripts/packages and I copied my Win 2K file from Slack 11 and it works fine (that's time saving to not have to install Win 2K again.
Vmware player fell by the wayside on Slack 12 (did not do it).