Scenario: An Exchange 5.5 Server SP3 (SP4 doesn't work see Bug 1076) on Windows 2000 Server on a network using Samba 3.0.2 as a PDC. The Microsoft Exchange Administrator client works fine if it is used directly on the server running Exchange. If the client is installed on another computer and one tries to connect to the Exchange server the following error is generated: <error message> A connection could not be made to the Microsoft Exchange Server computer '<servername>'. The Microsoft Exchange Server Computer does not respond. Microsoft Exchange Directory ID no: DS_E_COMMUNICATIONS_PROBLEM </error message> Other detail concerning the PDC can be found in Bug #1076 https://bugzilla.samba.org/show_bug.cgi?id=1076
reproduced here during install of another exchange server.
Again under preliminary testing the patch provided for bug 1076 seems to have fixed this particular issue.
ok. could you please describe your setup? is exchange installed on nt4 and the client running on win2k?
Our current testing uses Windows 2000 Server for Exchange and the Remote Exchange Administrator has been tested on XP and 2k server. We have not tested on nt.
Thank you, this reflects what I've seen elsewhere. When Exchange-Server is running on NT4 and the Exchange-Administrator is running on another NT4-box, Windows expects a Session-Key in the netrsamlogon-reply from the samba-dc. If Samba does not pass this key, the connect will fail, likewise any Exchange-replication, etc. I'm still testing a patch to allow this. If Server and Administrator are running on >win2k windows is happy without session-keys.
Created attachment 849 [details] put session-key in reply This patch puts an lm_session_key in the netrsamlogon-reply from a samba-dc for Exchange 5.5 running on NT4.
This problem is fixed now. If you see any further problems, please reopen the bug.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.