similar to: 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

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: > >

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

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

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.

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 TEST:/home/usertest:/bin/bash In log, I have : myw7worstation.log /[2019/06/19 12:04:29.496822,? 1]

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

Am 2017-12-12 um 15:59 schrieb Stefan G. Weichinger via samba: > [2017/12/12 15:55:55.186723, 1] > ../source3/winbindd/idmap_tdb_common.c:68(idmap_tdb_common_allocate_id_action) > Fatal Error: GID range full!! (max: 2999) > [2017/12/12 15:55:55.186736, 1] > ../source3/winbindd/idmap_tdb_common.c:140(idmap_tdb_common_allocate_id) > Error allocating a new GID > > for

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

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

Hai,   I had some users today that couldnt login. Windows stopped at the “Welcome” screen.     Now, i checked the logs and i noticed a change in winbind. i noticed 2 logs files with increase a 1000% in size.  log.winbindd-idmap and log.wb-NTDOM     Before ( samba 4.4.5 ) log.winbindd-idmap [2016/09/30 11:32:37.040567,  0] ../source3/winbindd/winbindd.c:280(winbindd_sig_term_handler)

Hello, I'm currently stuck with a QNAP NAS appliance (don't buy this !) I have a Sernet Samba 4.5 as an AD controller and my QNAP have a Samba 4.0.25 (latest update) All i want is to join the QNAP to the AD, the QNAP will act as the file server. The join in the official way is okay but the uid / gid mapping is f*cked. I tried almost everything, change the idmap,

Dear Rowland, Please find a dump of smb.conf and resolv.conf of my centos 7 server : # testparm Load smb config files from /etc/samba/smb.conf Loaded services file OK. Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions # Global parameters [global] client min protocol = SMB2 client signing = required disable spoolss = Yes domain

Am 2017-12-04 um 12:42 schrieb Rowland Penny: > II take it that 'arbeitsgruppe' is the workgroup name, it should be > 'ARBEITSGRUPPE' in the 'idmap config' lines. The output of testparm shows them lowercase, smb.conf has it in uppercase: [global] security = ADS workgroup = ARBEITSGRUPPE realm = arbeitsgruppe.hidden.tld log file =

Hello, Samba 4.4.7 AD member on Linux SLES 12 here ... We've been running flawlessly for weeks with version 4.4.5 until we updated to 4.4.6 and experienced this bug: https://bugzilla.samba.org/show_bug.cgi?id=12369 So we updated to 4.4.7 in which this issue was fixed with an interim downgrade to version 4.4.5 until 4.4.7 was available. Now, we're experiencing another issue and it seems

Hello! This is my first email to the Samba mailing list :) We have been having an issue on our servers where the winbind service begins to utilize 100%~ CPU and logs the following error: *winbindd: Exceeding 200 client connections, no idle connection found* We have been running Samba *3.6.3-0.52.5*, however when originally investigating the problem, it was found that *3.6.3-0.58.1* included a

Here are the lines of the winbind.log justs after a restart of winbind: [2024/09/25 07:32:24.878544,? 1] ../../source3/winbindd/wb_lookupsid.c:102(wb_lookupsid_recv) ? Failed with STATUS_SOME_UNMAPPED. [2024/09/25 07:32:41.921563,? 0] ../../source3/winbindd/winbindd_dual.c:1964(winbindd_sig_term_handler) ? Got sig[15] terminate (is_parent=1) [2024/09/25 07:32:42.042654,? 0]

I review a few other servers, all 4.4.5 works fine. The few i test now with 4.4.6 all the same errors in the logs. The smb.conf of this setup. P.S. This server is accessed only by windows clients so this is why all the shares have : acl_xattr:ignore system acl = yes [global] workgroup = NTDOM security = ADS realm = INTERNAL.DOMAIN.TLD netbios name = MEMBER1 # Prio member

On Sun, 2 Sep 2018 22:37:05 -0400 Jamie Jackson via samba <samba at lists.samba.org> wrote: > Thanks for the workaround, Luca. I might end up going with: > > #!/bin/bash > getent group | grep -q 'Domain Users' && exit 0 > echo "restarting winbind" > sudo systemctl restart winbind > > > Rowland, it crashed again. Here's some info.

I happily and trustfully use Louis' backup-script from https://github.com/thctlo/samba4 to dump AD content via cronjob. Is it necessary/recommended to do that on *each* samba DC? Is there something server-specific in the dump(s) or is it enough to do that once per domain? thanks ...