If adding a windows machine to a Samba domain fails and the below “solves” your issue, then you need to tighten the security on the Samba side:
[ WayBack ] Old Nabble Samba General Windows 7 RC [ WayBack ] Windows 7 can see Samba Shares but cannot see Samba Domain [ WayBack ] Adding a Windows 8.1 computer to a SAMBA domain twm’s blog [ WayBack ] Note to self: If adding a Windows 8.1 computer to a SAMBA domain fails with the error “The specified domain either does not exist or could not be contac… Thomas Mueller (dummzeuch) Google+ Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] ; Enable NT-Domain compatibility mode ; Default: ; [value not present] ; "DomainCompatibilityMode"=- "DomainCompatibilityMode"=dword:00000001 ; Disable required DNS name resolution ; Default: ; [value not present] ; "DNSNameResolutionRequired"=- "DNSNameResolutionRequired"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters] ; Disable requirement of signed communication ; My Samba (3.0.33) works with signed communication enabled, so no need to disable it. ; Default: ; "RequireSignOrSeal"=dword:00000001 ; Disable the usage of strong keys ; Default: ; "RequireStrongKey"=dword:00000001 "<strong>RequireStrongKey</strong>"=dword:00000000jeroen
