similar to: inconsistent winbind on upgraded member server

On 10/12/2016 1:34 PM, Mark Nienberg via samba wrote: > Well, the easy fix is to add this to the share definition: > > admin users = "@STA\domain admins" > > The wiki implies that this should not be necessary, so I don't know if the > wiki is wrong or if I failed to follow it correctly. This was my first > share using Windows ACLS and it was an interesting

On 10/12/2016 7:32 PM, Mark Nienberg wrote: > Yes, it looks like this: > > https://wiki.samba.org/index.php/Implementing_roaming_profiles#Profile_share_using_Windows_ACLs > > but as I say, it works now that I have added the admin users, so I am > satisfied for now. > > On Wed, Oct 12, 2016 at 11:31 AM, lingpanda101--- via samba > <samba at lists.samba.org

On Fri, Oct 7, 2016 at 12:38 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > have you given Domain Admins the required rights ? > > net rpc rights grant DOMAIN\\"Domain Admins" > SeDiskOperatorPrivilege -UAdministrator > Yes. I followed this wiki example: https://wiki.samba.org/index.php/Shares_with_Windows_ACLs Here is some output: [nienberg at

Yes, it looks like this: https://wiki.samba.org/index.php/Implementing_roaming_profiles#Profile_share_using_Windows_ACLs but as I say, it works now that I have added the admin users, so I am satisfied for now. On Wed, Oct 12, 2016 at 11:31 AM, lingpanda101--- via samba < samba at lists.samba.org> wrote: > On 10/12/2016 1:34 PM, Mark Nienberg via samba wrote: > >> Well, the

On Mon, Oct 17, 2016 at 10:24 AM, Mark Nienberg < mnlists at tippingstructural.com> wrote: > > On Mon, Oct 10, 2016 at 10:18 AM, Trenta sis via samba < > samba at lists.samba.org> wrote: > >> We have detected that machines with dhcp (It was configured as is >> described >> in samba wiki dhcp and samba 4) are updating correclty and any message >>

Sorry I should have said in my original post, this server is a NT4 style domain server. Looking in /var/log/samba I see log files with the machine names in the file names, so samba definitely knows the machine names. On Thu, Dec 18, 2014 at 1:17 PM, Ricky Nance <ricky.nance at gmail.com> wrote: > > Mark, I think (and I may be wrong here, so if a dev sees this correct me) >

On Wed, 19 Apr 2017 16:06:52 -0700 Mark Nienberg via samba <samba at lists.samba.org> wrote: > I'm working on a shell script to create new users on a AD DC. > Currently we use ADUC, but that is slow and error-prone. My > (untested) command looks like this: > > samba-tool user create $USERNAME $PASSWORD \ > --nis-domain=sta \ > --unix-home=/home/${USERNAME} \ >

I'm working on a shell script to create new users on a AD DC. Currently we use ADUC, but that is slow and error-prone. My (untested) command looks like this: samba-tool user create $USERNAME $PASSWORD \ --nis-domain=sta \ --unix-home=/home/${USERNAME} \ --uid-number=${NEXTID} \ --login-shell=/sbin/nologin \ --gid-number=513 \ --use-username-as-cn \ --home-drive=Z \

Mark, I think (and I may be wrong here, so if a dev sees this correct me) smbstatus works with sockets. With that being said, I don't think it has been updated to work with samba as an AD DC, but should still work fine on other configurations (member server, legacy DC, etc). If you are running with a non ad dc config, let us know, there may be a bug there. Ricky On Wed, Dec 17, 2014 at 5:12

Well, I created a bug report for this issue. Seems that none of the developers has picked up on it. https://bugzilla.samba.org/show_bug.cgi?id=13214 On 16 January 2018 at 19:47, Mark Nienberg <mnlists at tippingstructural.com> wrote: > > On Tue, Jan 9, 2018 at 7:34 AM, Kristján Valur Jónsson via samba < > samba at lists.samba.org> wrote: > >> >> I have

In Samba 4.1 I get the following output for smbstatus: Samba version 4.1.1 PID Username Group Machine ------------------------------------------------------------------- 2482 john Everyone 10.0.0.109 (ipv4:10.0.0.109:49178) 7364 george Everyone 10.0.0.60 (ipv4:10.0.0.60:49232) In Samba 3.6 it was like this: Samba version 3.6.24 PID

I'm investigating high CPU load on a domain member server (file server) after an upgrade from 4.5.5 to 4.6.2. The problem continued after a subsequent upgrade to 4.6.7. I turned up the log level to 3 for a short time and looked at the logs. One thing I notice is some entries like this: [2018/01/24 18:28:37.933498, 3] ../source3/auth/user_krb5.c:164(get_user_from_kerberos_info)

On Tue, 3 Nov 2020, Michael Hennebry wrote: > I tried to boot a Centos 8.2 install CD, > one burned with Centos-8-2-2004-x86_64-boot . > > In the setup, it persisted in telling me > that ethernet thing enp0s25 was disconnected. > Nyet. > 'Twas working several seconds previous and is working now. > This is a showstopper. > How do I debug it? I had the same thing

I'm using procmail as the local delivery agent for Maildir style mailboxes. I discovered that I was able to send mail to other users but was unable to send mail to myself. Examples from verbose procmail log: **** Successful message to another user **** procmail: [24589] Fri Jun 2 15:03:34 2006 procmail: Assigning

good afternoon, when entering into the domain an error occurs, the administrator has all the rights, but for some reason it is not possible to enter this server into the domain, samba 4.19.0, the log is attached GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'spnego'

I spoke too soon in my last email. My DNS is not working. The host commands from the AD DC how-to all fail with NXDOMAIN. nslookup says server can't find nikola.ozco.home. Basically the same message. Here is a dump of my many tries. ----------------------------------------------------------------------------------------------------------------- nikola ~ # export

Greetings, One of my biggest frustrations with CentOS 7 has been firewalld. Essentially all of the documentation just flat doesn't work. One common thing that needs to be done is to change the zone of an interface, however I've tried: firewall-cmd --permanent --zone=internal --change-interface=ens192 firewall-cmd --permanent --zone=internal --add-interface=ens192 I've also tried

https://bugzilla.netfilter.org/show_bug.cgi?id=1138 Bug ID: 1138 Summary: icmpv6 mld-listener-query not detcted Product: nftables Version: unspecified Hardware: x86_64 OS: SuSE Linux Status: NEW Severity: normal Priority: P5 Component: kernel Assignee: pablo at netfilter.org

On Nov 6, 2015 3:31 PM, "Nick Bright" <nick.bright at valnet.net> wrote: > > Greetings, > > One of my biggest frustrations with CentOS 7 has been firewalld. > > Essentially all of the documentation just flat doesn't work. > > One common thing that needs to be done is to change the zone of an interface, however I've tried: > > firewall-cmd

Hello there. I´ve been having problems with dynamic dns update by dhcp on my samba ADDC running on CentOS 7 on an RPI2. After a while, the dhccp_dyndns.sh stops stops being able to authenticate with named. for the longest time I was stumped with this, exploring all kinds of kerberos issues, but found out that *restartint* named did resolve the issue. I have finally traced this problem down to a