similar to: audit logging

I ask because I would like to be reassured about it, because there are so many entries of this type in my logs. The windows workstations are joined to the domain. At users sessions log on, a script mounts the samba share on each windows users sessions. I do not understand why a workstation joined to the domain tries to auth against samba ; because only domain users can auth successfully

Hello, On my system, nssswitch is like this : passwd:???? files sss shadow:???? files sss group:????? files sss So I assumed that it works with SSSD, I do not notice any issue with Samba. My share is accessible, permissions acls are working. The only thing I noticed is maybe NTLMv2 is always used by default with Samba. /[2019/06/18 09:51:44.542476,? 3]

Hi, Since samba 4.7 I have setup auth logging, and while I can relate most failed passwords to users mistyping a password, there is one kind that I don't understand, happening across our samba-DCs. Things work without issues, but I'm just being curious. :-) > [2017/11/23 04:47:32.166753, 2] ../auth/auth_log.c:760(log_authentication_event_human_readable) > Auth: [Kerberos

The 2 commands works : # getent passwd MYDOMAIN\\usertest MYDOMAIN\\usertest:*:10430:14513:user TEST:/home/usertest:/bin/bash # getent group MYDOMAIN\\"Utilisateurs du domaine" MYDOMAIN\utilisateurs du domaine:x:14513: I have to put "Utilisateurs du domaine" instead of Domain\ Users because the Windows AD is a french AD. Le 19/06/2019 ? 12:32, Rowland penny via samba a

We have to Samba DCs and a couple of Synology NAS connected/bound to the Samba AD. On regular basis the Synology NAS (I believe Samba 4.4.16) looses its connection to the AD outputting the error message, that the domain cannot be found. In the logs of the NAS I can only find the error message ?synowin: domain_test_join.c:59 net ads test join fail?. In the logs of the DC I notice that from one

Hi! My DC is running Samba 4.8.2(Ubuntu 16) I have windows 2016(member domain), running IIS... But my site in IIS, use user the DC (in portal), but now dont worked , is much erro in log.samba when autentcation in site with user dc... Any Idea? Regards ---------------------------- [2018/05/28 17:35:52.085263,  0] ../lib/util/fault.c:78(fault_report)  

Hi there, I'm trying to get FreeRADIUS to authenticate against my Samba DC. It's Samba 4.7.6-ubuntu running on Ubuntu 18 (kernel version 4.15.0-66-generic). It came nicely packaged with Zentyal, which provides a nice GUI for managing a domain, as well as a CA and lots of cool small features. That same Zentyal also includes support for FreeRADIUS (3.0.16). This is my smb.conf:

Hello I have a Problem with one windows 10 client. [2020/10/05 09:21:47.356628, 2] ../source3/auth/auth.c:334(auth_check_ntlm_password) check_ntlm_password: Authentication for user [ap31] -> [ap31] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1 [2020/10/05 09:21:47.356724, 2] ../auth/auth_log.c:610(log_authentication_event_human_readable) Auth: [SMB2,(null)] user [.]\[ap31]

Hi, all. I know this is ancient history, but I have a couple of DOS machines that host older device programming hardware. I've been able to access an older version of Samba for years without incident. Last weekend I upgraded my server to Ubuntu 18.04, which provides Samba 4.7.6. Unfortunately, after hours of frustration I find I'm unable to connect from any of the older machines.

Hello,     I recently upgrade Samba to 4.7.0 and enabled the Authentication and Authorization audit support. One of the first events I see is from a disabled user account. [2017/09/26 12:24:17.894767,  3, pid=1257, effective(0, 0), real(0, 0)] ../auth/auth_log.c:760(log_authentication_event_human_readable)   Auth: [Kerberos KDC,ENC-TS Pre-authentication] user [(null)]\[bdiley at

Hi everyone, we are running Samba version 4.19.3 on Rocky Linux 8.9. Recently we have been seeing errors like these for all Linux hosts in our network. Jan 11 15:36:55 dc4.REALM.COM samba[4339]: [2024/01/11 15:36:55.080863, 2] ../../auth/auth_log.c:876(log_authentication_event_human_readable) Jan 11 15:36:55 dc4.REALM.COM samba[4339]: Auth: [Kerberos KDC,ENC-TS Pre-authentication] user

I am soo lost trying to get Samba AD 4.7.5 as a Kerberos source for NFSv4. The NFS server is the Samba AD server running Ubuntu Server 16.0.4.3 and the client is Linux Mint 18.3 This export WORKS and mounts on client ########## /etc/exports ########## /mnt/fileshare         *(rw,no_subtree_check,async) ############################ This export DOES NOT ########## /etc/exports ##########

On Mon, 24 Dec 2018, Luke Barone via samba wrote: Thanks, Luke. Unfortunately that makes no difference. Still getting: Error 5: Access has been denied at the MS_DOS console. > Try adding "server max protocol = nt1" in the [global] section? > > On Mon, Dec 24, 2018 at 1:59 PM Steven Hirsch via samba < > samba at lists.samba.org> wrote: > >> Hi, all.

Out of curiosity: is QNAP as bad as Synology or is there another ?mainstream? NAS solution with more vanilla Samba out there? Alexander On 25. March 2020 at 11:40:08, Ralph Boehme via samba (samba at lists.samba.org) wrote: Am 3/25/20 um 11:36 AM schrieb Rowland penny via samba: > Thanks Ralph, didn't know that, but shouldn't they provide source code > somewhere ? they

Hello guys Yesterday afternoon kerberos stopped working on both of our domain controllers. Unfortunately, I did not have time to examine it thoroughly, I needed to have it up asap. I know that RDP authentication took a few minutes, but it ended up being logged. LDAP was normally working. There were a lot of these messages in the logs: [2018/04/22 14:46:43.315705, 1]

I did not set max protocol to SMB2 in smb.cnf, I don't want to force SMB2 selection if SMB3 can be used by a client. The machine is a Windows 7, so is SMB2 compliant. Le 22/07/2019 ? 11:44, Gaiseric Vandal via samba a ?crit?: > I would guess that changing the min protocol does not affect existing > connections unless you were to restart samba. > > Is the max protocol set to at

Hello, We had a strange thing happen today - we shut down our system (virtual machines) so that some work could be done in the server closet and everything was shut down gracefully but when everything was started back up I can no longer access my file server from windows. I get the following message in windows: \\fs1 is not accessible. You might not have permission to use this network

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

On 18/06/2019 19:49, Edouard Guign? via samba wrote: > ?gidNumber for 'Domain Users' is 513 > > not in range? '10000-14999' of uidNumber > > Is it a problem ? Oh yes, ALL user uidNumber's and Domain Users gidNumber MUST be inside the DOMAIN range you set in smb.conf, if they aren't, all your users WILL be ignored by Samba. Find the next available

On 24/04/2020 11:38, Enrico Morelli via samba wrote: > On Thu, 23 Apr 2020 08:08:39 +1200 > Andrew Bartlett via samba <samba at lists.samba.org> wrote: > >> On Wed, 2020-04-22 at 20:01 +0100, Rowland penny via samba wrote: >>> On 22/04/2020 19:25, Enrico Morelli via samba wrote: >>>>> On 22/04/2020 16:06, Enrico Morelli via samba wrote: