The AD connect sync to office365 also works with 4.10.18 i can not test with 4.11.x because on this version there is another bug requarding adding DNS records. so: 4.10.x -> the sync works 4.11.x -> i can not test 4.12.6 -> the sync fails with Errorcode: 0x55 Am Mittwoch, den 30.09.2020, 20:45 +0000 schrieb Heinz H?lzl via samba:> Hi, > > > I have downgraded a DC to version 4.10.7, > and so the fullimport and fullsync to the "azure AD" worked as > expected. > > when i sync from a DC with 4.12.6 the sync fails, alway with the > errors: > stopped-connectivity - failed-search - timeout - Errorcode: 0x55 > > > when i sync from a DC with 4.10.7 the sync works fine. > > > So I have to run at least 1 DC with the old version 4.10.7 and can > not > upgrade. > > > > Is there a way to fix this? > > > Regards, > Heinz > > > > > we use "Azure AD connect" to sync users from the samba-AD to > > office365. > > > > > > The synchronization worked fine for about 2 years. > > > > Now I get an error when I start a full import: > > > > stopped-connectivity - failed-search - timeout - Errorcode: 0x55 > > > > > > I'm not sure if it has happened since upgrading from 4.10.5 to > > 4.12.6 > > or if it is due to the increased amount of users. > > > > I have to do a fullsync because more containers have been added for > > sync. > > > > Any ideas? > > > > > > my system: > > 4 DCs with samba 4.12.6 running on ubuntu 20.04 > > > > > > Regards, > > Heinz > > > > p.s. > > it wasn't my idea to use office365 ;-)
Hi, I want to ask: the AD connect in 4.10.x work and sync also group members? Luk?? In 4.10.x Dne 02. 10. 20 v 15:16 Heinz H?lzl via samba napsal(a):> The AD connect sync to office365 also works with 4.10.18 > > i can not test with 4.11.x because on this version there is another bug > requarding adding DNS records. > > so: > 4.10.x -> the sync works > 4.11.x -> i can not test > 4.12.6 -> the sync fails with Errorcode: 0x55 > > > > > Am Mittwoch, den 30.09.2020, 20:45 +0000 schrieb Heinz H?lzl via samba: >> Hi, >> >> >> I have downgraded a DC to version 4.10.7, >> and so the fullimport and fullsync to the "azure AD" worked as >> expected. >> >> when i sync from a DC with 4.12.6 the sync fails, alway with the >> errors: >> stopped-connectivity - failed-search - timeout - Errorcode: 0x55 >> >> >> when i sync from a DC with 4.10.7 the sync works fine. >> >> >> So I have to run at least 1 DC with the old version 4.10.7 and can >> not >> upgrade. >> >> >> >> Is there a way to fix this? >> >> >> Regards, >> Heinz >> >> >> >>> we use "Azure AD connect" to sync users from the samba-AD to >>> office365. >>> >>> >>> The synchronization worked fine for about 2 years. >>> >>> Now I get an error when I start a full import: >>> >>> stopped-connectivity - failed-search - timeout - Errorcode: 0x55 >>> >>> >>> I'm not sure if it has happened since upgrading from 4.10.5 to >>> 4.12.6 >>> or if it is due to the increased amount of users. >>> >>> I have to do a fullsync because more containers have been added for >>> sync. >>> >>> Any ideas? >>> >>> >>> my system: >>> 4 DCs with samba 4.12.6 running on ubuntu 20.04 >>> >>> >>> Regards, >>> Heinz >>> >>> p.s. >>> it wasn't my idea to use office365 ;-)
Hi, I don't know because we're only syncing users without password syncing. We don't sync groups. Heinz Am Freitag, den 02.10.2020, 21:46 +0200 schrieb Luk?? Bernard via samba:> Hi, > > I want to ask: the AD connect in 4.10.x work and sync also group > members? > > Luk?? > > > > In 4.10.x > > Dne 02. 10. 20 v 15:16 Heinz H?lzl via samba napsal(a): > > The AD connect sync to office365 also works with 4.10.18 > > > > i can not test with 4.11.x because on this version there is another > > bug > > requarding adding DNS records. > > > > so: > > 4.10.x -> the sync works > > 4.11.x -> i can not test > > 4.12.6 -> the sync fails with Errorcode: 0x55 > > > > > > > > > > Am Mittwoch, den 30.09.2020, 20:45 +0000 schrieb Heinz H?lzl via > > samba: > > > Hi, > > > > > > > > > I have downgraded a DC to version 4.10.7, > > > and so the fullimport and fullsync to the "azure AD" worked as > > > expected. > > > > > > when i sync from a DC with 4.12.6 the sync fails, alway with the > > > errors: > > > stopped-connectivity - failed-search - timeout - Errorcode: 0x55 > > > > > > > > > when i sync from a DC with 4.10.7 the sync works fine. > > > > > > > > > So I have to run at least 1 DC with the old version 4.10.7 and > > > can > > > not > > > upgrade. > > > > > > > > > > > > Is there a way to fix this? > > > > > > > > > Regards, > > > Heinz > > > > > > > > > > > > > we use "Azure AD connect" to sync users from the samba-AD to > > > > office365. > > > > > > > > > > > > The synchronization worked fine for about 2 years. > > > > > > > > Now I get an error when I start a full import: > > > > > > > > stopped-connectivity - failed-search - timeout - Errorcode: > > > > 0x55 > > > > > > > > > > > > I'm not sure if it has happened since upgrading from 4.10.5 to > > > > 4.12.6 > > > > or if it is due to the increased amount of users. > > > > > > > > I have to do a fullsync because more containers have been added > > > > for > > > > sync. > > > > > > > > Any ideas? > > > > > > > > > > > > my system: > > > > 4 DCs with samba 4.12.6 running on ubuntu 20.04 > > > > > > > > > > > > Regards, > > > > Heinz > > > > > > > > p.s. > > > > it wasn't my idea to use office365 ;-)