[cifs-protocol] [REG:115052112759051] Samba 4.1 classic (nt4-like) support as a DC to Windows 10

Edgar Olougouna edgaro at microsoft.com
Thu May 28 15:23:56 MDT 2015

In the distant past we tested NT4 domain join support on a best-effort basis, however NT4 is clearly out of support lifecycle for over 10 years.
As it has been for several years, there is no current plan in testing NT4 style domains moving forward. 
As a result, we can assume that any compatibility between Windows 10 and NT4-style old domains is purely accidental legacy rather than tested scenario.

Error message when you try to join a Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2-based computer to a Windows NT 4.0 domain: "Logon failure: unknown user name or bad password"
Examples of known workarounds on Windows 7:
DomainCompatibilityMode = 1 
DNSNameResolutionRequired = 0 
RequireStrongKey = 0 
RequireSignOrSeal = 0
AllowNT4Crypto = 1


-----Original Message-----
From: Edgar Olougouna 
Sent: Monday, May 25, 2015 12:22 AM
To: Andrew Bartlett
Cc: Stefan (metze) Metzmacher; cifs-protocol at lists.samba.org; MSSolve Case Email; Vincent CARDON; denis
Subject: RE: [cifs-protocol] [REG:115052112759051] Samba 4.1 classic (nt4-like) support as a DC to Windows 10

Thanks for this important clarification. I now gather that I might not be able to provide much assistance on this inquiry. This is not Windows NT architecture. There is no matching Windows SKU. There is no functional level as documented in MS-ADTS msDS-Behavior-Version: Forest Functional Level, https://msdn.microsoft.com/en-us/library/cc223743.aspx.

From a broader perspective, I would assume Windows 10 join/logon to Windows NT4 server as an unsupported/untested scenario. It would not be realistic to expect seamless compatibility between the pair. Windows NT4 server support lifecycle ended over 10 years ago. 

Even if I pursued your issue, I would not get any internal support or traction from subject matter experts. Plus this would be against normal support policy.


-----Original Message-----
From: Andrew Bartlett [mailto:abartlet at samba.org] 
Sent: Saturday, May 23, 2015 1:28 AM
To: Edgar Olougouna
Cc: Stefan (metze) Metzmacher; cifs-protocol at lists.samba.org; MSSolve Case Email; Vincent CARDON; denis
Subject: Re: [cifs-protocol] [REG:115052112759051] Samba 4.1 classic (nt4-like) support as a DC to Windows 10

On Fri, 2015-05-22 at 21:27 +0000, Edgar Olougouna wrote:
> QUESTION: What is the meaning of nt4-like in "Samba 4.1 classic (nt4-like) support as a DC"? is there any "equivalent"  Windows SKU?

No, there is no matching Windows SKU.  For context, see the comments by Ned Pyle in this thread:


Another user there references "Microsoft Connect bug submission has ID 397104", but the real work came via close coordination between your team and us, the Samba Team :-)

> Typically we would collect TTT of LSA and debug. Since Win 10 is a development build, I'd like to see whether we can repro this in house and take a look.
> Could you describe how to configure the environment and the repro steps? 
> Details:
> How to setup the Samba 4.1 classic (nt4-like) DC.
> Where to get the Linux flavor and how install the Samba DC.
> NOTE: I will be using Hyper-V. 

Thanks.  If someone else (eg Vincent or Denis) doesn't get these to you shortly, I'll personally reproduce this and get you the exact instructions I used next week.

Andrew Bartlett

Andrew Bartlett                       http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba

More information about the cifs-protocol mailing list