Displaying 20 results from an estimated 30000 matches similar to: "GPO Problem"
2017 Jun 06
2
GPO Problem
2017-06-06 15:54 GMT-03:00 Rowland Penny via samba <samba at lists.samba.org>:
> On Tue, 6 Jun 2017 15:35:42 -0300
> Epsilon Minus via samba <samba at lists.samba.org> wrote:
>
>> Hi. I have a problem applying GPO. I do not know where to look
>> Reviewing I found this:
>>
>> # samba-tool ntacl sysvolcheck
>> lp_load_ex: refreshing parameters
2017 Jun 13
2
GPO Problem
Thanks Elias.
But I run samba-tool ntacl sysvolreset and:
root at DC02:~# samba-tool ntacl sysvolreset
lp_load_ex: refreshing parameters
Initialising global parameters
Processing section "[global]"
Processing section "[netlogon]"
Processing section "[sysvol]"
Processing section "[sistemas]"
ldb_wrap open of idmap.ldb
lp_load_ex: refreshing parameters
2019 May 26
2
GPO problem ACL permission
Hello. I have a problem with GPO manage. Sorry for my english is not the best.
On the windows, GPO manage, the system send me this error:
"The permissions for this GPO in the SYSVOL folder are inconsistent
with those in Active Directory. It is recommended that these permissions
be consistent. To change the SYSVOL permissions to those in Active
Directory, click OK.
For more
2017 Jun 07
0
GPO Problem
Maybe this link help.
https://wiki.samba.org/index.php/Updating_Samba#Fixing_Incorrect_Sysvol_and_Directory_ACLs
On Tue, Jun 6, 2017 at 4:09 PM, Epsilon Minus via samba <
samba at lists.samba.org> wrote:
> 2017-06-06 15:54 GMT-03:00 Rowland Penny via samba <samba at lists.samba.org
> >:
> > On Tue, 6 Jun 2017 15:35:42 -0300
> > Epsilon Minus via samba <samba at
2017 Jun 13
0
GPO Problem
>
> onnect_acl_xattr: setting 'inherit acls = true' 'dos filemode = true' and
> 'force unknown acl user = true' for service Unknown Service (snum == -1)
> connect_acl_xattr: setting 'inherit acls = true' 'dos filemode = true' and
> 'force unknown acl user = true' for service Unknown Service (snum == -1)
> lp_load_ex: refreshing
2017 Jun 15
2
samba-tool ntacl sysvolreset ERROR
This is my smb.conf
root at DC02:~# cat /etc/samba/smb.conf
# Global parameters
[global]
workgroup = CLINICAGUEMES
realm = CLINICAGUEMES.COM.AR
netbios name = DC02
server role = active directory domain controller
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
winbindd, ntp_signd, kcc, dnsupdate
idmap_ldb:use rfc2307 = yes
ldap server require strong
2017 Jun 06
0
GPO Problem
On Tue, 6 Jun 2017 15:35:42 -0300
Epsilon Minus via samba <samba at lists.samba.org> wrote:
> Hi. I have a problem applying GPO. I do not know where to look
> Reviewing I found this:
>
> # samba-tool ntacl sysvolcheck
> lp_load_ex: refreshing parameters
> Initialising global parameters
> Processing section "[global]"
> Processing section
2015 Oct 04
2
sysvol acl's broken beyond repair
ok, I've investigated the problem more closely. First of all, I didn't
mention that I have 2 domain controllers: dc(initial) and bdc (backup).
Rsync command
/usr/bin/rsync -XAavz --delete-after dc:/usr/local/samba/var/locks/sysvol/*
/usr/local/samba/var/locks/sysvol/
fires every 5 minutes on bdc.
However, if I try to gpupdate from bdc I get the above error. Gpupdating
from dc works
2017 Oct 26
4
sysvolcheck on fresh samba 4.7 DCs
Hi,
I joined a new samba-4.7 DC to our AD, replicated everything over, then
turned off the old DCs, seized fsmo roles, and added two extra 4.7 DCs.
Everything above succeeded without warnings, and everything seems to be
running very well finally, except for the sysvolcheck / sysvolreset.
We're on xfs, and the File System Support checks on the samba wiki page
all pass, although at the
2017 May 31
2
Erro sysvolcheck/sysvolreset
Hi
My configuration:
smb.conf
# Global parameters
[global]
workgroup = MYSERVER
realm = interno.mydomain.com.br
netbios name = DC-LINUX
server role = active directory domain controller
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc,
drepl, winbindd, ntp_signd, kcc, dnsupdate
idmap_ldb:use rfc2307 = yes
ldap server
2013 Mar 19
1
samba-tool classicupgrade (from v3 to v4) aborts with "Unable to get id for sid"
I'm trying to upgrade from samba3 -> 4. I ran this command:
WORKDIR=/usr/local/mobius
/usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=$WORKDIR/var --use-xattrs=yes --realm=infinityhealthcare.com $WORKDIR/smb.conf
but it failed with the error given in this email's subject. What does it mean, and how do I fix it?
This is just another is a growing line of errors that
2015 Aug 11
4
Error
Hello list, today I update de the version of samba, 4.2.3, when I run this tool, I have this error.
1) - ./samba-tool gpo aclcheck
ldb_wrap open of secrets.ldb
GENSEC backend 'gssapi_spnego' registered
GENSEC backend 'gssapi_krb5' registered
GENSEC backend 'gssapi_krb5_sasl' registered
GENSEC backend 'spnego' registered
GENSEC backend 'schannel' registered
2017 Dec 05
3
Samba 4 AD issues with RPC
Hi Guys,
Setup:
Versions: Samba: 4.6.7
Bind9: 9.10.3
Firewall disabled
AD Provision:
Migrated from samba 3 to 4 using classic upgrade.
samba-tool domain classicupgrade --dbdir=/var/lib/samba.PDC/dbdir --realm=TEST.LOCAL --dns-backend=BIND9_FLATFILE /etc/samba.PDC/smb.PDC.conf
The following was the section in regards to the upgrade
Processing section
2013 Apr 05
2
ClassicUpgrade => EpicFail
ClassicUpgrade of my samba3 data to samba4 fails, with this error:
ERROR(<class 'passdb.error'>): uncaught exception - Unable to get id for sid
Full log of the classicupgrade is at the end of this email.
Project member on this list, Andrew Barlett, wrote that the issue is probably that my Samba 3 passdb was passable in an NT 4 DC mode, but is actually 'invalid' :
2019 May 26
0
GPO problem ACL permission
i don't know if the problem with the command samba-tool gpo aclcheck
is connect with the original problem, but is necesary resolv all
warinings.
I put de log level = 5 to check the report.
this is the output:
root at DC04:~# samba-tool gpo aclcheck
INFO: Current debug levels:
all: 5
tdb: 5
printdrivers: 5
lanman: 5
smb: 5
rpc_parse: 5
rpc_srv: 5
rpc_cli: 5
passdb: 5
2017 Jun 16
1
samba-tool ntacl sysvolreset ERROR
Or if you want to maintain the 'log level = 2' you can set just the 'vfs'
log level to 1 eg:
log level = 2 vfs:1
This way you are just silencing the bit that needs to be silenced, not the
whole of samba. If that's what you want, of course.
On 16 June 2017 at 07:06, Rowland Penny via samba <samba at lists.samba.org>
wrote:
> On Thu, 15 Jun 2017 20:00:42 -0300
>
2015 May 16
3
Samba 4.17 AD Cannot connect to shares as administrator
Hi,
I encountered a strange problem...some of my windows machines cannot be
joined to an Samba 4.17 AD domain (8 of ~90 clients). These are 7 Win7
clients and one WinXP client.
The message I receive in windows is: "Logon failure: unknown user name or
bad password".
All other Win7 and XP machines could be joined...the same OS image has been
used to install both the machines that could be
2013 Jun 02
2
dynamic DNS Updates still failing, re-installed 9 more times, tried everything I could think of, now bald.
I have tried everything, This is CentOS 6.4 with SELinux DISABLED, Bind
version BIND 9.8.2rc1-RedHat-9.8.2-0.17, samba 4.0.6 downloaded as a tar.gz
from samba.org -- I have read EVERY maillinglist, IRC Log, how-to on
google, tutorial on samba.org, and many many people have had this problem
and not once have any of the posters resolved it, so I am now a desperate
man reaching out to you with as
2015 Oct 03
2
sysvol acl's broken beyond repair
Hm, can I fix it manually? Maybe sysvolcheck stumbles on the first error
and misses something more severe later on.
2015-10-03 12:09 GMT+03:00 Rowland Penny <rowlandpenny241155 at gmail.com>:
> On 03/10/15 00:50, Krutskikh Ivan wrote:
>
>> Hi everyone.
>>
>> I ran into notorios gpo error on windows clients. When I go to my dc
>> controller and run
>>
2015 May 19
3
Samba 4.17 Cannot join Win7 clients to domain
Hi Davor,
thanks for the answer. They were actually part of a NT4 domain called
mayweg.net (the new realm name). But I did join workgroup "WORKGROUP"
before I tried to join the new domain.
If it's possible that they're sending the information the wrong way because
they were part of a workgroup named after the new realm, is there any way
to clear the old data (apart from a new