similar to: Windows 10 in Samba 3 domain: netlogon share access denied

Hi all, Is anyone using Windows SMB signing in a production environment ? This is the signing proceedure created by setting the Registry keys EnableSecuritySignature:1, RequireSecuritySignature: 1 in the lanmanserver and lanmanworkstation parameters. I'm playing with implementing this in Samba for 3.0, but am finding that it doesn't seem to work when mixing Windows NT or Windows 2000

Hi We have 2 servers running samba 1 is linux 7 /samba 4.2.3 1 is linux 6 /samba 3.6.23-25.0.1 Both are joined to a Windows Domain Both use ADS for security (we use CAC on the client) Recently users of the samba 3.6 shares have been having trouble connecting The issue seems to be theclient registry setting :

Hi Rowland sorry for not being clear. In my first post I already wrote: Now I have to tight security with setting those flags in the windows client: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] EnablePlainTextPassword=0 EnableSecuritySignature=1 RequireSecuritySignature=1 . . . when I change registry to RequireSecuritySignature=0, everything works like

Hi, I was reading your article. One question, do you have Norton antivirus installed in your system? if so, there's a problem with both of them. We are experiencing the same problem. Just have to wait for the next service pack from Might Microsoft. Have a nice day. Louis Ong Summa Engineering Ltd. LO@Summaeng.com (905) 678-3388 Ext. 241

Goldmine seems to a compiled database application compiled in something likeClipper. Clipper applications record lock through ISAM like files (DBF). However, in Windows NT/2000/XP, Opportunistic locking is turned on by default in order to accelerate file transfer from file services. [Windows 95/98 did not Opportunisticly lock] However, opportunistic locking corrupts ISAM and ISAM like

Hi, I have an Informix program that unload data to a file in a samba directory. Problem is although the file has changed, I still see the old data from my Windows 98 SE PC. I only see the updated data after refreshing the snmba directory numerous times. Sometimes I have to wait for more that 10 minutes !! Funny thing is this problem does not apply to my friend's PC. Why is this so and

strange i did not change anything in my windows 7 64bit. This is my full setup pretty basic. Ubuntu 14.04.2 LTS, Trusty Tahr, with sernet samba 4.1.17-9 I do have 1 user for samba. pdbedit -L xbmc:5000:MediaUser [global] workgroup = PRIVE server string = %h server dns proxy = yes ; name resolve order = lmhosts host wins bcast #### Networking #### # interfaces = 127.0.0.0/8 eth0

Hello I have an samba server with a public share. It was configured with security=share. Now I have to tight security with setting those flags in the windows client: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] EnablePlainTextPassword=0 EnableSecuritySignature=1 RequireSecuritySignature=1 Since this change the public share is not working anymore. I found

Hi Rowland The client is stopping communication, not the server. With error 1240. And since it is working with the client setting RequireSecuritySignature=0 without any problem, ' hosts allow' cannot be either the problem nor the solution. So - setting RequireSecuritySignature=1 at the client needs a corresponding setting at the server - I guess. But even explicit settings on samba side

Have a need to support one NT4 server in one environment and trying to escape the past a bit by upgrading the PDC which currently runs Samba-3.6.24. So far my testing has shown that Samba4-4.5 as a PDC appears to work just fine. I can even install Exchange 5.5 on the test NT4 server in this environment. However attempting the same Exchange 5.5 installation when running Samba4 in AD mode it

Howdy, Does anyone know how to check the samba setting of "smb signing"? There is a data write error that can happen with the signing, and I'd like to check my samba servers. See http://www.eweek.com/article2/0,4149,1415221,00.asp and http://www.tangent-systems.com/support/delayedwrite.html Alan Pence System Administrator "The smart ones ask when they don't know. And,

Hey all, has anyone done dcdiag against his DC yet? It's made from a windows client on command line: dcdiag /s:<servername> What are your results? With me some of the tests were not successful, e.g. ForestDNSDomain. My dcdiag is German so its output would not be so helpful for the mailing list. So somebody else can do a check to compare? Thanks in advance Tim

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

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

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 -----------------------------------------------

LLVM Weekly - #52, Dec 29th 2014 =============================== If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/52>. Welcome to the fifty-second issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by [Alex Bradbury](http://asbradbury.org).

Can anyone help with this? I set it all up a few months ago, the samba side being standard upgrades via debian - configured as a PDC, and the windows 7 clients being clean installs, with the standard lanmanworkstation regedits done. They've been working fine since then, but have now started failing, instead raising the error message 'The trust relationship between this work station and

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

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

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