search for: gassner

Displaying 4 results from an estimated 4 matches for "gassner".

Did you mean: gasser
2018 Jan 26
3
Replication Problem win2k8r2 uppercase Attribute
Hi, have the same Problem described in, https://lists.samba.org/archive/samba/2016-November/204659.html it should be fixed already, https://bugzilla.samba.org/show_bug.cgi?id=12399 my version 4.5.15 on Debian 8 i have one win DC and 10 samba DC's  is there a solution via "samba-tool dbcheck" or how is the procedure to fix it ? i did compare the databases and tried to
2018 Oct 18
2
AD error 8418: The replication operation failed because of a schema mismatch between the servers involved (WERR_DS_DRA_SCHEMA_MISMATCH)
On 2018-10-18 09:42, Andrew Bartlett via samba wrote: > On Thu, 2018-10-18 at 09:07 +0200, Noël Köthe via samba wrote: >> Hello, >> >> we are running a 2008 R2 AD (schema 47) with two DCs: >> * dc-win (Windows 2008 R2) >> * dc-samba (samba 4.5.12, Debian stable) >> >> Since some weeks replication works only from dc-win to dc-samba but not >> in
2018 Dec 10
0
AD error 8418: The replication operation failed because of a schema mismatch between the servers involved (WERR_DS_DRA_SCHEMA_MISMATCH)
Hello Matthias, Am Donnerstag, den 18.10.2018, 11:15 +0200 schrieb Matthias Gassner via samba: > > > we are running a 2008 R2 AD (schema 47) with two DCs: > > > * dc-win (Windows 2008 R2) > > > * dc-samba (samba 4.5.12, Debian stable) ... > i had this problem to, in my case the the characters in the LDAP paths > was not in capital. > > like...
2018 Dec 10
1
AD error 8418: The replication operation failed because of a schema mismatch between the servers involved (WERR_DS_DRA_SCHEMA_MISMATCH)
On Mon, 10 Dec 2018 12:57:35 +0100 Noël Köthe via samba <samba at lists.samba.org> wrote: > Hello Matthias, > > Am Donnerstag, den 18.10.2018, 11:15 +0200 schrieb Matthias Gassner > via samba: > > > > > we are running a 2008 R2 AD (schema 47) with two DCs: > > > > * dc-win (Windows 2008 R2) > > > > * dc-samba (samba 4.5.12, Debian stable) > ... > > i had this problem to, in my case the the characters in the LDAP > > p...