The latest schema patch (consider the URL) seems to break the interaction with the Microsoft MMC consoles. Every time I open one of them I get a messagebox telling me "Naming information cannot be located because: Unknown error". I've done some investigations (wireshark, patch analysis) but I don't have a clue yet.
Created attachment 3505 [details] Cosmetic patch for return value A small cosemtic correction, so the result seems more obvious. Please apply!
Was it fixed ? I just upgraded my server and It seems to work at first glance... I didn't do a fresh provision, just copied files from previous build. (In reply to comment #0) > The latest schema patch (consider the URL) seems to break the interaction with > the Microsoft MMC consoles. Every time I open one of them I get a messagebox > telling me "Naming information cannot be located because: Unknown error". I've > done some investigations (wireshark, patch analysis) but I don't have a clue > yet. >
(In reply to comment #2) I provided now also the platform informations. My client is a Win2k SP4 virtual machine. Maybe with another OS (yours) it works! > Was it fixed ? I just upgraded my server and It seems to work at first > glance... > I didn't do a fresh provision, just copied files from previous build.
You are correct, it seems to work fine under XP SP3, but I tested W2K SP4 with the same issue.
Created attachment 3532 [details] Cosmetic patch for KERBEROS parts This patch fixes up the SAMBA 4 KERBEROS routines for right return values and corrects also a wrong function name (typo).
Created attachment 3533 [details] Cosmetic patch for LDB parts/library This patch is much longer and tries to use the LDB return constants as much as possible versus using hardcoded numbers. The constants are more readable and I tried to introduce them were it makes sense to use (e.g. in comparison routines it does'nt). Since I changed the value "-1" to 1/"LDB_ERR_OPERATIONS_ERROR" in a few cases, I had also to adapt some if's on return values.
This is fixed in 937b466266256d26d02cf8d48e72a26272fe8627. Please check.
Not fixed yet.
This could be a indication of our problem: When opening ADDT (Active Directory Domains and Trusts) MMC I get a more detailed error message: "The configuration information describing this enterprise is not available."
I found the problem in Microsoft's KB. But how we fix it for SAMBA 4?
Created attachment 3590 [details] NTLMSSP patch Here a patch related to the problem that fixes the NTLMSSP result host and domain DNS names.
Created attachment 3592 [details] New version of the previous patch Use "lp_*" calls
Created attachment 3593 [details] GIT formatted version of the NTLMSSP patch Improved version and GIT formatted.
Created attachment 3594 [details] GIT formatted version of the NTLMSSP patch Now it should be ready and complete.
Assign it up to Stefan Metzmacher and let Andrew Bartlett be the QA Contact.
NTLMSSP pathes are pushed with 8ac5db124630586605bd3972975ea47ee1cb34c0
Can you please upload a capture thate shows the remaining problem
Comment on attachment 3594 [details] GIT formatted version of the NTLMSSP patch Can do. I mark the NTLMSSP patch as obsolete, because it has been applied.
Created attachment 3602 [details] Capture Windows 2000 Admin Pack ADUC console <-> SAMBA 4
Part of the problem has been fixed through a patch of Tridge ("Remove dependencies of my home domain"). At least the "Browse" button in the "Connect to Domain" dialog works again. But the connection failures with their weird error massages persist.
If you try again with GIT after c412a930ad19da866503e6d8ccb71fb3191fc6d2, I think Microsoft's folks found the fundamental issue here (hitting other tools too) at the interop event.
Andrew, you got it! Thanks for chasing this down!