similar to: ulogd / ulogd packages?

On Tue, 2018-05-15 at 13:04 -0500, Chris Adams wrote: > Once upon a time, Adam Tauno Williams <awilliam at whitemice.org> said: > > Rules load automatically via the /etc/sysconfig/network- > > scripts/rules- > > {interface} files.??Routes added to /etc/sysconfig/network- > > scripts/routes-{interface} are always added to the default policy. > What are you

I need to add persistent routes to a policy routing table. I can add rules to an IP policy table after installing NetworkManager-config- routing-rules; but I have not found how to add routes to a table other than the specific table. Manually I do a: ip route add default via 192.168.1.6 dev ens192 table pods Rules load automatically via the /etc/sysconfig/network-scripts/rules- {interface}

Logon scripts assigned to a user do not execute when the user logs on; it did before the upgrade. I can run the script from the command line and it completes OK [like \\{DOMAIN}\netlogon\logon.bat]. I can also browse to the [netlogon] share without issue. Upgrade was from a late 4.0.x to 4.1.x to current 4.2.x. User's can logon without other issues [apparently]. Platform: CentOS7

Since upgrading S4 DCs I am see the following message in log.samba - DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested: FFFFFFF8Unable to fetch value for secret BCKUPKEY_13bb48fc-0844-4736-9972-e26453333856, are we an undetected RODC? DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested:

> > Initially, it appears to have worked. ... > > It shows the same on one of the S4 DCs, but the > > DomainDnsZonesMasterRole still shows as "no current owner" on the > > third S4 DC [all Sernet 4.5.2].  Argh. > You could try checking the database on the third DC, 'samba-tool > dbcheck --help' for more info. > You could also try forcing

I have a site with a working Samba4 AD domain with a single DC. It works. I've added three new DCs to the domain [using the SerNet packages for 4.0.21]. The intention is to then demote the old, original Samba4 DC. But problems exist for netlogon/sysvol. One of the new DCs - the second one added - works, clients can access netlogon & sysvol. However the other two DCs have ACL errors

I added three DCs to a single DC Samba4 AD domain. They initially replicated and came up - but replication does not appear to be ongoing. A change made to a user via MMC connected to one DC does not appear on another DC. It the logs I see bursts of the following message: [2014/08/12 15:08:08.026270, 0] ../source4/librpc/rpc/dcerpc_util.c:660(dcerpc_pipe_auth_recv) Failed to bind to uuid

On Mon, 2016-09-19 at 20:57 +0200, Marc Muehlfeld wrote: > > Logon scripts assigned to a user do not execute when the user logs > > on; it did before the upgrade. > * What kind of upgrade are you talking about? > NT4 to AD? (migration) > x.y to 4.2? AD 4.0.21 -> 4.2.x This worked prior to the upgrade. > * Is this an PDC or DC? They are DCs. > * Where have you

> You seem to be missing two FSMO roles: > DomainDnsZonesMasterRole > ForestDnsZonesMasterRole > Just what version of Samba are you using ? My Samba 4.5.2 domain also appears to be missing these roles. Can I simply seize these roles? [root at larkin27 ~]# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=TEMP2008R2DC,CN=Servers,.. InfrastructureMasterRole owner:

Am Donnerstag, 10. März 2016, 10:41:34 CET schrieb mathias dufresne: Hi, Mathias and all thank you for your answer. > Hi all, > > SPN = servicePrincipalName > > A simple search returning all servicePrincipalName declared in your AD: > ldbsearch -H $sam serviceprincipalname=* serviceprincipalname > For me: ldbsearch -H /var/lib/samba/private/sam.ldb serviceprincipalname=*

On Sun, 2015-04-12 at 16:14 -0400, Adam Tauno Williams wrote: > I removed a DC using the DC removal tool mentioned in > http://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3 > as https://bugzilla.samba.org/show_bug.cgi?id=10734 prevents normal DC > demotion. > The DC was still all over in DNS, so I had to pick it out. > Now replication between

On Mon, 2016-09-19 at 09:31 -0400, Adam Tauno Williams via samba wrote: > Package: sernet-samba-4.2.14-23.el6.x86_64 > These DCs were very recently upgraded from a prior version. > [2016/09/19 09:32:55.168161, 0] > ../source4/libcli/smb2/signing.c:116(smb2_check_signature) > Bad SMB2 signature for message of size 202 > ../source4/rpc_server/drsuapi/getncchanges.c:807: Failed

On Sun, 2016-11-20 at 21:11 +0000, Rowland Penny via samba wrote: > On Sun, 20 Nov 2016 15:55:08 -0500 > Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > > And it looks like nobody is listening on port 135 - > > [root at larkin26 ~]# netstat --listen --inet --program --numeric > > Active Internet connections (only servers) > > Proto Recv-Q

Hi all, SPN = servicePrincipalName A simple search returning all servicePrincipalName declared in your AD: ldbsearch -H $sam serviceprincipalname=* serviceprincipalname An extract from result concerning a lambda client: # record 41 dn: CN=win-client345,OU=Machines,DC=ad,DC=domain,DC=tld servicePrincipalName: HOST/MB38W746-0009 servicePrincipalName: HOST/MB38W746-0009.ad.domain.tld

On Tue, 2015-04-14 at 15:20 +0100, Rowland Penny wrote: > On 14/04/15 14:59, Adam Tauno Williams wrote: > > On Thu, 2014-10-30 at 13:41 -0300, Horacio G. de Oro wrote: > >> Hi! I'm trying to add a member to be used as fileserver, following the > >> guides at: > >> - https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server > >> -

On Mon, 2016-11-21 at 13:55 +1300, Andrew Bartlett wrote: > On Sun, 2016-11-20 at 16:50 -0500, Adam Tauno Williams via samba > wrote: > > On Sun, 2016-11-20 at 21:11 +0000, Rowland Penny via samba wrote: > > > On Sun, 20 Nov 2016 15:55:08 -0500 > > > Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > > > > And it looks like nobody is

I removed a DC using the DC removal tool mentioned in http://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3 as https://bugzilla.samba.org/show_bug.cgi?id=10734 prevents normal DC demotion. The DC was still all over in DNS, so I had to pick it out. Now replication between the remaining three DCs is broken [root at larkin26 ~]# samba-tool drs showrepl

What is the point of --save in yum-config-manager. I cannot figure out how to use --setopt= $ yum-config-manager --save --setopt="exclude=samba*" updates Seems evident what that should do, but it doesn't do anything. The documentation for --save says "save the current options (useful with --setopt)" I would like to script/automate some YUM configuration. -- Adam

On Wed, 2016-09-14 at 16:50 +0100, isdtor wrote: > > Not sure what would cause that error message, nor have I > > experienced it. Looks like other people have seen it: > > https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+wi > > th+%5BUnspecified+GSS+failure.++Minor+code+may+provide+more+informa > > tion:+No+credentials+cache+found > I found no way

> I tried adding the tun0 interface to the internal zone and firewall- > cmd?told me tun0 was managed by NetworkManager. After that it didn't > show?tun0 as a member of any zone. > #? firewall-cmd --zone=internal --add-interface=tun0 > The interface is under control of NetworkManager, setting zone to? > 'internal'. success > # firewall-cmd --list-all-zones >