On Sunday 07 March 2004 00:05, Tim Hanson wrote:
On Sun, 2004-03-07 at 00:16, John Andersen wrote:
On Saturday 06 March 2004 19:17, Tim Hanson wrote:
I'm having some trouble configuring vmware. I got around the vm*.o problem by reading the SuSE database and got the thing running.
Now, I can't get host-only networking to work. Bridged works fine; I can find the internet using windows through my Linux host. Ping of the host through windows works with no packet loss. I can't find the host through my "Network Neighborhood" Find utility.
I'm not familiar with the smb.conf file in /etc/vmware/smb/. I do not have another instance of Samba running.
Bridged probably is not what you want, because I doubt the samba is set up to allow connections via it's outside nic. (Think of bridged as if it installed a second nic in your machine and the only way for the vm to talk to the host is as if they were two different machines plugged into the same hub/switch.
You probably want NAT. I've never used vmware's SAMBA setup, always prefering to do my own. Do you suppose swat can be pointed at the VMware smb.conf?
-- _____________________________________ John Andersen
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).
NAT also works for host file access, Its the only method I use (except for certain things where bridged is needed). I've never found a use for host only, and all of my samba access is via NAT. -- _____________________________________ John Andersen