similar to: samba4 missing group membership with getent group

Hi there, I have tested it too and have no crashes anymore. ("ll /opt/samba/var/locks/sysvol/" & "wbinfo --uid-info 3000000") Many thanks from me too. Mit freundlichen Gr??en ? Thomas Nolte -- Nolte Infosysteme,? Im Sikfeld 8, 38304 Wolfenbuettel Tel 05331-946210, Fax 05331-946211, Handy 0170-5508198 Computer, Netzwerk, Kommunikation www.nisx.de -----Urspr?ngliche

Hello, I made an interesting observation related to the "Clocksource tsc unstable (delta = -2999660320319 ns)" problem. In the log of ntpd I found: Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status change 6001 Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status change 2001 Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status change

Hi all, with this version, as in 4.0.5, i have always the windbind crash after wbinfo --uid-info 3000000 or ls -la sysvol/ my system 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux I already post here some information (no problem with 4.0.4, found last stable patch with bisect), could someone help me ? thanks and regards philippe > -----Original Message----- >

Hi there, just the same here. Problem still exists. I have testet the newest sernet ubuntu-packages (4.0.6-SerNet-Ubuntu-1.precise): Same Problem. Mit freundlichen Gr??en ? Thomas Nolte -- Nolte Infosysteme,? Im Sikfeld 8, 38304 Wolfenbuettel Tel 05331-946210, Fax 05331-946211, Handy 0170-5508198 Computer, Netzwerk, Kommunikation www.nisx.de -----Urspr?ngliche Nachricht----- Von:

On Tue, 27 Nov 2018 16:39:41 -0200 Marcio Vogel Merlone dos Santos via samba <samba at lists.samba.org> wrote: > Hi, > > I have a samba 4.7 AD DC running on a Ubuntu 18.04 server with distro > packages. I update a user with a new group and this new membership is > not reflected on that user. On example below, I can successfully add > the user "test.account" to

Hi, Sometimes, seemingly randomly, long-running Xen domains, using clocksource xen, have their clock shift by ~3000 or ~36000 seconds, often with the dom0 complaining about clocksource tsc. The number changes if the hypervisor is explicitly told to use clocksource=pit, but it still happens. It doesn''t seem to be particularly hardware-specific. See also http://bugs.debian.org/599161 I

Hi, I have a samba 4.7 AD DC running on a Ubuntu 18.04 server with distro packages. I update a user with a new group and this new membership is not reflected on that user. On example below, I can successfully add the user "test.account" to group "test", but not my user "marcio.merlone": root at araucaria:~# id test.account uid=30214(A1\test.account)

This patch attempts to address an issue some have reported where our nss_winbind is even slower than it's simple non-caching implementation needs to be. I think this comes from us not handling the BUILTIN domain properly, and so we constantly attempt to contact the DC, and then fail an internal validation step, throwing away that connection. I think this is also the cause of crashes folks

On 2/14/25 11:22, Rowland Penny via samba wrote: > Well yes, you can do it that way, but there is an easier way. > There is a group in AD called 'Domain Admins' > Add any AD users that you want to be domain administrators to that > group, then, using visudo add this line to the sudo config: > > %SAMDOM\\domain\ admins ALL=(ALL:ALL) ALL > > Where 'SAMDOM' is

Hi Rowland, Those tests were made on DC (araucaria), not a domain member. root at araucaria:~# testparm /etc/samba/smb.conf Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[netlogon]" Processing section "[sysvol]" Loaded services file OK. Server role: ROLE_ACTIVE_DIRECTORY_DC Press

On 22/04/2020 10:51, Oleg Blyahher via samba wrote: > Hi everyone, > > I'm running Samba 4.7.6 on Ubuntu 18.04. Might be an idea to upgrade Samba, 4.7.x is EOL as far as Samba is concerned, you can get later Samba versions here: http://apt.van-belle.nl/ > > I have an issue with adding users to groups with samba-tool, not > really sure where to look for more info. samba

On Fri, 14 Feb 2025 12:14:18 -0500 "John R. Graham via samba" <samba at lists.samba.org> wrote: > On 2/14/25 11:22, Rowland Penny via samba wrote: > > Well yes, you can do it that way, but there is an easier way. > > There is a group in AD called 'Domain Admins' > > Add any AD users that you want to be domain administrators to that > > group,

Hi everyone, I'm running Samba 4.7.6 on Ubuntu 18.04. I have an issue with adding users to groups with samba-tool, not really sure where to look for more info. samba -i didn't show anything at all. This is what I do: *samba-tool group add new-group** **samba-tool group addmembers new-group my-user* if I run *id my-user *or *groups my-user*, then the group *new-group *does not appear

Hi all, I am trying to setup an E100P for use on Swisscom E1-PRI here in Switzerland. Swisscom seems to use Siemens hardware. Here are my configs (cvs from a few hours ago) : zaptel.conf loadzone=fr ; tried "de" but got warning at modprobe defaultzone=fr span=1,1,0,cas,hdb3,crc4,yellow ; Seems to be right, as the Siemens SDSL-G703 modem switches its LEDs off ... not sure

I've been googling and reading a lot, but I'm not getting any closer to getting an SMS sent via Asterisk. Prior to switching to asterisk, I used sms_client on an ISDN line to dial one of two Swisscom SMS centers: 0900900941 or 0794998990. My dialplan looks like this: exten => 0900900941,1,Goto(smsmotx,${CALLERIDNUM},1) exten => 0794998990,1,Goto(smsmotx,${CALLERIDNUM},1) ;

Hi all, Just a little note for the records and archives. We see many small glitches / troubles in the mailing-list but rarely success stories ... Here's one : Asterisk is running perfectly fine in our setup : Debian 3.0 stable / Athlon 1.8, 256 MB Ram / Digium E-100P / Swisscom PRI isdn We have 6 companies (more to come) sharing the system in the building with a total of about 20

On Mon, 29 May 2017 23:01:43 +0200 (CEST) Sébastien QUESSON via samba <samba at lists.samba.org> wrote: > samba-tool group addmembers domaingroup 'SAMDOM\user1' > ERROR(exception): Failed to add members "SAMDOM\user1" to group > "domaingroup" - Unable to find "SAMDOM\user1". Operation cancelled. > > samba-tool group addmembers

samba-tool group addmembers domaingroup 'SAMDOM\user1' ERROR(exception): Failed to add members "SAMDOM\user1" to group "domaingroup" - Unable to find "SAMDOM\user1". Operation cancelled. samba-tool group addmembers 'SAMDOM\domaingroup' 'SAMDOM\user1' ERROR(exception): Failed to add members "SAMDOM\user1" to group

Hai, You must have mist something.. I did it as followed in the GPO settings. I created a "DOMAIN\Allow-RDP" group in the AD. Added users to this group. In the GPO, i used "default computer" Policies - Windows settings - security settings - Restricted groups. Here add your DOMAIN\Allow-RDP to the Remote Desktop Users. And - Windows settings - security settings

Hi, If I'm not mistaken, the Remote Desktop Users is a local group. Si as Said Louis, you'll have to create a domain group that will be added to the local group on each machin through GPO Regards, Le 02/03/2016 17:28, Martin Juhl a écrit : > Hi > > My next try is to create the group myself, but the point here was that the Builtin group created by the provisioning of Samba,