Difference between revisions of "Required Settings for Samba NT4 Domains"

(initial windows 7 support page)
 
m (/* Added powershell join method)
 
(44 intermediate revisions by 12 users not shown)
Line 1: Line 1:
== Samba versions supporting Windows7 Domain Logon ==
+
= General Information =
  
Support for Windows 7 using Samba Domain Controllers has been added to the following versions:
+
Microsoft discontinued the official support for NT4 domains in the Windows operating systems. However, with some modifications, you are still able to use later released Windows operating systems with a Samba NT4 domain. Anyway, consider migrating to a Samba Active Directory (AD) to avoid problems if a future update from Microsoft disables or removes no longer supported NT4 features. For details about migrating, see [[Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)|Migrating a Samba NT4 Domain to Samba AD (Classic Upgrade)]].
  
* Samba 3.4
+
{{Imbox
* Samba 3.3
+
| type = important
 +
| text = If you are running Samba Active Directory (AD), do not set any of the modifications mentioned on this page.
 +
}}
  
We successfully tested Windows 7 Ultimate (Build 2600) with Samba 3.4.0 and Samba 3.3.7.
 
  
  
== Windows 7 Registry settings ==
 
  
There are currently two registry settings required to be added on the Windows 7 client prior to joining a Samba Domain. These are:
 
  
        HKLM\System\CCS\Services\LanmanWorkstation\Parameters
+
= Joining Windows 7 and Later / Windows Server 2008 and Later to a Samba NT4 Domain =
            DWORD  DomainCompatibilityMode = 1
 
            DWORD  DNSNameResolutionRequired = 0
 
  
Make sure to either reboot Windows 7 or restart the LanmanWorkstation service after setting these entries.
+
During the join, the following error message is displayed:
  
You will receive one warning about DNS domain name configuration after the join has succeeded. This warning can be ignored at the moment.
+
The following error occurred attempting to join the domain "SA":
 +
The specified domain either does not exist or could not be contacted.
  
Do '''not''' edit any other registry parameters (NETLOGON) that have been seen in the wild. If you have already modified your Windows 7 registry, please make sure to reset the keys to their default values.
+
To enable the client to join the Samba NT4 domain:
  
--[[User:Gd|Gd]] 11:48, 1 September 2009 (CDT)
+
* Save the following content to a plain text file named <code>samba_7_2008_fix.reg</code> using a text editor such as "Notepad" or "Editor" (not Word/Wordpad/OpenOffice/LibreOffice/etc.):
 +
 
 +
Windows Registry Editor Version 5.00
 +
 +
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]
 +
"DomainCompatibilityMode"=dword:00000001
 +
"DNSNameResolutionRequired"=dword:00000000
 +
 
 +
* Log in using the local <code>Administrator</code> account.
 +
 
 +
* Double-click the file to import it to the Windows registry.
 +
 
 +
* Reboot to take the changes effect.
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Windows 7 / Windows Server 2008 R2: Changing the Primary Domain DNS Name of This computer to "" Failed. =
 +
 
 +
During joining the machine to the NT4 domain the following error message is displayed:
 +
 
 +
Changing the Primary Domain DNS name of this computer to "" failed. The name will remain "...".
 +
The error was:
 +
 +
The specified domain either does not exist or could not be contacted
 +
 
 +
You can ignore this error message or install a Microsoft hotfix on the Windows machine. For details, see [http://support.microsoft.com/kb/2171571 KB2171571].
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Windows 8.1 / Windows Server 2012 R2: Error code 0x80090345 launching Windows Credential Manager =
 +
 
 +
After installing the [https://support.microsoft.com/en-us/kb/3000850 November 2014 update rollup (KB3000850)] the following error is displayed:
 +
 
 +
Error code 0x80090345 launching Windows Credential Manager
 +
 
 +
To fix this problem:
 +
 
 +
* Save the following content to a plain text file named <code>samba_8_2012_fix.reg</code> using a text editor such as "Notepad" or "Editor" (not Word/Wordpad/OpenOffice/LibreOffice/etc.):
 +
 
 +
Windows Registry Editor Version 5.00
 +
 +
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb]
 +
"ProtectionPolicy"=dword:00000001
 +
 
 +
* Log in using the local <code>Administrator</code> account.
 +
 
 +
* Double-click the file to import it to the Windows registry.
 +
 
 +
* Reboot to take the changes effect.
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Windows 10 =
 +
 
 +
{{Imbox
 +
| type = important
 +
| text = Microsoft seems to be trying to get everybody to run Active Directory (AD), You may not be able to join a Windows 10 PC to an NT4-style domain. It has been reported that rolling back to an earlier version of Windows 10 does allow the join to occur. You should plan to upgrade to AD as soon as possible.
 +
}}
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Windows 10 and Windows Server 2016: There Are Currently No Logon Servers Available to Service the Logon Request =
 +
 
 +
After you successfully joined Windows 10 or Windows Server 2016 to your Samba NT4 domain, logging in failed and the following error is displayed:
 +
 
 +
There are currently no logon servers available to service the logon request.
 +
 
 +
To work around this problem, configure the Samba Primary Domain Controller (PDC) to support only the SMB 1 protocol. However, Microsoft deprecated the SMB 1 protocol in Windows and will remove the protocol in a future version. Windows 10 and Windows Server 2016 Fall Creators Update 1709 and later do no longer install SMB 1 by default. For details, see [https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-windows-10-and-windows-server-version-1709 SMBv1 is not installed by default in Windows 10 Fall Creators Update and Windows Server, version 1709]. Before you re-enable SMB 1 on Windows, the workaround described in this section will fail. For details about re-enabling SMB 1 on Windows, see your Windows documentation.
 +
 
 +
To configure the PDC to only support the SMB 1 protocol:
 +
 
 +
* Set the following parameter in the <code>[global]</code> section in the <code>smb.conf</code> file:
 +
 
 +
server max protocol = NT1
 +
 
 +
:{{Imbox
 +
| type = note
 +
| text = This setting prevent all your clients to use a newer SMB protocol version than SMB 1 when communicating with the PDC. Anyway, the Samba team recommends to use this workaround. Disabling newer SMB versions on the Windows 10 client instead prevent this machine communicating using newer SMB version with <u>all</u> Samba/Windows hosts.
 +
}}
 +
 
 +
* Restart Samba.
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Using Powershell =
 +
 
 +
It has been reported by Alexandru Joni, that is possible to join Windows 10 to an NT4-style domain using Powershell:
 +
 
 +
Add a local computer to a domain using credentials
 +
    Add-Computer -ComputerName Server01 -LocalCredential Server01\Admin01 -DomainName Domain02 -Credential Domain02\Admin02 -Restart –Force
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= IMPORTANT: Registry Changes That You Should Never Set! =
 +
 
 +
{{Imbox
 +
| type = warning
 +
| text = You must not to change the values of the <code>RequireSignOrSeal</code> or <code>RequireStrongKey</code>. Changing the settings breaks the interoperability with Windows and Samba installations.
 +
}}
 +
 
 +
If you changed these parameters, reset the values of both keys back to <code>1</code>:
 +
 
 +
* Save the following content to a plain text file named <code>reset_RequireSignOrSeal_RequireStrongKey.reg</code> using a text editor such as "Notepad" or "Editor" (not Word/Wordpad/OpenOffice/LibreOffice/etc.):
 +
 
 +
Windows Registry Editor Version 5.00
 +
 +
[HKEY_LOCAL_MACHINE\System\CCS\Services\Netlogon\Parameters]
 +
"RequireSignOrSeal"=dword:00000001
 +
"RequireStrongKey"=dword:00000001
 +
 
 +
* Log in using the local "<code>Administrator</code> account.
 +
 
 +
* Double-click the file to import it to the Windows registry.
 +
 
 +
* Reboot to take the changes effect.
 +
 
 +
 
 +
 
 +
 
 +
 
 +
----
 +
[[Category:NT4 Domains]]

Latest revision as of 10:26, 24 January 2020

General Information

Microsoft discontinued the official support for NT4 domains in the Windows operating systems. However, with some modifications, you are still able to use later released Windows operating systems with a Samba NT4 domain. Anyway, consider migrating to a Samba Active Directory (AD) to avoid problems if a future update from Microsoft disables or removes no longer supported NT4 features. For details about migrating, see Migrating a Samba NT4 Domain to Samba AD (Classic Upgrade).



Joining Windows 7 and Later / Windows Server 2008 and Later to a Samba NT4 Domain

During the join, the following error message is displayed:

The following error occurred attempting to join the domain "SA":
The specified domain either does not exist or could not be contacted.

To enable the client to join the Samba NT4 domain:

  • Save the following content to a plain text file named samba_7_2008_fix.reg using a text editor such as "Notepad" or "Editor" (not Word/Wordpad/OpenOffice/LibreOffice/etc.):
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]
"DomainCompatibilityMode"=dword:00000001
"DNSNameResolutionRequired"=dword:00000000
  • Log in using the local Administrator account.
  • Double-click the file to import it to the Windows registry.
  • Reboot to take the changes effect.



Windows 7 / Windows Server 2008 R2: Changing the Primary Domain DNS Name of This computer to "" Failed.

During joining the machine to the NT4 domain the following error message is displayed:

Changing the Primary Domain DNS name of this computer to "" failed. The name will remain "...".
The error was:

The specified domain either does not exist or could not be contacted

You can ignore this error message or install a Microsoft hotfix on the Windows machine. For details, see KB2171571.




Windows 8.1 / Windows Server 2012 R2: Error code 0x80090345 launching Windows Credential Manager

After installing the November 2014 update rollup (KB3000850) the following error is displayed:

Error code 0x80090345 launching Windows Credential Manager

To fix this problem:

  • Save the following content to a plain text file named samba_8_2012_fix.reg using a text editor such as "Notepad" or "Editor" (not Word/Wordpad/OpenOffice/LibreOffice/etc.):
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb]
"ProtectionPolicy"=dword:00000001
  • Log in using the local Administrator account.
  • Double-click the file to import it to the Windows registry.
  • Reboot to take the changes effect.



Windows 10



Windows 10 and Windows Server 2016: There Are Currently No Logon Servers Available to Service the Logon Request

After you successfully joined Windows 10 or Windows Server 2016 to your Samba NT4 domain, logging in failed and the following error is displayed:

There are currently no logon servers available to service the logon request.

To work around this problem, configure the Samba Primary Domain Controller (PDC) to support only the SMB 1 protocol. However, Microsoft deprecated the SMB 1 protocol in Windows and will remove the protocol in a future version. Windows 10 and Windows Server 2016 Fall Creators Update 1709 and later do no longer install SMB 1 by default. For details, see SMBv1 is not installed by default in Windows 10 Fall Creators Update and Windows Server, version 1709. Before you re-enable SMB 1 on Windows, the workaround described in this section will fail. For details about re-enabling SMB 1 on Windows, see your Windows documentation.

To configure the PDC to only support the SMB 1 protocol:

  • Set the following parameter in the [global] section in the smb.conf file:
server max protocol = NT1
  • Restart Samba.



Using Powershell

It has been reported by Alexandru Joni, that is possible to join Windows 10 to an NT4-style domain using Powershell:

Add a local computer to a domain using credentials

   Add-Computer -ComputerName Server01 -LocalCredential Server01\Admin01 -DomainName Domain02 -Credential Domain02\Admin02 -Restart –Force



IMPORTANT: Registry Changes That You Should Never Set!

If you changed these parameters, reset the values of both keys back to 1:

  • Save the following content to a plain text file named reset_RequireSignOrSeal_RequireStrongKey.reg using a text editor such as "Notepad" or "Editor" (not Word/Wordpad/OpenOffice/LibreOffice/etc.):
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\System\CCS\Services\Netlogon\Parameters]
"RequireSignOrSeal"=dword:00000001
"RequireStrongKey"=dword:00000001
  • Log in using the local "Administrator account.
  • Double-click the file to import it to the Windows registry.
  • Reboot to take the changes effect.