Displaying 3 results from an estimated 3 matches for "fullsync".
2020 Sep 29
2
azure ad connect timeout
...hronization 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 ;-)
2020 Oct 02
2
azure ad connect timeout
...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.
>
>
>...
2020 Oct 02
0
azure ad connect timeout
...t; 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 syn...