similar to: Samba / NFS performance

Hi, I'm using samba 3.0.0 under redhat 9.0. Quota is assinged to user but they can't see their used space on windows explorer. The used space reported is only 8.0k, no matter what they have in ther home. I used the samba rpm downloaded from samba site. For a smbd -b command i get this (extract): --with Options: WITH_ADS WITH_PAM WITH_QUOTAS WITH_SENDFILE WITH_SMBMOUNT

On Thu, 2017-06-08 at 10:09 +0200, awl1 via samba wrote: > Hello again, Samba experts, > > sorry for being such a pain in your necks, but I really need to get a > recent Samba version to compile, and it looks like I definitely need > your help with this. > > In the meantime, I have found that the huge number of "conflicting > types" errors for rpc_*_init(...)

Hello, I've compiled Samba 3.0.4 with Heimdal 0.6.2 and all of the other trimmings to join and ADS tree, which I have successfully done. Winbind correctly pulls all of the username and group information from the ADS tree and all is good. However... I seem to be running into a wall with the wonderful Solaris 8 character username / groupname limit. Usernames with spaces or names longer than

Hello. I can not enter the domain machine: net rpc join -S 192.168.128.10 -U user cli_rpc_pipe_open_noauth: rpc_pipe_bind for pipe \lsarpc failed with error NT_STATUS_UNSUCCESSFUL Could not initialise lsa pipe Enter root's password: cli_rpc_pipe_open_noauth: rpc_pipe_bind for pipe \lsarpc failed with error NT_STATUS_UNSUCCESSFUL Error connecting to LSA pipe. Error was NT_STATUS_UNSUCCESSFUL

Hello, I'm working on a server and I enabled quota's on the filesystem. This works fine. But Samba doesn't see that quota. I have read that you need to compile samba with quota support. My problem is that I have a running Samba (from SuSe 10) and I don't know if there is quota support build in. Is there some way to see if quota support has been compiled in? Greetings, Peter

I noticed lots of smbclient options are missing in Samba 3.0.14a when compared to 3.0.13 - notably, all user/authentication options - so I can't connect now as a specified user anymore. Is it just my build, or is it "official"? Samba 3.0.14a: # smbclient --usage Usage: [-?] [-?|--help] [--usage] [-R|--name-resolve NAME-RESOLVE-ORDER] [-M|--message HOST] [-I|--ip-address IP]

On Thu, 2017-06-08 at 11:28 +0200, awl1 via samba wrote: > Hello Andrew, > > and many thanks for your fast reply! :-) > > Am 08.06.2017 um 11:05 schrieb Andrew Bartlett: > > I think the key to avoiding the issue is that you have listed rpc > > modules which are not modules. The only rpc server module is > > rpc_mdssvc_module. > > Ah, OK, I see - so I

Hi Thanks for the feedback. I currently have 3 production domains. - MYDOMAIN.COM is a production Windows 2008 domain used to support MS Exchange (but not file sharing.) - TECH - Samba3 "classic" domain with unix domain controllers that supports most users for authentication and file sharing. The DC machines are both Samba domains (for Windows clients) and KRB/LDAP

Need some help if anyone can provide it on this issue. I have a very basic setup and am trying to have samba utilize openldap. I have made sure the password is correct but for whatever reason, I am unable to connect. Here is a log of what is going on. Any help would be greatly apprecated. TIA Maximum core file size limits now 16777216(soft) -1(hard) get_current_groups: user is in 7 groups: 0,

My customer complain that in the AD DC they see the following insecure communication coming from the Samba server (DC member): "The following client performed a SASL (Negotiate/Kerberos/NTLM/Digest) LDAP bind without requesting signing (integrity verification), or performed a simple bind over a cleartext (non-SSL/TLS-encrypted) LDAP connection." So Samba does an insecure LDAP bind and

Hi! I'm experiencing problems with access to one of shares on server with Samba working as PDC for windows clients, after I upgraded Samba from 3.0.22 to 3.0.23 (this problem also present in 3.0.23a). There are config section for this share: ---------------------------------------------------------------- [domain] comment = Domain users exchange share path =

Thanks. I am still not sure whether option "with-acl-support" has been compiled in the smbd. The following is the output: Build environment: Built by: root@hxwu-dt-tt Built on: Tue Dec 23 15:00:40 CST 2003 Built using: gcc Build host: SunOS hxwu-dt-tt 5.9 Generic_112233-08 sun4u sparc SUNW,Sun-Blade-100 SRCDIR: /space/hxwu/swinstall/samba-3.0.1/source

I'm curious to know where the tdbsam password database file is kept on my Fedora 7 system. Using the unmodified smb.conf file that shipped with Fedora 7, I've enabled users using smbpasswd, and successfully accessed shares. I just can't figure out where the password database is located: [root@box ~]# service smb start [root@box ~]# setsebool samba_enable_home_dirs on [root@box ~]#

Hello, I'm trying to set up samba using ADS for authentication. I can successfully join the samba machine to the domain. Windows hosts can "see" the samba machine. After successfully joining, doing: # wbinfo -u shows me ADS-defined users. Same goes for groups. However, when I try and assign one of those users ownership of a file, I get: # chown user1 /tmp/test chown: test1:

I've got some problems with file access control on a linux-server with samba 3.0.14a compiled from a src-rpm. This is the method I've been using for the past 5-6 releases. It's a redhat 8.0 machine and the kernel version is 2.4.30. The problems seem to have appeared since upgrading from 3.0.13. Symptom 1: When using force group on a share, users from the two groups edb and

Hello Andrew, and many thanks for your fast reply! :-) Am 08.06.2017 um 11:05 schrieb Andrew Bartlett: > I think the key to avoiding the issue is that you have listed rpc > modules which are not modules. The only rpc server module is > rpc_mdssvc_module. Ah, OK, I see - so I seem to have been wrong when assuming that I could take the output of Samba 3.5.16 "smbd -b" command

Hello, I've managed to join four other samba servers to win2k3 domains in the past but I am stuck doing so with samba-3.0.23c_2,1. I've verified hosts / domain forward and reverse lookups succeed. Below are my configurations. I'm running FreeBSD 6.1-stable cvsupped as of Nov 17. I've built Samba with the following options... WITH_LDAP=true WITH_ADS=true WITHOUT_CUPS=true

We have a rhel4 system running samba - domain user accounts - NFS disk space. All updates and software patches have been applies through rhn. Since samba was installed with redhat provided rpms, --with-quotas WAS configured in. The samba share is seen and can be used by authenticated users. However quotas are not being recognized. The same disk space, if accessed via Windows shares are

RedHat Enterprise AS 4 Samba 3.0.10-1.4E.12.2 nfs automounted home directories Samba: --with Options: WITH_ADS WITH_AUTOMOUNT WITH_PAM WITH_QUOTAS WITH_SENDFILE WITH_SMBMOUNT WITH_SYSLOG WITH_UTMP WITH_WINBIND Logged in locally, a user is warned when over quota and cannot copy further files. Over CIFS, a user is warned when over quota and cannot copy

Hello folks, I am implementing on a RH Fedora Core Linux machine NTLM authentication through samba 3.0.2 for my squid server (Squid-2.5STABLE5-2). Our customer's environment is Mixed Mode Windows 2000. To make a long story short: (1) I have successfully upgraded kerberos from 1.2.7 to 1.3.3 (I was successful because I also upgraded the libraries that kerberos 1.3.3 requires (2) I have