[Samba] Trust relationship fails after classicupgrade

[Andrey Repin]

Greetings, Timo Altun!

> Hey Louis,

> thanks for the answer! That sounds like a viable route to go. Of course I'd
> prefer doing the classicupgrade and having the trust relationship still
> intact. It did work this way at some point during testing, that's why I
> find it hard to accept that I have to circumvent the problem like this.
> Did somebody else lose trust relationships after classicupgrade and found a
> way to restore them? I didn't find much information on this on
> Google...only advice is to rejoin the machines to the new domain...I know
> that works.

> Maybe I still have some errors or missing parameters in my configs on the
> AD DC?

You have a dot in Workgroup name.

> As always, any hints where this problem might originate from are
> highly appreciated!

> Next I'll probably try to purge all samba from the AD DC and try again.

> Greetings,
> Timo

> *smb.conf*
> [global]
> workgroup = MAYWEG.NET
> realm = INTRANET.MAYWEG.NET
> netbios name = SERVER06
> server role = active directory domain controller
> server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind,
> ntp_signd, kcc, dnsupdate
> idmap_ldb:use rfc2307 = yes

> [netlogon]
> path = /var/lib/samba/sysvol/intranet.mayweg.net/scripts
> read only = No

> [sysvol]
> path = /var/lib/samba/sysvol
> read only = No


-- 
With best regards,
Andrey Repin
Wednesday, April 15, 2015 14:34:24

Sorry for my terrible english...