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

(Roll back to the 30 July 2013, 22:17 version. The later changes are not correct (e. g. it's not just related to s3) or have nothing to do with this topic (W8 and dots in domain name))
m (/* Added powershell join method)
 
(24 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= When do I need Registry changes? =
+
= General Information =
  
'''Samba usually doesn't require any changes on your Windows OS.
+
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)]].
  
So please read very carefully on the sections below why and when you should do them!
+
{{Imbox
 +
| type = important
 +
| text = If you are running Samba Active Directory (AD), do not set any of the modifications mentioned on this page.
 +
}}
  
If your situation or problem isn't mentioned here, then it's highly recommented to <u>NOT</u> do any registry changes!'''
 
  
  
  
  
= Joining Windows7/8 or Windows Server 2008r2/2012 to an Samba NT4-style domain =
+
= Joining Windows 7 and Later / Windows Server 2008 and Later to a Samba NT4 Domain =
  
'''This changes are only necessary if you want to join a Windows7/8 or Windows Server 2008r2/2012 machine to a <u>Samba NT4-style domain</u>!
+
During the join, the following error message is displayed:
  
It's not required and not recommended if you run Samba as AD DC!'''
+
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:
  
If you try to join any of the mentioned OS you'll encounter an error
+
* 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.):
  
  The following error occourred attempting to join the domain „.....“:
+
  Windows Registry Editor Version 5.00
 
   
 
   
  The specified domain either does not exist or could not be contacted.
+
  [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.
 +
 
 +
 
  
The following registry change work with any Samba version that isn't already [[Samba_Release_Planning|discontinued]]:
 
  
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]
 
 
DWORD DomainCompatibilityMode 1
 
DWORD DNSNameResolutionRequired 0
 
  
Do the changes manually in <tt>regedit.exe</tt> or save the above in a plain text file with Notepad/Editor (not Word/Wordpad/OpenOffice/LibreOffice/...!) and name it <tt>sambafix.reg</tt>. Make sure, that the file has the ending <tt>.reg</tt>. Then you can import it directly to your registry by double-clicking, if you have the sufficient permissions.
+
= Windows 7 / Windows Server 2008 R2: Changing the Primary Domain DNS Name of This computer to "" Failed. =
  
After the next reboot you can join the machine to your domain, but you'll still encounter an error:
+
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 ".....".
+
  Changing the Primary Domain DNS name of this computer to "" failed. The name will remain "...".
 
  The error was:
 
  The error was:
 
   
 
   
 
  The specified domain either does not exist or could not be contacted
 
  The specified domain either does not exist or could not be contacted
  
But this error can safely be ignored or, if you run Windows 7, silenced by a hotfix, that was published by Microsoft: [http://support.microsoft.com/kb/2171571 KB2171571: You incorrectly receive an error message when you join a computer that is running Windows 7 or Windows Server 2008 R2 to a Samba 3-based domain].
+
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.
 +
}}
  
  
  
  
= IMPORTANT: Registry changes that never should be done! =
 
  
There are many pages on the internet, which suggest to change the values of <tt>RequireSignOrSeal</tt> and <tt>RequireStrongKey</tt>. '''This is <u>NOT</u> recommended by the Samba team, as it will break interoperability with other Windows and Samba versions!'''
+
= Windows 10 and Windows Server 2016: There Are Currently No Logon Servers Available to Service the Logon Request =
  
If you have already changed these parameters, turn them back to <tt>1</tt> as shown below and reboot:
+
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]
 
  [HKEY_LOCAL_MACHINE\System\CCS\Services\Netlogon\Parameters]
   
+
  "RequireSignOrSeal"=dword:00000001
DWORD RequireSignOrSeal = 1
+
  "RequireStrongKey"=dword:00000001
  DWORD RequireStrongKey = 1
+
 
 +
* 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.