Dirk Laurenz (Samba Mailinglisten Account)
2015-Aug-30 10:49 UTC
[Samba] Office 365, Windows 10 and Samba AD
Hello everybody, i found out, that there's a problem with Windows 10, Office 365 and Samba AD. A Win 10 Client, joined to a Samba AD Domain does not allow office 365 to connect to an IMAP Based Mail service. If the AD controller is a windows 2012 R2, this works. See: https://social.technet.microsoft.com/Forums/de-DE/9983a475-856a-4ff8-8aa2-1e 430ebd293a/outlook-2013-window-10-imap-domne?forum=office_generalde (is only german) Has anyone else this problem? Working with a local account on the same windows 10 system works (as described in the workaround). Regards, Dirk --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus
On Sun, 30 Aug 2015 12:49:09 +0200, Dirk Laurenz \(Samba Mailinglisten Account\) wrote:> i found out, that there's a problem with Windows 10, Office 365 and Samba > AD. A Win 10 Client, joined to a Samba AD Domain does not allow office 365 > to connect to an IMAP Based Mail service. > > If the AD controller is a windows 2012 R2, this works. See: > https://social.technet.microsoft.com/Forums/de-DE/9983a475-856a-4ff8-8aa2-1e > 430ebd293a/outlook-2013-window-10-imap-domne?forum=office_generalde (is only > german)Thanks for the report Dirk. Please raise a bug at bugzilla.samba.org track this issue. Cheers, David
Dirk Laurenz (Samba Mailinglisten Account
2015-Oct-02 07:07 UTC
[Samba] Office 365, Windows 10 and Samba AD
Hi, i managed to create a level 10 debug log - bug id 11538 -----Ursprüngliche Nachricht----- Von: Dirk Laurenz [mailto:dirk at laurenz.ws] Gesendet: Freitag, 25. September 2015 11:58 An: 'Dirk Laurenz (Samba Mailinglisten Account)' <samba at laurenz.ws>; 'David Disseldorp' <ddiss at suse.de> Cc: samba at lists.samba.org Betreff: AW: [Samba] Office 365, Windows 10 and Samba AD Unfortunately level 10 debug log is empty - it seems to be a local problem only on windows 10 -----Ursprüngliche Nachricht----- Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von Dirk Laurenz (Samba Mailinglisten Account) Gesendet: Freitag, 25. September 2015 06:43 An: 'David Disseldorp' <ddiss at suse.de>; 'Dirk Laurenz (Samba Mailinglisten Account)' <samba at laurenz.ws> Cc: samba at lists.samba.org Betreff: Re: [Samba] Office 365, Windows 10 and Samba AD Hi, the same with Office 2016 from Officec 365. I will raise a bug report this weekend. Level 10 Debug Log? -----Ursprüngliche Nachricht----- Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von David Disseldorp Gesendet: Dienstag, 1. September 2015 12:02 An: Dirk Laurenz (Samba Mailinglisten Account) <samba at laurenz.ws> Cc: samba at lists.samba.org Betreff: Re: [Samba] Office 365, Windows 10 and Samba AD On Sun, 30 Aug 2015 12:49:09 +0200, Dirk Laurenz \(Samba Mailinglisten Account\) wrote:> i found out, that there's a problem with Windows 10, Office 365 and > Samba AD. A Win 10 Client, joined to a Samba AD Domain does not allow > office 365 to connect to an IMAP Based Mail service. > > If the AD controller is a windows 2012 R2, this works. See: > https://social.technet.microsoft.com/Forums/de-DE/9983a475-856a-4ff8-8 > aa2-1e > 430ebd293a/outlook-2013-window-10-imap-domne?forum=office_generalde > (is only > german)Thanks for the report Dirk. Please raise a bug at bugzilla.samba.org track this issue. Cheers, David -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus
Am 2015-10-02 um 09:07 schrieb Dirk Laurenz (Samba Mailinglisten Account:> Hi, > > i managed to create a level 10 debug log - bug id 11538I hit this bug yesterday in a NT-based domain with samba-3.6.25. Is there any patch or workaround for samba-3.x as well? The patch in the mentioned bug does some LDAP-change ... I don't have any LDAP there. Sure, migration to samba-4 and/or ADS-based domain has to be sooner or later, I assume ;-)