vmware + smb

Michael H. Warfield mhw at wittsend.com
Tue Jun 27 12:37:14 GMT 2000

On Tue, Jun 27, 2000 at 10:30:36PM +1000, Jens Lauer wrote:
> Sorry, but due to that the mail arcive is not available I cannot browse
> it
>                 - perhaps the question was answered hundred times before
> ..

> I have some problems with samba and vmware together. It seems that
> vmware (and its vmware_samba) use
> some ports which before only was for the generic linux samba so that
> such kind of error message appears in  "/var/log/samba/log.smb" :

> [2000/06/23 07:15:14, 0] lib/util_sock.c:open_socket_in(671)
>   bind failed on port 139 socket_addr= (Address already in use)

> This correlates slightly with the date I have installed vmware the first
> time on this machine.
> On an other host where vmware runs every week the smbd dies without
> reason and the windows users
> cannot log in anymore. What experiences are? How is vmware to set (host
> only or bridged) - pros and cons please.

	Well...  The opening words should be:  "Yes, of course, didn't you
read the documentation?

	Somewhere it states very clearly that you are NOT suppose to run
the version of Samba that comes with VMWare if you are already running
Samba on the system.  The VMWare version is only intended for systems which
are not running Samba and need a version installed to enable the host
system and guest system to share file systems.  If you already have Samba
installed, you don't need it.

	What you have is a documented self-inflicted injury and as the old
country doctor once said "if it hurts when you do that - DON'T DO THAT".

> Thanks in advance
> --jens

 Michael H. Warfield    |  (770) 985-6132   |  mhw at WittsEnd.com
  (The Mad Wizard)      |  (770) 331-2437   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!

More information about the samba-technical mailing list