similar to: [Solved] A working CUPS authentication now fails without change anything...

2015-05-04 18:50 GMT+02:00 Andrey Repin <anrdaemon at yandex.ru>: > Greetings, Daniel Carrasco Mar?n! > > >>> 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... >

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

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 anything... > > The thursday I was configuring the server to allow the management of cups > with AD

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

Seems I cheered too early, and I have some more winbind issues I didn't realise before... here are winbind logs: > [2016/04/11 20:39:01.330107, 1] ../source3/librpc/crypto/gse_krb5.c:416(fill_mem_keytab_from_system_keytab) > ../source3/librpc/crypto/gse_krb5.c:416: krb5_kt_start_seq_get failed (Permission denied) > [2016/04/11 20:39:01.330143, 0]

On 26/10/15 19:50, mourik jan c heupink wrote: > 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

Hello, I'm receiving repeated cores with the captioned environment. Here's a snippet from log.smbd: ======================== [2018/07/08 03:01:55.936275, 0] ../lib/util/fault.c:79(fault_report) INTERNAL ERROR: Signal 11 in pid 91640 (4.7.1) Please read the Trouble-Shooting section of the Samba HOWTO [2018/07/08 03:01:55.936307, 0] ../lib/util/fault.c:81(fault_report)

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

If anyone want the below dump its reproduceable, so i looks to my this is a bug and simply fixed. I didnt set the kerberos settings in sshd_config: so i enabled. KerberosAuthentication yes KerberosGetAFSToken no KerberosOrLocalPasswd yes KerberosTicketCleanup yes and the crash is gone. greetz, Louis -----Oorspronkelijk bericht----- Van: belle at bazuin.nl [mailto:samba-bounces at

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

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

Hello, I can't get Kerberos authentication works with my Linux clients. Server : samba 4.1.4 (compiled from source) Client : Debian Wheezy with sernet-samba 4.0.17-8 Without Kerberos authentication, everything works : -> the domain users can log with pam_winbind (with ssh, gdm ....). -> "kinit myuser at MYREALM" works fine. -> "wbinfo -K MYDOM\\myuser" works.

On 27/03/15 20:46, Peter Serbe wrote: > Dear Samba fellows, > > I try to install samba on my notebook in order to get it into > my samba based domain. It was a bit picky to get everything > assembled on the notebook - but that last issue is hard. :-( > > I installed it from the sources on Debian Jessie - exactly > in the same manner I used for my servers. I got sssd and

ok, i cant make i crash. but i notice my cpu load. 17535 username 20 0 294852 13716 11520 R 100.0 1.3 280:28.70 winbindd 542 username 20 0 291040 16720 14172 R 99.6 1.6 281:45.88 winbindd and the funny thing.. this user isnt logged in anymore since the last 6 hours. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: samba [mailto:samba-bounces at

Hi, Bartlett I decided to cut some subsystem by myself, So I spent several days to study the SAMBA 4 WAF build system and now know the base steps of build. but which subsystem can be removed for snmd/nmbd/smbpasswd ? followings are the full dependencies of these 3 binary ldd bin/smbpasswd libpthread.so.0 => /lib/libpthread.so.0 (0xf7139000) libsamba-util.so.0 =>

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

On 28/08/15 09:20, Volker Lendecke wrote: > On Thu, Aug 27, 2015 at 08:17:15AM +0200, L.P.H. van Belle wrote: >> This was a test on debian Jessie with sernet samba 4.2.3. >> and the test was, "login" with a AD user on ssh. >> this worked, fine, but this i noticed later. > Ok, got more information. But I am still not able to > reproduce it. Unless someone would

Le Sat, 18 Feb 2017 20:17:12 +0000 Rowland Penny via samba <samba at lists.samba.org> écrivait: > Only change I made before installing Samba, was to comment the > '127.0.1.1' line in /etc/hosts Tried again with your smb.conf and minimal changes, and it gets worse: [2017/02/20 14:42:19.048133, 0] ../lib/util/fault.c:78(fault_report)

Samba4-winbind (sernet-samba-4.0.9) on RHEL 6.4 dumps core on password authentication for a domain user (su/sudo), and so domain password authentication fails.? The machine is a standalone server in a Windows AD (2008R2) domain. PuTTY logins using GSSAPI work fine, kdestroy/kinit succeeds with AD password, but su'ing to the userid from a puttty session fails. The issue seems to be related to