similar to: Fwd: Re: Fwd: Re: Fwd: Re: Kerberos and NTLMv2 authentication

Displaying 20 results from an estimated 600 matches similar to: "Fwd: Re: Fwd: Re: Fwd: Re: Kerberos and NTLMv2 authentication"

2019 Jun 19
2
Fwd: Re: Fwd: Re: Fwd: Re: Kerberos and NTLMv2 authentication
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
2019 Jun 19
2
Fwd: Re: Fwd: Re: Fwd: Re: Kerberos and NTLMv2 authentication
Hello, I performed a test in order to get access to my samba share with winbindd (and not sssd). For that, 1. I change the gid of domain users from 513 to 15513 (to match with the domain range 10000 - 14999) And verify my test user is part of 15513 2. Stop sssd and change nsswitch.conf like this : /passwd:???? files winbind// //shadow:???? files// //group:????? files //winbind// / 3.
2019 Jun 19
0
Fwd: Re: Fwd: Re: Fwd: Re: Kerberos and NTLMv2 authentication
On 19/06/2019 16:16, Edouard Guign? via samba wrote: > So I re run the test with domain users gid 14513 > > Still not working (sssd stopped, nsswitch.cnf with? "files winbind" > for passwd group, # net cache flush + restart winbindd smb) > > On the samba server : > # wbinfo -i MYDOMAIN\usertest > MYDOMAIN\usertest:*:10430:*14513*:user
2019 Jun 18
2
Fwd: Re: Fwd: Re: Fwd: Re: Kerberos and NTLMv2 authentication
Is it possible to make start DOMAIN range from 500 instead of 10000 ? I realized that all my gid are in range 500 to 600 and not in range 10000 - 14999 I thought? DOMAIN range 10000 - 14999 was reserved for DOMAIN users -------- Message transf?r? -------- Sujet?: Re: [Samba] Fwd: Re: Fwd: Re: Kerberos and NTLMv2 authentication Date?: Tue, 18 Jun 2019 16:25:39 -0300 De?: Edouard Guign? via
2017 Dec 06
2
GID range full!!
Am 2017-12-06 um 13:20 schrieb Stefan G. Weichinger via samba: > Could it somehow be the case that the kerberos-ticket between DM and DC > runs out after X hours or so? > > Just guessing ... found this thread https://lists.samba.org/archive/samba/2017-October/211476.html sounds quite similar - klist showed no Kerberos ticket, did a kinit ... dunno? I also see this: # tail
2017 Dec 04
2
GID range full!!
Twice this week I had a Domain Member Server "crash" A week ago I saw errors like this in log.winbindd-idmap: [2017/11/27 11:25:02.768090, 1] ../source3/winbindd/idmap_tdb_common.c:140(idmap_tdb_common_allocate_id) Error allocating a new GID [2017/11/27 11:25:02.768213, 1] ../source3/winbindd/idmap_tdb_common.c:68(idmap_tdb_common_allocate_id_action) Fatal Error: GID range full!!
2016 Dec 19
1
wbinfo -u does not listed trusted users, wbinfo -n works, idmap not working
On both Samba 4.5.1 member server and Samba 3.6.25 member server I tried the following command wbinfo –set-uid-mapping=35049,S-1-5-21-xx-xx-xxx-xxx this should have created a mapping entry consistent with the one on the domain controller for a trusted user But I got the following error failed to call wbcSetUidMapping: WBC_ERR_NOT_IMPLEMENTED As far as I can tell from network
2017 Dec 12
4
GID range full!!
Am 2017-12-06 um 15:03 schrieb Stefan G. Weichinger via samba: > > Did dbcheck on DC. 257 errors for 372 objects. > Jeez. Why? Where does that come from? > > From some updating? I am quite sure that I ran those checks back when I > converted the domain and wouldn't have skipped these errors IMO. > > example: > >
2024 Nov 13
1
tdb_expand overflow detected
Hello, I'm using samba416-4.16.11 on FreeBSD 14.1 (on ZFS, in a jail, with quotas on those filesystems, etc) I'm seeing these entries in my logs. Is this something which needs action? If not, I'll start ignoring them. Nov 11 19:00:45 tm samba-dcerpcd[7373]: [2024/11/11 19:00:45.852391, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Nov 11 19:00:45 tm samba-dcerpcd[7373]:
2024 Nov 19
1
tdb_expand overflow detected
On 19/11/24 02:27, Dan Langille via samba wrote: > On Wed, Nov 13, 2024, at 4:30 PM, Dan Langille via samba wrote: >> Hello, >> >> I'm using samba416-4.16.11 on FreeBSD 14.1 (on ZFS, in a jail, with >> quotas on those filesystems, etc) >> >> I'm seeing these entries in my logs. Is this something which needs >> action? If not, I'll start
2018 Jun 17
3
Connection problem due to tdb_lock failed
We are using Samba 4.6.15. We have users not being able to login. winbindd log shows this: [2018/06/14 14:48:44.300203, 0, pid=3228] ../source3/rpc_client/cli_pipe.c:3292(cli_rpc_pipe_open_schannel_with_creds) netlogon_creds_cli_get returned NT_STATUS_UNSUCCESSFUL [2018/06/14 14:53:43.896350, 0, pid=3228] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)
2015 Aug 25
2
Import USER and PASSWORD Samba3+OpenLadp TO Samba4
That's my ldif I can import successfully. The problem is not passing the password for the Samba4... dn: cn=usertest,cn=users,dc=dominio,dc=local objectClass: usertest sAMAccountName: usertest displayName: User Test homeDirectory: /home/usertest uid: usertest cn: usertest uidNumber: 10211 userPassword:: e1NTSEF9Mk1Ya0NSTGsxQjRDbGhmcnk5MTYybEFMOEVoTFowUkg= sn: usertest givenName: usertest --
2015 Aug 25
2
Import USER and PASSWORD Samba3+OpenLadp TO Samba4
Thank Rowland, imagine that your crystal ball is not working, my already broken a long time .... I want to know if anyone here in the list have been through a similar problem with my, no wonder the ldif anyone, just wonder if anyone else has had to import only users and Openldap passwords for Samba4. Again thank you for your huge and wonderful collaboration Rowland. -- View this message in
2024 Nov 18
1
tdb_expand overflow detected
On Wed, Nov 13, 2024, at 4:30 PM, Dan Langille via samba wrote: > Hello, > > I'm using samba416-4.16.11 on FreeBSD 14.1 (on ZFS, in a jail, with > quotas on those filesystems, etc) > > I'm seeing these entries in my logs. Is this something which needs > action? If not, I'll start ignoring them. > > Nov 11 19:00:45 tm samba-dcerpcd[7373]: [2024/11/11
2019 Jun 21
2
Samba winbind on redhat 7
On 21/06/2019 15:39, Edouard Guign? via samba wrote: > Hello, > > I am facing 2 issues now. > The first one is the more critical for me... > > 1. When I switch from sssd to winbind with : > # authconfig --enablekrb5 --enablewinbind --enablewinbindauth > --enablemkhomedir --update > > My sftp access did not work. Does it change the way to pass the login ? > I used
2019 Mar 12
3
sometimes users fails to login
Hello, I have Samba 4.6 as AD domain member and sometime the users fails to login, the issue disappear after some minutes. I have enabled log leve 10 and I can see the following errors: 2019/03/12 09:20:32.280799,  5, pid=15466, effective(0, 0), real(0, 0)] ../source3/lib/username.c:181(Get_Pwnam_alloc)   Finding user BITINTRA\U002489 [2019/03/12 09:20:32.281111,  5, pid=15466, effective(0,
2019 Jun 21
3
Samba winbind on centos 7 - "domain users" acls added
hello, My 2nd issue is about acls which are added by "Domain users". May you help me to solve it again ? Concerning this issue, on my samba share, I set permissions for the share "groups" located on /var/datashared for "domain admins" (rwx) and "domain users" (r-x) /var]# getfacl datashared/ # file: datashared/ # owner: root # group: root user::rwx
2012 Mar 22
2
Debugging tdb_oob log messages in samba 3.6
Hello samba list, We're trialling Samba 3.6 and on some of our systems I see the following type of messages in the smbd and winbind logs: [2012/03/16 17:28:59.038177, 0] ../lib/util/tdb_wrap.c:65(tdb_wrap_log) tdb(/var/lib/samba/messages.tdb): tdb_oob len 663932 beyond eof at 12288 [2012/03/16 17:28:59.038331, 0] ../lib/util/tdb_wrap.c:65(tdb_wrap_log)
2019 Feb 13
3
idmap backend ad well-known-sids 512 & 513
Hi, we are in the process of testing a migration from our NT Classic Domain with OpenLdap to Samba AD. In our test setup migration of all accounts, groups and computer accounts went well using the classicupgrade path. Next step now is testing how to add a member server for file server services. We were able to get the server to join the domain and also idmapping works mostly as expected.
2017 Dec 04
0
GID range full!!
On Mon, 4 Dec 2017 12:13:39 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > Twice this week I had a Domain Member Server "crash" > > A week ago I saw errors like this in log.winbindd-idmap: > > [2017/11/27 11:25:02.768090, 1] > ../source3/winbindd/idmap_tdb_common.c:140(idmap_tdb_common_allocate_id) > Error