similar to: testparm comaprison

Hi, Thanks, Well winbind enum is needed, and ntlm auth is required by some applications, seems that samba has disabled by default but windows has enabled, we have to migrate some old applications I understand taht is OK with yout comments thanks Missatge de Trenta sis <trenta.sis at gmail.com> del dia dl., 23 de set. 2019 a les 11:22: > > Hi, > > I have used testparm. >

Thanks, ntlm auth is temporary until we have solved some issues getent is needed by filesystem acl thanks for all Missatge de Trenta sis <trenta.sis at gmail.com> del dia dl., 23 de set. 2019 a les 12:37: > > Hi, > > Thanks, Well winbind enum is needed, and ntlm auth is required by some > applications, seems that samba has disabled by default but windows has > enabled, we

Hi, I have used testparm. smb.conf from dc1 4.4.5 # Global parameters [global] bind interfaces only = Yes interfaces = lo eth0 eth0:0 netbios name = server1 realm = DOMAIN.COM server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate workgroup = DOMAIN server role = active directory domain

Not possible, I do not have a Windows AD DC, but I don't doubt it works, probably because windows has a similar work around to 'samba-tool group listmembers Domain\ Users' --> Correct this command returns correctly the users Can you create a file on the netapp that ends up belonging to 'username:Domain Users' ? --> Correct fiel created without issues Does 'getent

Hi, If you try net group /domain "Domain Users" in samba domain with domain users as primary group any user is showed, but If you try the same in a native AD then users are listed, try this to reproduce the error Thanks 2018-02-12 20:24 GMT+01:00 Trenta sis <trenta.sis at gmail.com>: > Hi Rowland, > > Not really sure if that is correct, tried with native AD and domain

Hi, during a demote of an online and working DC I receive this error dsreplicasync failed (8440 'werr_ds_dra_bad_nc') Any suggestion where could be the issue, server is not really demoted Server is samba 4.4.5 and other server that has fsmo roles is 4.10.7 Thanks

Hi, I have to upgrade 2 different samba AD DC (2 domains) from 4.4.5 to 4.10.7 First is a single server and updaded with in-place upgrade from 4.4.5 to 4.10.7 and all perfect Second environment I need to add a second dc and also upgrade existing server, and I have some question about how to do this: - join second domain server with 4.10.7 - then make in place upgrade on existing server dc1?

Thanks Rowland!!! Missatge de Trenta sis <trenta.sis at gmail.com> del dia dj., 5 de set. 2019 a les 11:52: > > Hi, > > Thanks for your information about DNS config. > About second server and update, I understand that First I have to > transfer role to new added, demote old, and then rejoin and transfer > fsmo roles to source server, right? > My question is related

Hi, About duplicate issues warning during join, What I can do to find and solve this errors? I like to investigate source of this issue and solve this errors before join Thanks Missatge de Trenta sis <trenta.sis at gmail.com> del dia dt., 10 de set. 2019 a les 11:14: > > Hi, > > About duplicate issues warning during join, What I can do to find and > solve this errors? >

Hi, I'm making tests to migrate our actual 4.4.5 to a latest versions and add a second dc. I have added a second dc with 4.10.7 and seems to work fine, now I have 4.4.5 with fsmo roles and a second dn with 4.10.7, but reading wiki https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC seems that since latest days some changes about steps to upgrade, now seems that is recommended to us

On Thu, 2019-09-19 at 09:49 +0200, Trenta sis via samba wrote: > hi > Sorry, error is > > ldb_key_value/ldb_kv_index.c:2413: duplicate attribute value in > CN=server,OU=servers,DC=DOMIAN,DC=COM for index on > servicePrincipalNAme, duplicate og objectGUID > 931a3f57-1062-423e-9488-695700b197b0 in > @INDEX:SERVICEPRINCIPALNAME:WSMAN/OLD-SERVER > > multiple errors liek

Hi Andrew, thanks for you information, but I have some question, I'm not a samba expert... Sorry! Not that issue, but a very well known one. The trouble is, Samba 4.4 was happy to get a tree like this: X | | Y Z in an order like this: Step 1 Y Step 2 Y Z Step 3 X | | Y Z As long as everything worked out in the end, it was fine. But this had issues, so we patched it to instead

Hi, After reading wiki documentation about join I have tested to join a second dc, but with problems. I need to add a second controller to our AD, and then upgrade existing server (4.4.5) and I have tried to join a new DC 4.10.7 to 4.4.5 server but I receive join errors, attached output wit and without debug: I have executed samba-tool dbcheck --cross-ncs all seems OK I have made a test

Hello All, We have interesting issue. When application connect to PDC by port 389 (without ssl) everything works fine. When we try to use SSL by port 636 we have issue. ldapsearch -x -D "cn=user,ou=users,dc=dc,dc=local" -p 636 -h PDC -b "DC=dc,DC=local" -w pass output: ldap_result: Can't contact LDAP server (-1) ldapsearch -x -D

Hi, I'll try to give information asked in preious messages: - We have only one samba Domain controller and one dns (bind in same samba server) - Our domain doesn't have any .local - avahi is not running and we use debian lenny - This is a samba 4 AD domain, migrated form samba 3 nt domain using classic upgrade as it is described in samba wiki - problem is reported in lan network, is not a

Hi, I have searched and not found waht tls versions are supported with samba 4.4.5 as AD. IS tls 1.2 supported with samba 4.4? If not what version? Thanks

Hi, below the required files: smb.conf of ucs master: [global] logging = file max log size = 0 netbios name = ucs server role = active directory domain controller name resolve order = wins host bcast server string = Univention Corporate Server server services = -dns -smb +s3fs -nbt server role check:inhibit

hi rowland, after migration one of past migration tasks were generare reverse zone and add alla and ptr manually. I have made some additional tests and seemsthat if we shutdown samba domain controller or disconnect network then we can access with \\ip with two domain members server, and then if we reconnect network in samba ad server we reproduces error with \\ip any solution? thanks

Hi, Recently we have migrated from samba 3 nt domain to samba 4 AD (4.4.5) and we have detected that some applications are not working correctly, this applications need to access to \\ip resource, with name works, but we have some applications that needs to work only by ip Also detected this problem with some cname in dns are not responding we use bind9 + dlz, and we if we access from \\name

Sorry, but I didn't really know how to word this. I have Univention Corporate server running as AD DC, with a UCS running as a member fileserver. One win10 client has file permission issues after lack of reboot or logout/login in roughly a weeks time. Symptom = can't write to shares even though permissions are correct. Sometimes files are created without honoring default ACL. Could this