search for: enablesecuritysignatur

...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 : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters\EnableSecuritySignature Users cant connect to the 3.6 shares with it enabled They can connect to the 4.2.3 shares We have tried server side smb.conf settings but no luck They can only connect when the client registry key is disabled (and this violates a STIG) Anyone seen this? Thoughts? Thx tim Tim Reardon - GCED/...

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 clients with Windows XP servers. The clients get ACCESS_DENIED messa...

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 expected. If setting is still RequireSecuritySignature=0 - everything is working with the changed samba config. But - i'am forced to change from RequireSecuritySignature=0 to Req...

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 that smb signing requires security=user So I tried with this and it is not working too. My config is [global] security = user auth methods = guest map to guest = Bad User...

I just joined a Windows 10 (build 10130) to our Samba 3 domain. It seems to work. I can login, a home directory is created on the server, and I can access shares. All shares are OK, except "netlogon". Logon scripts don't run, and I cannot open the netlogon share. I get "Access denied" and a prompt to enter my username and password, which keeps coming back. At the

...ableBandwidthThrottling : False > EnableByteRangeLockingOnReadOnlyFiles : True > EnableInsecureGuestLogons : True > EnableLargeMtu : True > EnableLoadBalanceScaleOut : True > EnableMultiChannel : True > EnableSecuritySignature : True > ExtendedSessionTimeout : 1000 > FileInfoCacheEntriesMax : 32768 > FileInfoCacheLifetime : 60 > FileNotFoundCacheEntriesMax : 32768 > FileNotFoundCacheLifetime : 60 > KeepConn...

...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\LanmanWor >>kstation\Parameters] >>EnablePlainTextPassword=0 >>EnableSecuritySignature=1 >>RequireSecuritySignature=1 >> >.. >> >>The Client shows ReasonCode: 0x80004005 When I change registry to >>RequireSecuritySignature=0, I can access >> >>How I have to configure the smb-server to have a real public share for >>windows7-clients...

...y 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 expected. > > If setting is still RequireSecuritySignature=0 ? everything is working > with the changed samba config. > But - i?am forced to change from...

...: 1023 EnableBandwidthThrottling : False EnableByteRangeLockingOnReadOnlyFiles : True EnableInsecureGuestLogons : True EnableLargeMtu : True EnableLoadBalanceScaleOut : True EnableMultiChannel : True EnableSecuritySignature : True ExtendedSessionTimeout : 1000 FileInfoCacheEntriesMax : 32768 FileInfoCacheLifetime : 60 FileNotFoundCacheEntriesMax : 32768 FileNotFoundCacheLifetime : 60 KeepConn : 600 MaxCmds...

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

...quot; error, but restricted to Windows 2000 (Server,Advanced Server,Professional) installations. http://support.microsoft.com/default.aspx?scid=kb;en-us;321733 This MSKB suggests changing the following parameter on the server: HKLM\System\CurrentControlSet\Services\lanmanserver\parameters enablesecuritysignature=0 However, I find no such parameter or discussion of such parameter (naturally) in the samba docs, because of course, I'm running Samba, not a WinNT server. Questions: - - - - - - - - - - Has anybody experienced this problem elsewhere? Can anybody point out a potential solution? Did I miss...

...a 2 GB file is > 200 minutes. Microsoft KB articles talk about changing TcpAckFrequency Values on the server, for slow comms from XP to a Win2K PDC (http://support.microsoft.com/?kbid=321169) but this is on the server, and the same article talks about changing RequireSecuritySignature & EnableSecuritySignature (on the client, I think), but these are already set to 0. The most odd thing about this is that the poor performance started happening during a copy operation: 10GB were copied in a few minutes, then the connection ran slow and has run slow ever since. Any help would be greatly appreciated....

...ed my problem. The main problem is when more than one people want to use a file it get slower and slower and slower... and I don't understand why? I applied these registry patches founded in the archive [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters] "EnableSecuritySignature"=dword:00000000 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters] "EnableOplocks"=dword:00000000 but nothing changes. The smb.conf: [global] dos charset = CP852 workgroup = TGI_HU netbios name = CERBERUS server string = TGIhu fileserv...

...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\LanmanWor >kstation\Parameters] >EnablePlainTextPassword=0 >EnableSecuritySignature=1 >RequireSecuritySignature=1 > >Since this change the public share is not working anymore. I >found that smb signing requires security=user >So I tried with this and it is not working too. > >My config is > >[global] > security = user > auth methods...

...: False > > EnableByteRangeLockingOnReadOnlyFiles : True > > EnableInsecureGuestLogons : True > > EnableLargeMtu : True > > EnableLoadBalanceScaleOut : True > > EnableMultiChannel : True > > EnableSecuritySignature : True > > ExtendedSessionTimeout : 1000 > > FileInfoCacheEntriesMax : 32768 > > FileInfoCacheLifetime : 60 > > FileNotFoundCacheEntriesMax : 32768 > > FileNotFoundCacheLifetime : 60 >...

...igured with >>>security=share. >>>Now I have to tight security with setting those flags in the windows >>>client: >>>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWor >>>kstation\Parameters] >>>EnablePlainTextPassword=0 >>>EnableSecuritySignature=1 >>>RequireSecuritySignature=1 >>> >>.. >>> >>>The Client shows ReasonCode: 0x80004005 When I change registry to >>>RequireSecuritySignature=0, I can access >>> >>>How I have to configure the smb-server to have a real public &g...

...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\LanmanWorkstatio > n\Parameters] > > EnablePlainTextPassword=0 > > EnableSecuritySignature=1 > > RequireSecuritySignature=1 > . . . > when I change registry to RequireSecuritySignature=0, everything works like expected. > > If setting is still RequireSecuritySignature=0 - everything is working > with the changed samba config. > But - i'am forced to change fr...

...ings I have tried to fix it: In Windows XP Pro SP1, I have tried setting the registry entries for: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\... Memory Management\SystemPages HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\... Parameters\{EnableOplocks|EnableSecuritySignature) but with no effect. I also made sure that there were adequate permissions, as evidenced by the fact that the second attempts would succeed. In Samba, I changed/added the following and many other variations with no effect: [global] use sendfile = yes/no large readwrite = yes/no admin users = m...

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