On Sunday 07 March 2004 08:12, Bruce Marshall wrote:
On Sunday 07 March 2004 04:05 am, Tim Hanson wrote:
Actually, the networking is "host only." NAT uses the host's ip to access the outside. "Bridged" uses a fake nic to access the outside with its own ip. "Host only" is the only method which uses Samba to access the host's file system, through a second fake nic. It has always worked before (previous SuSE versions).
Not really true.... bridged will talk from the windows machine (running in VMware) over to the host linux machine samba (if there is one running)
I've always preferred to have a linux samba running and use bridged networking because any other windows machine on the network (as well as the vmware guests) then have access to all other machines. In short, every machine, virtual or not, has access to every other machine.
Yes Bruce, bridged will talk to the host samba, but this requires you make samba availaible on your Outside nic, (eg available to the world). If you use NAT its only available on the inside virtual nic and you are safer. Bridged requires (normally) an enternal dhcp server to give you another IP and requires aliasing your real nic (putting it into promiscuous mode). NAT does not require another external IP (Which may not be available in all cases. E.G. Some DSL providers and Cable modems only support one ip). You are correct that if other machines also have to talk to your virtual machines bridged does work best. But then you have to run some sort of firewall in the VMs just to keep the SMB worms from attacking your vms. -- _____________________________________ John Andersen