similar to: get access denied on samba AD share

Are there any logs on the client or server at a higher log level? Andrew Bartlett On Wed, 2020-05-20 at 12:39 +1200, Grant Petersen via samba wrote: > I forgot to mention that using the smbclient option > > -A /etc/cred/authfile > > behaves the same way as attempting to manually enter the password on > the command line; failing in 4.12.2 and working in 4.11.0 > >

I recently migrated our samba PDC to an LDAP backend on a test machine. Testing my account policies, I found out that the password lockout did not work. When authentication fail, samba seems to call init_ldap_from_sam asking to update the bad password count. When I set the lockout threshold to 1, the account is locked after a failed attempt and the badPasswordCount attribute is updated correctly

Hi, I'm facing to an issue where I cannot find solution. Here is the test case : * Samba 4.7, multi-server setup (multiple DC) * Windows 7 and Windows 10 client (not domain member) * Shares can be listed but no access to them in some case >From my workstation if I access to \\myserver.domain\myshare I get an error like "//UNC// is not accessible . you might

Hello!  I had working Samba installation on openSUSE Tumbleweed server.  I made my previous OS update a month ago, and everything worked fine after it.  But today I updated the OS again, and smb.service failed to start. Version 4.9.1-git.96.c3bff26bf16SUSE-oS15.5-x86_64 I tried many things: - minimal config - removed Samba package with all the dependencies and installed it again and so

On 24/06/2019 10:00, Stefan Froehlich via samba wrote: > On Mon, Jun 24, 2019 at 10:52:07AM +0200, Stefan Froehlich via samba wrote: >> <http://froehlich.priv.at/www/samba/> > Always try your own links before posting them... it must be > <http://froehlich.priv.at/samba/> of course, sorry. > No problem, I just refreshed the old page I had open ;-) You have this on the

If DNS is setup correct, then and your sure, then show ipconfig /all from a working and failing pc. And for i forget to mention. Did you check if the time is in sync? ( sorry must ask ) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Gaetan SLONGO via samba > Verzonden: dinsdag 29 augustus 2017 11:47 > Aan:

Would someone please tell me where I can find some good troubleshooting documents to resolve AD authentication issues when using Samba? Is this mailing list the best place? I was able to setup a working WINBIND-Samba setup on CentOS 7.6, but I am required to use SSSD on a different CentOS 7.6 server. Using a test VM, I can get services running, but I can't authenticate from a Mac or

I am googling around for an issue and can't figure it out so far. Status: 2 Debian 9.3 ADCs with samba-4.6.12 each. 1 Gentoo Samba Domain Member server "main", Samba version 4.5.15 (we downgraded because of another issue a month ago or so). *one* AD user is able to log into his Windows10 PC, but doesn't get a network share connected. If I test that from the DM server or the

Hello, I'm having a permissions problem I just can't quite figure out. I can not access any directory that is owned by my userid if the permissions are 700. If I change them to 770, with my default group on the directory, then I can access the directory. This was working fine with Fedora 19 for several years, and it broke when I upgraded to Fedora 22, and still broken with F23. my

On 24/06/2019 12:41, Stefan Froehlich via samba wrote: > On Mon, Jun 24, 2019 at 10:22:41AM +0100, Rowland penny via samba wrote: >> On 24/06/2019 10:00, Stefan Froehlich via samba wrote: >>> On Mon, Jun 24, 2019 at 10:52:07AM +0200, Stefan Froehlich via samba wrote: >>>> <http://froehlich.priv.at/www/samba/> >>> Always try your own links before posting

Hi team, Upgraded samba from 4.7.x to 4.9.3, when i tried to connect my public share using smb://ip/ through guest login in MAC my shares are not listed if i am connected to AD. 2019/01/03 18:56:31.351985, 3, pid=1114, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth.c:192(auth_check_ntlm_password) check_ntlm_password: mapped user is: []\[GUEST]@[HS-MBP-3] [2019/01/03

Mandi! Rowland penny via samba In chel di` si favelave... > Even though your users may have the same username in AD as in the NT4-style > domain, they are different users, so a few thoughts. You have 'map to guest > = bad user', so I take it you must have 'guest ok = yes' set in the shares > (you haven't shown us the shares), so try changing 'bad user' to

On 3/3/2016 2:02 PM, Marc Muehlfeld wrote: > It would help if you would provide some information about your system: > - Samba version - smb.conf - "ls -ld" of the directory - etc. Regards, > Marc Hello, version: samba-4.3.4-1.fc23.x86_64 ls -ld: ls -ld /home/blaster drwxrwx--- 76 blaster users 4096 Mar 3 14:15 /home/blaster testparm Load smb config files from

On Mon, 24 Sep 2018 17:33:47 +0200 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > Mandi! L.P.H. van Belle via samba > In chel di` si favelave... > > > I hope this helps you understanding your problem a bit more. > > See also: > > https://docs.microsoft.com/en-us/windows/security/identity-protection/access-control/local-accounts > > No,

I've just upgraded my DM from samba 4.5 to 4.8, using luois repos (also, debian jessie -> stretch). I'm experimenting some troubles on some shares, seems that both guest access and 'machine account' access does not work. The share is rather simple: [wpkg] browseable = No comment = WPKG Automated Software Deploying System force create mode = 0664 force directory mode =

Thanks for the suggestions! > The latter is easiest to deal with, replace it with a CNAME in the AD dns. I did the CNAME, but when I remove the netbios alias I can see the shares list when accessing \\aliasname, but then I'm not allowed into any of them. I tried rebooting the client but same result, and I also don't see anything in the logs :( > The first will require a bit more

Hi, I recently upgraded a smb server from Ubuntu 18.04 to Ubuntu 20.04 which required the Samba version to be upgraded from 4.7.6 to 4.15.13. Post the upgrade, winbind authentication fails with NT_STATUS_RPC_SEC_PKG_ERROR intermittently. The error goes away on restarting the smb service but comes back after some time. There were no isses with the setup before the upgrade. Tried clearing the

I have a Centos 7.6 server with samba 4.8.3  configured as a member of an AD domain using "ads' security and the "nss" idmap backend. Clients are unable to access the shares on the server - they repeatedly get asked for their credentials. The smbd log shows the user authenticating and a mapping from the user's SID to their unix uid is found. However, it seems that

Hai, 1) apparmor, disable it, and try again, so we can confirm if its an apparmor settings. 2) winbind is starting from systemd while as AD-DC you should disable that. - stop the member parts of samba and systemd. systemctl stop winbind smbd nmbd samba systemctl disable winbind smbd nmbd samba systemctl mask winbind smbd nmbd samba - enable the samba-ad-dc part in systemd.

Hi all, Just migrated users to a samba 4 server on built on Solaris 11 samba pkg. Some users are mapping all required drives (G:, H:, and I:) but some are not able to map them. The affected users user log files indicate that the %g variable is being translated to '-1' instead of the users Unix group. I would welcome any feedback or suggestions on how to resolve this issue. >From my