similar to: Samba log hell

Okay, first the admisssions: I'll admit that I haven't been following the development as closely as I probably should have. And I'll admit in this case I might not be using Samba in the most efficient way possible. Also, I'm not 100% sure if I'm encountering a bug or just a seriously stupid misconfiguration issue. And I'm still collecting data on exactly what happened.

I'm getting a little closer and understanding how the logs, etc work. I can log onto a Samba share, can read and write to my home directory, but I'm concerned about trying to get the file share Staff to work - want it to be read and write to the Group named Staff. I have set up the group and added myself to the group If I do a smbldap-groupshow Staff - I get sudo smbldap-groupshow

Hi, I have a peculiar problem with my Samba installation. I have a directory with lots of files that I want to make available via Samba. I can connect just fine, but I quickly noticed a lot of files seemed to be missing. After some testing I found out that the directory listing was simple cut off, right in the middle of a filename even. I created a test-directory with 1000 random files in

Hi I've talked about this in other messages but have a feeling it might have got lost amongst the other symptoms we were discussing. I had a Redhat 9 server on which I'd installed Samba 3.5.6 (built from source). I had it authenticating successfully against a windows 2008 active directory server. I then upgraded the Redhat server to RHEL5.3, on which I installed Samba 3.5.7 (and

System Summary: centos 6.2 samba 3.5 smbldap-tools 0.9.6 openldap 2.4.23 Hello, I am installing smb 3.5 on a CentOS 6.2 host using smbldap-tools. I've previously installed a similar configuration on RHEL4 using smb 3.0 but CentOS now uses nss-pam-ldapd and nslcd instead of nss_ldap, so the configurations cannot be moved straight across. Currently, when I attempt to connect to an smb share

Hi, The following ii ?samba ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?2:3.4.7~dfsg-1 SMB/CIFS file, print, and login server for Unix ii ?samba-common ? ? ? ? ? ? ? ? ? ? ? ? 2:3.4.7~dfsg-1 common files used by both the Samba server and client ii ?samba-common-bin ? ? ? ? ? ? ? ? ? ? 2:3.4.7~dfsg-1 common files used by both the Samba server and client are installed on a squeeze ( 2.6.32-3-686 #1 SMP Thu

Hello to all, I have recently upgraded to SAMBA 3.4.2 on Solaris 10, and reconfigured it to use domain authentication (security = domain). We slapped guest authentication on most shares, with an explicit "valid users = ...." on a small number of sensitive shares. Due to the number of users we were looking at, we set up two UNIX groups "payroll" and "payoff" and

Hi, I upgraded samba to samba-3.0.23-1.fc4 and now I get authentication errors trying to connect to any shares explicitly defined in smb.conf. Iam using PAM for authentication. /etc/samba/smb.conf: [global] encrypt passwords = no debug level = 10 workgroup = MYGROUP server string = Samba Server security = user hosts allow = 129.180. load printers = yes cups options = raw log

We are using samba 3.4.8. We have some pc's using OS Windows XP Pro dan others Windows 7 Pro. All of them can join and logon domain to samba PDC + LDAP. FYI, the windows 7 clients are already hacked at registry settings: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DNSNameResolutionRequired"=dword:00000000

think it is a bug of samba but maybe someone can help me figure this out :-) Attached is the log and the relevant parts of smb.conf p.s. the share's name is 'privat' thanks & regards vinz ------=_20110202165921_20608 Content-Type: text/plain; name="smb.conf" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="smb.conf" #

think it is a bug of samba but maybe someone can help me figure this out :-) Attached is the log and the relevant parts of smb.conf p.s. the share's name is 'privat' thanks & regards vinz ------=_20110207170208_63601 Content-Type: text/plain; name="smb.conf" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="smb.conf" #

I have a file server with two shares accessible to 2 different groups. After the last update ( from debian 2:3.2.5-4 to 2:3.3.2-1 ) i cannot any more access ONLY ONE of the two shares and I can't understand the reason! Can anyone hel me? I'm getting mad! Thanks Giorgio from smb.conf: [documenti_movi] path = /home/documenti_movi valid users = @staffmovi read

Hello everyone! After running Samba on several machines for some years, I just came accross a rather strange problem. The short story is that the special user home shares are readable, but not writeable. Here's the long story: The system is a freshly set-up Debian Squeeze, right out of the box. This is the Samba config: -------------------------------- 8<

Hi! I have got the problem with my guest account. I can`t access to the share. The OS is Centos 5 Linux 2.6.18-8.1.10.el5 #1 SMP Version of krb5 is 1.5-29 This is my smb.conf: [global] # server string is the equivalent of the NT Description field netbios name = SERVER # workgroup = NT-Domain-Name or Workgroup-Name workgroup = DOMAIN realm = DOMAIN.NET security = ADS password server

Hi all, I seem to be having a problem identical to this bug: https://bugzilla.samba.org/show_bug.cgi?id=3940 in Samba 3.0.28, however the bug is supposed to be fixed by now. I have a Fedora 7 box joined as a member to Windows 2003 domain. All my Windows users have accounts on the Samba machine, with the same user name in Windows and in Unix. I have a share with valid users = +group, where

Hi, I have two samba domains. On one member of DOMAIN1 I set up a share "intranet" with valid users = +"DOMAIN1+webmaster" +"DOMAIN2+TestGroup" Winbindd is running. When I try to access the share from a DOMAIN2 workstation permission is denied. When I look at the logfile, I see that the server tries to find the group of DOMAIN2 (TestGroup) in ldap of the local

Hi, I have two servers, servera (DOMAINA) and serverb (DOMAINB). I have made a trust between this domain. But I try logon computer from domaina as user for domainb, the log in serverb wrotes me that a authentication was succeded: [2004/10/12 17:19:19, 3] rpc_server/srv_netlog_nt.c:_net_sam_logon(620) SAM Logon (Network). Domain:[DOMAINB]. User:[bronasek@\\XP1] Requested Domain:[DOMAINB]

Running Gentoo linux samba-3.0.23a I've used samba for quite some time but never have had to delve into its inner workings... Its always just worked. Recently I'm finding that when accessing linux shares from a winxp machine, I have read access, but no write. Far as I know the unix to samba user mappings as set correctly (and as they have been for some time) Near as I can tell the

I have an issue with getting my students access to the samba shares for our lab's server. I am using authentication through our university's active directory. I followed the directions for getting this set up using winbind. I am using winbind for both samba authentication as well as user logins through pam. The trouble is this: I have no problems logging in and getting access to the

Server role: ROLE_STANDALONE [global] workgroup = G8DOWNRANGE server string = G8DOWNRANGE1 passdb backend = tdbsam guest account = g8team log file = /var/log/samba/log.%m max log size = 50 preferred master = Yes domain master = Yes wins support = Yes hosts allow = 10.0.1., 127. [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [work-clear]