I also found the log now.
And, as I supected before, the BES uses kerberos, which will not work in this case.
I logged the kerberos events on the BES.
translation in english:
Code:
A Kerberos error occured while authenticating
ClientTime:
ServerTime: 15:20:3.0000 5/1/2010 Z
ErrorCode: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
Erweiterter Fehler:
Clientbereich:
Clientname:
Servercontext: someremotedomain.LOCAL
Servername: krbtgt/localdomain.COM
Targetname: krbtgt/localdomain.com@remotedomain.LOCAL
Errortext:
File: 9
Line: ae0
Original message in German:
Code:
Eine Kerberos-Fehlermeldung wurde auf
Anmeldesitzung empfangen:
Clientzeit:
Serverzeit: 15:20:3.0000 5/1/2010 Z
Fehlercode: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
Erweiterter Fehler:
Clientbereich:
Clientname:
Serverbereich: someremotedomain.LOCAL
Servername: krbtgt/localdomain.COM
Zielname: krbtgt/localdomain.com@remotedomain.LOCAL
Fehlertext:
Datei: 9
Zeile: ae0
Die Fehlerdaten stehen in den Berichtdaten.
I am no expert in kerberos. From what I know, it looks, like the BES queries the DC of the local domain, to get a ticket from the remote domain, but, the local DC does not know how this can be done.
How can I change the Configuration of the BES to use NTLM/NTLMv2 for authentication instead of kerberos ?