similar to: Winbindd and getent group problem

The owner of a folder (userid gdunn01) is unable to make any changes to it (rename / delete) through Samba despite being listed as having read/write perms. I'm using winbind for username mapping. I feel like I'm missing something simple. ma21cab5# wbinfo -t checking the trust secret via RPC calls succeeded ma21cab5# ls -ld asdfas/ drwxr-xr-x 2 gdunn01 Domain Users 512 Jun 22 08:50

Hello Marc, > What schema version does your AD have? > http://www.itguydiaries.net/2012/09/how-to-find-current-active- > directory.html > > Samba is shipped with AD schema 47 (MS Windows Server 2008 R2). Maybe > you already run a newer schema version or had done schema enhancements, > that are currently not supported by Samba. AD scheme version is 47. However, a few years

Hello all, I have a pretty large DC and am using winbind for our linux workstations and im having a preculiar issue. Not all accounts but some...including mine are recieving the pam error to change password. example... ... WARNING: Your password has expired. You must change your password now and login again! Changing password for user msellers. Changing password for msellers (current) NT

Dear all, I have joined samba 4.1.18 (FreeBSD 9.1) to an Active Directory domain as an active directory domain controller. The domain has two other Windows Server 2008 R2 DCs. Both windows and samba complain about replication problems. Windows reports that replication from Windows DCs to Samba completes successfully, but replication from Samba to Windows fails with error "The replication

Dear Samba friends, Last weekend I decided to upgrade the samba server. We were running Samba 3.3 something and FreeBSD portupgrade was complaining that this version should be removed and assumingly replaced by the newest version. I removed the package via portupgrade and installed the 3.5.6 version. The upgrade went quite smoothly in general, but I encountered some difficulties with the printer

Dear Samba friends, Last weekend I decided to upgrade the samba server. We were running Samba 3.3 something and FreeBSD portupgrade was complaining that this version should be removed and assumingly replaced by the newest version. I removed the package via portupgrade and installed the 3.5.6 version. The upgrade went quite smoothly in general, but I encountered some difficulties with the printer

Hello, i hope u guys can help me. This is the first time I write to the list. Sorry about my english... i got a solaris 10 machine and installed "samba 3.0.2.3c" with "openldap 2.3.2.1" , "openssl 0.9.8" and "gcc 3.4.6". i configured kerberos and all the other things. all good. i added the samba-server (solaris10) to a active directory domain. with

Hello, I'm having problems with group consistencies between my samba server and a trusted domain. I'm running 3.0.23b with my samba server a member of an NT domain, which in turn trusts another domain (AD mixed mode). The AD admin added a user into a group, but my samba server sees the user as being added to a different group. Any ideas? Regards, Franz

Hi there Just a couple of questions to help me understand. When I upgrade from 3.0.22 to 3.0.23c the access restrictions on my shares on the member server no longer work. I read in the Changes file "Since Samba 3.0.8, it has been recommended that all domain accounts listed in smb.conf on a member server be fully qualified with the...." So far so good I know what I have to do still I

Hello, In the documentation it's writen (https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO) We do not recommend using the Domain Controller as a file Server What are the best practice in a environement with only 10 pc If you have just one physical computer (vm,lxc,..) Thanks -- probeSys - spécialiste GNU/Linux site web : http://www.probesys.com

Hello, Using samba 3.0.23c on Debian 3.1 (package version 3.0.23c-1~bpo.1 from sarge-backports) or version 3.0.14a (package version 3.0.14a-3sarge2 from sarge), I experience the following problem on a file server on a Windows 2003 domain with Active Directory. Some test user can access group shares of groups he is not in, or cannot access group shares of groups he is in. The output of the

I've got a client - a cheap client - and they want to add a new file server (samba sharing) to their network. They have one samba server already acting as the domain controller (PDC) and file server (and DHCP server). The wiring is a nightmare, and everything is daisy chained through 3 different non- programmable switches. They have no more open ports on any of the switches. Further, the

Hi all! Im using samba 3.0.23c from debian backports and I finding some problems, this host has worked flawlessly since a a few months ago. But now stopped to work properly. My versions are: ii winbind 3.0.23c-1~bpo.1 service to resolve user and group information from Windows N ii samba 3.0.23c-1~bpo.1 a LanManager-like file and printer server for

hi, i just do some tests with a fresh compiled samba 3.0.23a. trying to authenticate against PAM with pam_winbind gives: Aug 1 09:59:21 humevo36 pam_winbind[27853]: pam_winbind: pam_sm_authenticate (flags: 0x0000) Aug 1 09:59:23 humevo36 pam_winbind[27853]: Verify user `gasch' Aug 1 09:59:23 humevo36 pam_winbind[27853]: enabling cached login flag Aug 1 09:59:23 humevo36

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== Here's a new adage for you: "Don't let the crazy hacks take over". -- Tridge ============================================================== Release Announcements

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== Here's a new adage for you: "Don't let the crazy hacks take over". -- Tridge ============================================================== Release Announcements

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've upload the preliminary patch against 3.0.23b that will become 3.0.23c so people can do full testing against what we hope to be the release code. Note that the reported version in the patch is 3.0.23c-gwc-1 to prevent confusion from the final 3.0.23c release. You can download the gzipped patch file from

Hi! Here is the Output: bash-3.00# id NTBV+neuwald uid=5000(NTBV+neuwald) gid=5006(NTBV+dom??nen-benutzer) bash-3.00# /usr/local/samba/bin/wbinfo -r NTBV+neuwald 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5000 5015 5016 5017 5022 5029 5033 5035 5021 5023 5019 5032 5028 5027 5034 5020 5026 5030 5024 5018 5036 5025 5031 Ciao, Bj?rn -----Urspr?ngliche

"schema enhancements [...] are currently not supported by Samba." Does this applies only when connecting a Samba DC on MS AD or is the replication broken also when we enhance schema on Samba-only-domain? Cheers, mathias @Marc, as you can imagine I'm not too aware about schema modification and Samba replication restriction, but it seems this Office Communication Server schema

Ubuntu Server 7.04 Apache/2.2.3 (Ubuntu) PHP/5.2.1 mod_perl/2.0.2 Perl/v5.8.8 mod_auth_ntml_winbind from svn June 5, 2007. samba 3.0.24-2ubuntu1.2 winbind is working, I can log into the machine as an AD domain user. graham@wtldevapp1:~$ sudo ntlm_auth --username=gdunn01 password: NT_STATUS_OK: Success (0x0) from the conf.d/twiki.conf: AuthName "NTLM Authentication" NTLMAuth