http://bugs.winehq.org/show_bug.cgi?id=59051 --- Comment #1 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, here's a simple .NET test case that mimics what the SQL Server installer is doing when it tries to bind to the local machine via ADSI ("WinNT://..."). --- snip --- using System; using System.DirectoryServices; class Program { static void Main() { try { // Attempt to bind to the local computer via ADSI WinNT provider string path = "WinNT://" + Environment.MachineName + ",computer"; Console.WriteLine("Binding to: " + path); using (DirectoryEntry entry = new DirectoryEntry(path)) { Console.WriteLine("NativeObject: " + entry.NativeObject); } Console.WriteLine("Bind succeeded."); } catch (Exception ex) { Console.WriteLine("Bind failed: " + ex.Message); Console.WriteLine("Exception type: " + ex.GetType()); Console.WriteLine("HResult: 0x" + ex.HResult.ToString("X")); } } } --- snip --- Compile (assuming .NET Framework 4.5 install as per prerequisite): --- snip --- $ wine "C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\csc.exe" test.cs --- snip --- Run: --- snip --- $ wine ./test.exe Binding to: WinNT://DARKSTAR,computer 0024:fixme:activeds:ADsGetLastError (000000000010EF10,000000000010EB80,256,000000000010EB50,0)!stub Bind failed: Call failed. Exception type: System.Runtime.InteropServices.COMException HResult: 0x80004005 --- snip --- Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.