similar to: Problems with Winbind and NTLM Authentication

This issue right here told me exactly what I needed to understand this authentication process:https://pagure.io/SSSD/sssd/issue/3228 - The client talks to the DC to try and get a cifs ticket for my samba server's princpal name;- In case the client can't get the ticket for any reason, it falls back to NTLM <- windows client decision, nothing can be done about it by Samba/SSSD; Once I

I must be missing something- Are these Windows clients?  Or are these Linux clients authenticating against Samba ? if they were linux clients then yes I could see sssd or other authentication components besides winbind coming into play. And in that case yes you would have sssd work with winbind to enable caching of credentials. Is the event log entry below from the server ?   Is it from

Hi!! We have two squid proxies running at our site, both of them with the same versions and configurations (Fedora Core 5, Samba 3.0.22-1.fc5, installed through rpm, and Squid 2.5.STABLE13. Both are running on Dell servers with the same configuration. Samba on both machines is configured with "security = ads", and the testes "wbinfo -t", "wbinfo -u" and

There are roughly 20 DC's, spread across multiple different physical locations. It is indeed a replication issue. All of them are windows and we can get authenticated by any of them, randomly. Don't ask me why... they're managed by the "windows' guys"... I've already tried all sorts of possible combinations for the various NTLM-related parameters and it always fail

How is your sssd settup (sssd.conf) configured? When someone connects via samba, the underlying linux/unix file system routines need to have some what of understanding the windows users and groups.   This isn't for authentication  but is instead to make sure that the file permissions can be managed and enforced. My experience - at least when I had classic domain Samba controllers-  was

Heyho. My apologies if this mail arrives twice. The first time I sent it my email address didn't correspond to the one I signed onto the list with (one was an alias for the other). I'm not sure if the original will eventually make it through or not. I have a NT Domain which is run by my samba server (v3.0.22-r3 on Gentoo Linux). Everything works well, and the backend database is

I'm trying to get NTLM authentication working with Dovecot to authenticate Postfix SMTP clients. I can authenticate postfix smtp clients using the plain text login mechanism through winbind. However, using the NTLM mechanism gives me an error in my maillog that says: "dovecot: auth: winbind(?,10.20.2.0): user not authenticated: NT_STATUS_UNSUCCESSFUL". At this point,

I'm trying to get NTLM authentication working with Dovecot to authenticate Postfix SMTP clients. I can authenticate postfix smtp clients using the plain text login mechanism via Dovecot and winbind. However, using the NTLM mechanism gives me an error in my maillog that says: "dovecot: auth: winbind(?,10.20.2.0): user not authenticated: NT_STATUS_UNSUCCESSFUL". At this

I'm trying to get NTLM authentication working with Dovecot to authenticate Postfix SMTP clients. I can authenticate postfix smtp clients using the plain text login mechanism through winbind. However, using the NTLM mechanism gives me an error in my maillog that says: "dovecot: auth: winbind(?,10.20.2.0): user not authenticated: NT_STATUS_UNSUCCESSFUL". At this point, I'm

On 2019-02-13, Mark Foley via dovecot <dovecot at dovecot.org> wrote: > Is it possible that no one on this list is authenticating Outlook with Dovecot and NTLM? Yes, it's possible, the outdated instructions you found on the wiki suggests it's an uncommon configiration. No actual answers from me, but it might give you some clues: > More on this ... > > I short-sheeted

The domain controler is Windows. The file Server is Linux/Samba. The clients are Windows. I've tested the access on a dozen different windows machines. Three of them used NTLM and failed. All the others used kerberos and succeeded. They're all in the same network, same domain. Maybe it's the windows version? But they're all Window 8 or 10, not a great deal of a difference between

How would samba forward any requests on to any other service ?       You can have sssd setup on a server if you also need to support things like ssh, sftp, and nfs but that is separate from samba's "Windows" services. Or do you mean it forwards NTLM requests to a different server ? Disabling NTLM altogether would be a useful feature if you are trying to minimize the attack

On Mon, 18 Feb 2019 10:17:16 -0000 Stuart Henderson wrote: > > On 2019-02-13, Mark Foley via dovecot <dovecot at dovecot.org> wrote: > > Is it possible that no one on this list is authenticating Outlook with Dovecot and NTLM? > > Yes, it's possible, the outdated instructions you found on the wiki > suggests it's an uncommon configiration. Hmmm, really? And yet

Hi I work for a medium sized University and have recently set up some new infrastructure to authenticate our wireless users of Active Directory. Every thing was working as expected or so I thought. I set up a monitoring script that performs an ntlm_auth every minute and it shows that the authentication is failing inconsistently but for around 5 minutes at a time (see below). There are two

Hai Amos, Thank you for your very clear responce.. few small questions.. Is there a way to setup the proxy for the following. 1) use negotiate kerberos for auth, ( which is working already for all domain joined machines ) 2) use a fall back that works, for now basic ldap works for non windows machines, and domain joined machines. 3) use any other fallback way for authentication users on windows

My setup : Debian Etch i386 httpd-2.0.61 configured with the following command "./configure --prefix=/opt/httpd-2.0.61 --with-mpm=worker --enable-so --enable-dav=shared --enable-unique-id=shared --enable-version=shared --enable-ssl=shared --enable-info=shared --enable-cgi=shared --enable-rewrite=shared --enable-cache=shared -- enable-disk-cache=shared --enable-deflate=shared"

... sorry wrong list.. but you can read it and learn from it.. :-)) Greetz, Louis >-----Oorspronkelijk bericht----- >Van: samba [mailto:samba-bounces at lists.samba.org] Namens >L.P.H. van Belle >Verzonden: dinsdag 18 augustus 2015 9:45 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] [squid-users] debian Jessie squid with >auth (kerberos/ntlm/basic) ERROR

Whenever a client uses kerberos as authentication, it succeeds. Whenever a client uses NTLM as authentication, it fails (logs bellow) since SSSD can't support NTLM. Thus my question: what can I do to prevent NTLM from being used?? [2018/10/09 17:49:29.507046,  2] ../source3/auth/auth.c:332(auth_check_ntlm_password)  check_ntlm_password:  Authentication for user [MYUSER] -> [MYUSER] FAILED

Hello list, I'm trying to set up ntlm authentication for using mod_auth_winbind. Unfortunately during the "ntlm dance" some errors occurs. It complains about Oversized message, Invalid request and ntlm_auth goes to defunc... ( broken pipe as we can see in apache error log file ) apache 31623 31578 1 19:25 ? 00:00:00 [ntlm_auth] <defunct> Log file from apache is

combor@gazeta.pl wrote: > Hello list, > > I'm trying to set up ntlm authentication for using mod_auth_winbind. > > Unfortunately during the "ntlm dance" some errors occurs. It > complains about Oversized message, Invalid request and ntlm_auth > goes to defunc... ( broken pipe as we can see in apache error log file ) > apache 31623 31578 1 19:25 ?