similar to: SIGSEGV with pam_winbind kerberos authentication

Quoting Adam Tauno Williams <awilliam at whitemice.org>: >>>> It should work, it sounds like a mis-configuration somewhere, can you >>>> post the smb.conf, /etc/nsswitch.conf, /etc/resolv.conf and >>>> /etc/krb5.conf from the member server. >>> "wbinfo -u" lists 415 lines >>> "getent passwd" returns 93 lines

On 14/04/15 20:59, Adam Tauno Williams wrote: > On Tue, 2015-04-14 at 15:20 +0100, Rowland Penny wrote: >> On 14/04/15 14:59, Adam Tauno Williams wrote: >>> On Thu, 2014-10-30 at 13:41 -0300, Horacio G. de Oro wrote: >>>> Hi! I'm trying to add a member to be used as fileserver, following the >>>> guides at: >>>> -

Dear I have connected samba 3.6.8 to my Active Directory in the lsass.exe run to 100% When stopping winbind the lsass.exe CPU is down to 0% When set winbindd to debug mode, it seems it try to scan the root user every time. I would to know how to ban nsswitch to query winbindd for system internal users such has root, apache..... Here it is my nsswitch.conf : # # Example configuration of GNU

Hi Oracle Linux Server client with Samba 3.6.23 (file server) joined to the Samba4 AD domain. ---------------- smb.conf [global] #--authconfig--start-line-- netbios name = FS server string = "GSDAD Fileserver" workgroup = GSDAD realm = AD.GSD.LAN security = ads winbind use default domain = yes idmap config * : backend = rid idmap config * : range =

Dear list, upgrading from SLES11 SP1 to SLES11 SP2, I upgraded Samba from 3.4.3 to 3.6.3. I was successfully using idmap_ad to authenticate users but after the upgrade it stopped working and users are not seen by the OS. Obviously the users I want to see on the Linux server have all RFC2307 attributes populated and are seen by all other SLES11 SP1 servers. I checked everything (I know) from the

Hi, first of all i'm sorry for my english. I'm trying to create a print server in the same server that has the samba AD but i cannot make it work. For now i've: - A working AD server with Samba 4.2.5 - A Cups server with the print drivers - GPO policies to install the printers in the client computer All works perfect and even i can send test pages from cups, but i cannot

hi all, I can't figure out why winbind can't find ad users with wbinfo calls. It happens on a member server, Debian GNU/Linux stretch, samba is 4.7.5 from Louis repository: [global] security = ADS workgroup = EXAMPLEAD realm = EXAMPLE.ORG idmap config * : backend = tdb idmap config * : range = 1000000-3000000 idmap config EXAMPLEAD:backend = ad idmap config

Hi, Just a moments ago i've sent a message to other user saying that I've a working server with CUPS authentication using AD groups. Well, that authentication is not working anymore and i've not changed anything... The thursday I was configuring the server to allow the management of cups with AD groups and was working perfect. After that i've added some printer alias to samba

Thanks to both but did not worked. Tomorrow i'll try to reinstall the whole OS because maybe i've installed something wrong. Greetings!! 2015-11-11 12:08 GMT+01:00 Rowland Penny <rowlandpenny241155 at gmail.com>: > On 11/11/15 10:41, Daniel Carrasco Marín wrote: > >> Hi, first of all i'm sorry for my english. >> >> I'm trying to create a print

Hi, I installed a debian jessie machine, compiled/installed samba 4.3.1, configured as a domain member server, configured winbind: all working nicely. Great docs on the wiki. (https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server) One remaining thing: How do I exactly configure pam_winbind in the setup above? On the wiki I read that debian uses pam-auth-update. That does not seem

Hi Rowland, Thanks for the very quick reply. :-) On the page you reference (https://wiki.samba.org/index.php/Libnss_winbind_links) it says: # smbd -B | grep LIBDIR LIBDIR: /usr/local/samba/lib/ On my install, I need to use lower case b. Capitol doesn't work. Perhaps the wiki needs to be updated? Anyway: I created the symlinks, ldconfig, all seemed to work. Your recipe for

Greetings, Daniel Carrasco Mar?n! >> > Cups calls pam authentication, and pam use winbind then I need to give >> > permissions to winbind daemon but i don't know what account is using that >> > daemon. How i can see it?, because ps aux shows the most as root. >> >> winbind normally have access to Kerberos keytab by default. >> I see no reason why

Some other observations in log.winbindd-idmap: > [2016/04/12 08:37:54.028456, 1] ../source3/winbindd/idmap_ad.c:523(idmap_ad_sids_to_unixids) > Could not get unix ID for SID S-1-5-21-90839350-987482234-868425949-133237 > [2016/04/12 08:45:57.051863, 1] ../source3/winbindd/idmap_ad.c:523(idmap_ad_sids_to_unixids) > Could not get unix ID for SID

2015-05-04 18:16 GMT+02:00 Rowland Penny <rowlandpenny at googlemail.com>: > On 04/05/15 17:03, Daniel Carrasco Mar?n wrote: > >> Hi, >> >> Just a moments ago i've sent a message to other user saying that I've a >> working server with CUPS authentication using AD groups. Well, that >> authentication is not working anymore and i've not changed

It's already done. I did a lot of tests, installed testing packages... and y prefer to start with a clean system. Anyway was an empty domain with only an user. I'll report how it works ;) Greetings!! El 11 nov. 2015 12:43 p. m., "Rowland Penny" <rowlandpenny241155 at gmail.com> escribió: > On 11/11/15 11:31, Daniel Carrasco Marín wrote: > >> Thanks to both

Hai, i've seen a core dump... ? Clean server, static ip, Debian Jessie, samba 4.1.13 and cups installed. ? Im leaving the office now, but ill go test tomorrow some more. It happend while logging in on ssh server. pretty basic setup, like on the wiki, and?pam was updated by running pam-auth-update. tomorrow more info if this is not known. ? Nov 13 16:57:03 rtd-printsvr1 winbindd[12690]:??

Hi Rowland, > You have real trouble if you don't have the last three :-D > > They are well known SIDs > > 501 is Guest > 502 is krbtgt > 517 is Cert Publishers > > Try opening a terminal on the DC and run this: > > ldbsearch -H /usr/local/samba/private/sam.ldb > '(objectsid=S-1-5-21-90839350-987482234-868425949-501)' I searched with ldbsearch, and

Hi, I just upgraded my member (fileserver) server (wheezy) from sernet-4.1 to sernet-4.2, to be ready for tomorrow's badlock outbreak. Under 4.1 we used sssd, and now 4.2 with winbind. Everything seems to be running good: wbinfo (-p, -u, -g, -t) all give the expected results, same for getent (group, passwd, username) File serving works, life is good. :-) Last step: allowing ssh access

Dear Members, Today i upgraded my small domain which ran on debian 7 to debian 8. The samba version does not change, it stays at 4.1.17 After the upgrade i noticed, that the ssh password auth does not work on the member servers. Excerpt from the log: Aug 18 14:46:31 medea winbindd[707]: STATUS=daemon 'winbindd' finished starting up and ready to serve

Hi samba team ! I have found a very strange bug when changing my user's primaryGroupID with ldif files. The bug is very easy to reproduce : 1) Create a user, create a group, add the user to the group ------------------------------- ~# samba-tool user add stduser User 'stduser' created successfully ~# samba-tool group add stdgroup Added group stdgroup ~# samba-tool group addmembers