[Samba] Samba on Virtual Machines

Mervini, Joseph A jamervi at sandia.gov
Mon May 12 21:41:48 GMT 2008


After a lot more investigation and testing (as well as identifying a error in my set up) I have determined the problem that I am having is related to the way that Windows handles mount to a samba share that is getting it's share via nfs through automounting.

My configuration is a system running RHEL5 and either the stock samba with the release or 3.0.28a compiled from source. User home directories are accessed via automounting using NIS; auto.home is pointed to the NIS map.

I have been able to prove that it is a auto.home indirect mount problem only. I have set up a test share using the /net indirect mount (i.e., path = /net/<machine name><device><directory>) and it works perfectly. However, when I mount the share via the auto.home, the explorer window comes up showing the files but any attempt to read/write/properties/etc. hangs and eventually times out. I have spent many hours trying many different configurations to make the work but have had absolutely no luck. And unfortunately the log messages (samba side) do not give any indication of a failure.

My system configuration is RHEL Client release 5.1 (basically everything), samba 3.0.28a, automount 5.0.1-0.rc2-55-el5.3. My samba configuration is below.

   workgroup = testgroup
   server string = Samba Server

   log level = 2
   log file = /var/log/samba/log.%m
   max log size = 10000

   security = server
   password server = passwdserver
   encrypt passwords = yes

   client ntlmv2 auth = yes
   client lanman auth = no
   max protocol = lanman2.0
   map to guest = Bad User

   load printers = yes

   socket options = TCP_NODELAY
   bind interfaces only = True

   use kerberos keytab = yes

   local master = no
   domain master = no
   preferred master = no
   wins support = no
   wins server = winserver
   wins proxy = no
   dns proxy = no

   preserve case = yes
   short preserve case = yes
   default case = lower
   case sensitive = no

   strict locking = no

#============================ Share Definitions ==============================

   comment =  User Files
   path = /home/%u
   browseable = no
   writable = yes

# Test net access
   comment = Net Test
   path = /net/sass4001/u74/%u
   browseable = no
   writable = yes

Any help would be greatly appreciated.


Joe Mervini
Scientific Applications and User Support
Sandia National Laboratories
Department 09326 MS-0823
PO Box 5800
Albuquerque, NM 87120
(505) 844.6770

-----Original Message-----
From: Rune Tønnesen [mailto:rune at tonnesen.org]
Sent: Monday, May 05, 2008 9:27 AM
To: Mervini, Joseph A; samba at lists.samba.org
Subject: Re: [Samba] Samba on Virtual Machines

Hi Joseph

It sounds more like a vmware problem. How is the network configurated on your vmware machine?

Best Regards Rune Tønnesen

Den 5/5/2008, skrev "Mervini, Joseph A" <jamervi at sandia.gov>:

>We have deployed Samba on VMware (ESX) on IBM Bladecenter H. I am having a serious problem with Samba related to Window client access. I can mount the samba share with no problem whatsoever and see all the files that exist within that share. However, when I try to open/write/copy/get properties on any file in either direction the operation stalls and eventually I will get a message similar to "Cannot copy <file>: The specified network name is no longer available." on the Windows client. We are running stock RHEL5 workstatiom with most packages installed (sound/telephony excluded). Our samba security is set to domain but this has also been tested with security set to user.
>I have an identical samba server (except IP/hostname, etc.) on a standalone blade that works flawlessly. I have scoured the web looking for answers but have come up empty.
>Has anyone on this list ever had a similar problem that might be able to share some insight?
>Thanks in advance.
>Joe Mervini
>Scientific Applications and User Support Sandia National Laboratories
>Department 09326 MS-0823 PO Box 5800 Albuquerque, NM 87120
>(505) 844.6770
>To unsubscribe from this list go to the following URL and read the
>instructions:  https://lists.samba.org/mailman/listinfo/samba

More information about the samba mailing list