search for: thom_schu

Hi, all the users here are stored in a LDAP-Server, means authentication on a workstation (linux) is over LDAP. Yesterday I configured a Samba-Server, it also uses the LDAP-Server as its backend. I found out, that with a call "smbpasswd -a user" an existing user gets all the attributes from the sambaSamAccount automaticly. But here is my first question - for this call I need to know the

...ot;) I didn’t see it for USER object, but a lot of other objects. Andrej -----Ursprüngliche Nachricht----- Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von Andrew Bartlett via samba Gesendet: Samstag, 14. Oktober 2017 20:52 An: Garming Sam <garming at catalyst.net.nz>; thom_schu at gmx.de; samba at lists.samba.org Betreff: Re: [Samba] samba 4.7.0 replication errors On Mon, 2017-10-02 at 09:59 +1300, Garming Sam via samba wrote: > Can you provide a bit more logs? At first glance, it doesn't seem > quite related to group memberships. > I agree, we need more...

On Mon, 2017-10-02 at 09:59 +1300, Garming Sam via samba wrote: > Can you provide a bit more logs? At first glance, it doesn't seem quite > related to group memberships. > I agree, we need more logs here. Turn up the log level and see what the error causing that final error is.   However, take care not to publish confidential details like staff names and sensitive attributes like

> I faced the same problem, solved it by adding the line > import samba.drs_utils > to the file fsmo.py. > > When building samba yourself, from withtin the base directory you can > apply this patch file to do it for you: Thank you Nobert. Indeed the line "import samba.drs_utils" is missing, although I'm using the repositories from Sernet. According to

Hi, I want to upgrade samba 4.8.2 to samba 4.10.7. According to here: https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC#Rejoining_the_upgraded_DC best way is to rejoin the server after the upgrade. But also I need to upgrade the OS, in my case it means a new installation from the OS, because an upgrade is not possible, the old and the new version are to different. Can I do this the

> After demotion and reinstallation I joined DC1 with success again, but all SRV-entries (_kerberos, _ldap, _kpasswd) > were not generated. SOLVED, everything works fine. The DNS-SRV-entries were not generated, because after transferring the roles, the SOA-entries for all zones contained still the old DC which didnt exist anymore. I changed to the new PDC. Same for the DNS-entry

> Cleaned the DNS manually with the DNS application, but still I can't join. Same error. I thought it was the same error, but now I saw there is a small difference. It seems like a deleted object causes the problem. With "ldbsearch --cross-ncs --show-deleted .." I can see now that entry for "samba3" (beside all other demoted servers), which appears in the error message.

And (re)joining is not recommended ? There are so many services and computers connected to the samba server, which are not in my hand. Means after I upgraded all our 5 ADs I would have to inform many people about the new name and IP. Thanks

Hello, I made an upgrade from sernet-samba 4.3.11 to sernet-samba 4.6.7. With samba 4.3.11 all created users contained the objectclass "posixAccount". With samba 4.6.7 they don't. We have a NetApp-Storage-Server which exports nfs4-mounts (with kerberos). Yesterday I wanted to change the owner of a directory and "chown" threw an error "invalid argument". It was

> But with the DNS-Tool from Windows I can see a lot of entries for samba3, all of them for services like _gc, _kerberos, _ldap, _kpasswd. Cleaned the DNS manually with the DNS application, but still I can't join. Same error.

Hello, I transfered all fsmo-roles from a DC (4.3.11-SerNet, SLES 11 SP3) to another DC (4.6.6-SerNet, SLES 12 SP2). I had to try a couple of times because of an error "Failed FSMO transfer: NT_STATUS_IO_TIMEOUT" But then following error happened: samba-tool fsmo transfer --role=all This DC already has the 'rid' FSMO role This DC already has the 'pdc' FSMO role

Hello, now with "ldbsearch --cross-ncs ..." I dont find entries of domain controllers anymore except samba1 and samba2. sam.ldb seems to be clean now. But with the DNS-Tool from Windows I can see a lot of entries for samba3, all of them for services like _gc, _kerberos, _ldap, _kpasswd. Can this be the reason for the error I get when I join samba5 ? Do I have to delete this entries ?

> Get rid of samba3 by demoting it again as you did last time, search > through sam.ldb for any mention of samba3 and samba4 (you will > probably have to use '--cross-ncs' with ldbsearch or lbdedit), then > remove them. > Now start again with a new DC, but this time, call it anything but > samba3 or samba4. Getting worse and worse .... I demoted samba3 and then also

Hallo, we have 5 ADDCs. All of them did run with sernet-samba 4.6.7. I updated 4 of them to sernet-samba 4.7.0, one after the other, checked replication, everything seemed to be ok. One day later a colleague wanted to delete a lot of users with a powershell-script and since then the replication doesnt work anymore. (Im sure the script is not the problem, but it seemes like it triggered something)