similar to: Post classicupgrade Windows registry changes?

Hello to all, After a lot of trying this is the solution for all with samba 3.2.15 installed. My Windows 7 client machine joins the domain on the fly with this registry hack. I can logon without errors and all my netlogon scripts are working: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Para meters] "DomainCompatibilityMode"=dword:00000001

I don't have anything but Server 2003, 2008 and 2012 to test with. 2003 joins the domain without issue. 2008 and 2012 will not. The registry has been updated on both: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] "DNSNameResolutionRequired"=dword:00000000

Greetings! I have a brand new Windows 10 Pro box, Version 1703, Build 15063.1155, and made the two registry mods (DNSNameResolutionRequired and DomainCompatibilityMode) to enable it to join an old-style NT4 Samba domain (Version 4.3). However, I note that the dialog for joining a domain within Windows 10 now specifically says to "Join an Active Directory Domain," and no attempt to join

If I setup a samba 4 PDC (not AD) like I do with samba 3, I still have to change the follow registry key on Win 7/8/?/10 for join it to samba domain ? > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] > "DomainCompatibilityMode"=dword:00000001 > "DNSNameResolutionRequired"=dword:00000000 > >

Is it still possible to join a Windows 2012 Server R2 system as a member to a 'pre-NT5' Samba (3.6.23) domain controller? The Windows 'Domain Change' GUI errors immediately after failing the SRV lookup for the AD server. Even with the SRV record in place, the GUI fails trying to connect to the non-existent LDAP port. Netdom on the command line tries to work if the DC name

Hello I try to add a windows 10 client to a existent samba 3 domain. I have installed a windows 10 build 10049 with all Updates. On the windows client I added/modified the following Registry Keys that I can join to to the Samba 3 Domain. HKLM->System->CCS->LanmanWorkstation->Parameters DNSNameResolutionRequired = 0 DomainCompatibilityMode = 1 On the Samba Server I created the

Hi Rowland, ##I have to ask this, why are using an OS that is EOL, along with an version of Samba that is also EOL ???? Ans: My client is using the environment since from last 4 years and it is integrated with lot of tools. ##How are you trying to join the 2012 server, as a domain member or as a DC ? Ans: I am trying to join the 2012 server as a domain member only. ##You could try disabling

A while back, Volker sent out the following: [Hide Quoted Text] That won't work. Your only chance is Samba 3.3.4 with HKLM\System\CCS\Services\LanmanWorkstation\Parameters DWORD DomainCompatibilityMode = 1 DWORD DNSNameResolutionRequired = 0 HKLM\System\CCS\Services\Netlogon\Parameters DWORD RequireSignOnSeal = 0 DWORD

Hi, I am using a samba server for file sharing in our companies IPv4 based LAN. The samba server is running as VM on a ubuntu 14.04 qemu/kvm host using ubuntu 14.04 as OS. I am using the lastet version available for samba: 4.1.6+dfsg-1ubuntu2.14.04.3 My Windows 7 and Windows 8.1 client are able to find the server and connect to the shares but the Windows 8.1 client of a colleague is not able to

Hello, I have try windows 10 in an Samba 4.4.5 NT4-style domain. With some registry hacks (DomainCompatibilityMode and DNSNameResolutionRequired) it can be an member of the domain. When i try to login with domain member i get the error "There are currently no logon servers available to service the logon request" At

Hi Rowland, I have attached smb.conf file with this mail. Please refer the file and give me possible solution to resolve the issue. Regards, Ramkumar R +91 8892107131 -----Original Message----- From: Rowland Penny [mailto:rpenny at samba.org] Sent: 04 October 2017 13:11 To: samba at lists.samba.org Subject: Re: [Samba] Need to join Windows server 2012 R2 as a client to Samba Domain in

I'm trying to set up Samba as a PDC for some Win7 clients, and could use some help. I can successfully join the domain, with the message "Changing the primary domain DNS name of this computer to "" failed.", but I am still told that it was successful. However, when I try to log in, I am told "The trust relationship between this workstation and the primary domain

Dear Samba support team, I have a question on Samba 3.5.8 please, which is not solved by searching the forums. I tried all suggested solutions, but nothing take effect. Situation: - small public school - We have Ubuntu Server 11.04 64-bit - Samba 3.5.8 as PDC - Windows XP and Windows 7 Pro SP1 clients - On Windows XP everything works. Login is quick and reliable there. Problem: But

I've been running Samba 4 in NT4 Domain mode for a few years, and it's been working fine with Windows 7 PCs. I now need to join a new Windows 10 PC to the domain, but I'm not having any success! When I try to join the domain, the Windows 10 PC says "An Active Directory Domain Controller could not be contacted...." I've tried a few things, including:- Setting

Hello it is possible to join a Windows 10 pro on samba Version 4.3.11-Ubuntu. Our version Is not a samba AD. Regards. I try with this [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DomainCompatibilityMode"=dword:00000001 "DNSNameResolutionRequired"=dword:00000000 And not work propertly.

Hi All, I know this has been done to death on this forum, but I still can't get my Win 7 PCs to join a samba domain. I have edit the reg keys in HKLM \System\CCS\LanmanWorkStation\Parameters, DomainCompatibilityMode = 1 and DNSNameResolutionRequired = 0, but still no joy. I am running Samba 3.5.10 on CentOS 5.8 and below in my smb.conf file. ===========Begin================ [global]

Hi, I've got a problem with Windows 10 Education (last build) and my Samba PDC (under Fedora). All machines with Windows 7 can join domain successfully. But with Windows 10, I've got "network path not found" error. I've changed all registry keys that we need to change, but no way (DomainCompatibilityMode, DNSNameResolutionRequired, AllowInsecureGuestAuth) My PDC is in NT4

I have been going through all the Wikis and various Google searches to try to solve my problem, all to no avail. I can mount a Samba share, but whenever I try to login using a domain account, I receive an error about "The trust relationship between this workstation and the primary domain failed." What I have done so far, all to no avail. - Upgraded from Samba 3.4.2 to Samba 3.4.4

After being content with an old laptop running XP for years, my job decided to provide me with a shiny new one running Windows 7 Professional. The biggest problem with this is that I can't get the Windows 7 box to login to my Samba NT4-style domain controller. I have upgraded samba from 3.0.33 to 3.6.23, and copied my smbpasswd file to where the new samba expects to find it in

I'm running my samba 3.5.9 server on CentOS 5.x. Windows 7 clients can add themselves to the domain, and local users on the client can map network drives (even ones they don't have access to and modify the contents!!!) and net view and net use commands work, but give the user too much access. XP clients can add themselves to the domain, authenticate users correctly and apply correct