similar to: Samba 4.0.21 and Windows 10

Displaying 20 results from an estimated 600 matches similar to: "Samba 4.0.21 and Windows 10"

2015 Dec 15
0
Samba 4.0.21 and Windows 10
You have seen : https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains and you rebooted after the registry changes? And you have (optionaly) set max protocol = NT1 in smb.conf Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Nico > Verzonden: dinsdag 15 december 2015 13:50 > Aan: samba at
2015 Oct 02
5
Samba 4 PDC and Windows 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 > >
2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hello Rowland, > cache directory = /local/samba-config/common/cache > lock directory = /local/samba-config/common/lock > log file = /local/samba-config/common/log/%m > pid directory = /local/samba-config/common/pid > private dir = /local/samba-config/common/private > state directory = /local/samba-config/common/state > You will
2016 Aug 18
4
Windows 10 Domainlogon Samba 4.4.5 NT4-style domain
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
2010 Oct 25
2
[nut-commits] svn commit r2610 - branches/silent_build
Citeren Arnaud Quette <aquette op alioth.debian.org>: > Log: > Optionaly enable silent build rules, using AM_SILENT_RULES, only if > it's supported (requires automake 1.11) Why do we need a new branch for this? As far as I can see, only the below lines are really needed > +dnl Currently, we only (force) enable silent rules if available > +dnl Verbose mode can be
2016 Mar 31
5
Windows 10
Hello We have a problem with our Windows 10 Clients. Installed on a SLES12 Server is samba v4.4 I can bind the clients to the domain without any problem. Afterwards I want to login in the domain, I get the error, no logonserver available I can change in the smb conf max protocol to NT1 -> now it is possible to login with user xxx in the domain We don't want to use our samba server
2009 Nov 12
3
Samba 3.2.15 is working with Winows 7 !!!
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
2016 May 13
7
Not able to join windows 10 clients to samba 3.6.23 NT4 Style PDC
I prepared samba PDC and not able to join windows 10 clients. Please suggest any windows 10 registry settings.
2018 Jul 31
3
Post classicupgrade Windows registry changes?
All, I am getting ready to tackle a classicupgrade. Test runs have gone well. I am just wondering about the Windows client machines after the upgrade. Do I need to remove the previously applied registry changes: DomainCompatibilityMode DNSNameResolutionRequired Do I need to dis-join, and re-join the clients? Current setup is: Single Server: Samba NT4/PDC LDAPsam New setup is: Single Server:
2018 Jun 18
2
Does DomainCompatibilityMode still work for NT4 domain joins in Windows 10?
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
2015 Apr 15
3
Join 2012 Server R2 as member to NT domain
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
2016 Apr 14
2
samba 3 domain and win10 logon scripts
On 13/04/16 21:32, Marc Muehlfeld wrote: > Hello, > > Am 13.04.2016 um 13:20 schrieb lejeczek: >> I have a win10 which is (from what I see) a good member of samba domain >> except for one thing - it does not seem to a few simply things from a >> logon.bat, or does not do anything with it. >> would you share your thoughts? > We can't, if you don't share
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
Hi, thanks a lot for the tips. I already did the first one, importing the following into the registry: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DomainCompatibilityMode"=dword:00000001 "DNSNameResolutionRequired"=dword:00000000 I didn't do the second tip but it looks like it's not
2015 Apr 08
3
Windows 10 + Domain Join + Samba 3.x + Profile V5
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
2015 Apr 15
3
Join 2012 Server R2 as member to NT domain
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
2011 May 30
3
Join W2008 R2 64bit to samba 3.5.8
Just a short question: How can a W2008 R2 64 bit Server be joined to samba 3.5.8 Domain? ----------------------------------------------- EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de Internet: www.tropenklinik.de -----------------------------------------------
2017 Oct 04
2
Need to join Windows server 2012 R2 as a client to Samba Domain in ubuntu 12.04
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
2010 Jun 17
2
feature request: lzma compresion (7zip)
Hello, many linux SW is starting to implement new lzma compresson instrad of old zlib (gzip) od bzip2. lzma is default comrpession in very good compression SW 7-zip, which is faster and have higher compression ratio then bzip2 or rar. Currently its probalby the best compressor in therms of compression and decompression speed / compression ratio. In linux there is GNU lzma SW which implements
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
I was trying to fix a problem on Windows 10 with Outlook 2013. Also running an NT4-style domain. The machine had already been joined to the domain and outlook had been working but recently not (probably after patch tuesday.) I also had had problems with Win 10 mail and RDP. I came across the following link.
2009 Oct 26
2
Windows 7
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