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. Any ideas where I should start? -- When one woman was asked how long she had been going to symphony concerts, she paused to calculate and replied, "Forty-seven years -- and I find I mind it less and less." -- Louise Andrews Kent
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
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).
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
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. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 03/07/04 12:09 + +----------------------------------------------------------------------------+ "The only way to get rid of temptation is to yield to it."
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
On Sunday 07 March 2004 08:31 pm, John Andersen wrote:
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).
Oh really??? Wanna bet? Wanna take a crack at the two or three windows machines you'll find on my network? as well as all the linux machines running samba? Why in hell would you think that just because a service is running on a LAN that it has to be made available to the world?? Eh?
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).
I don't run any dhcp, anywhere. It's not needed if you don't want it.
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).
I don't run NAT either.
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.
Just a firewall between your gateway server and the 'outside world', but I assume we all do that... Don't we?
-- _____________________________________ John Andersen
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 03/07/04 20:43 + +----------------------------------------------------------------------------+ "Roses are red; Violets are blue." I'M SCHIZOPHRENIC, And so am I."
On Sun, Mar 07, 2004 at 08:47:24PM -0500 or thereabouts, Bruce Marshall wrote:
On Sunday 07 March 2004 08:31 pm, John Andersen wrote:
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 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).
Oh really??? Wanna bet? Wanna take a crack at the two or three windows machines you'll find on my network? as well as all the linux machines running samba?
Second that... same for me here.. John you do not have to make SAMBA open to a WAN..
Why in hell would you think that just because a service is running on a LAN that it has to be made available to the world?? Eh?
agreed..
Bridged requires (normally) an enternal dhcp server to give you another IP and requires aliasing your real nic (putting it into promiscuous mode).
Bridging does not require DHCP at all John.
I don't run any dhcp, anywhere. It's not needed if you don't want it.
same here.
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).
I don't run NAT either.
Me either, John, your concept of what NAT is or does is a little off here. What difference if DSN/Cable only support one IP? That does not factor into anything.
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.
Just a firewall between your gateway server and the 'outside world', but I assume we all do that... Don't we?
Right, no special firewall to keep SMB worms out on VMW.. it is already behind the LAN firewall. Draw a LAN diagram in your head... WAN-firewall-LAN-(including VMW) in its simplest terms.. -- Gary Your E-Mail has been returned due to insufficient voltage
participants (4)
-
Bruce Marshall
-
Gary
-
John Andersen
-
Tim Hanson