search for: requiresecuritysignatur

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 RequireSecuritySignature=1 If c...

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 like those are not helping: security = user...

Hi Louis Thank you! As i wrote in my first post, i tried even with these settings: client max protocol = SMB3 client min protocol = SMB2 client signing = required server signing = required But it was not working - as soon I use RequireSecuritySignature=1 on the client. It seems for that the client is stopping communication since the Win7-client expects something from samba. net use t: \\samba\pub<file:///\\samba\pub> systemerror 1240 MS knowledgebase article speek about enable plain text passwords. But this is wrong since...

Hi Rowland In former time there was "security=share", now i have to use "RequireSecuritySignature=1" on client side. Documentation for SMB signing says, this is only possible with "security=user", not with share. So I switched to security=user, configured guest-access to the public share and activated this RequireSecuritySignature=1 And then - with RequireSecuritySignature=1 - t...

...shure, no man in the middle is manipulating my smb-messages. Gru? Raphael ___________________________________________ -----Urspr?ngliche Nachricht----- Von: Rowland Penny [mailto:rowlandpenny at googlemail.com] Gesendet: Montag, 16. M?rz 2015 10:39 An: samba at lists.samba.org Betreff: Re: [Samba] RequireSecuritySignature=1 and public share with guest not working On 16/03/15 09:29, Olszewski, Raphael wrote: > > Hi Rowland > > In former time there was "security=share", now i have to use > "RequireSecuritySignature=1" on client side. > Documentation for SMB signing says, this is...

...bmc read only = no guest ok = yes >-----Oorspronkelijk bericht----- >Van: r.olszewski at ssc-services.de >[mailto:samba-bounces at lists.samba.org] Namens Olszewski, Raphael >Verzonden: vrijdag 13 maart 2015 10:42 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] RequireSecuritySignature=1 and public >share with guest not working > >Hi >I tried exactly your type of config. > >With "RequireSecuritySignature=0" the anon access is working >like expected. >As soon, as I set "RequireSecuritySignature=1" it is not >working anymore. >...

...ouis > > Thank you! > As i wrote in my first post, i tried even with these settings: > client max protocol = SMB3 > client min protocol = SMB2 > client signing = required > server signing = required > But it was not working - as soon I use RequireSecuritySignature=1 on the client. > > It seems for that the client is stopping communication since the Win7-client expects something from samba. > net use t: \\samba\pub<file:///\\samba\pub> > systemerror 1240 > > MS knowledgebase article speek about enable plain text passwo...

On 16/03/15 12:14, Olszewski, Raphael wrote: > > 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 like those are not helping:...

...server signing = required shows with testparm client signing = required server signing = required That shows me: testparm is interpreting the conf and shows me, what it is using really. BUT - even with your config I get exactly the same picture as in my countless tries before: RequireSecuritySignature=0 (old value) => share is working RequireSecuritySignature=1 (needed value) => share is NOT working, and I get the client-error 1240 or 0x80004005 (the only change is this flag from 0 to 1) To clarify: on client side i ONLY change this value RequireSecuritySignature to 1. Nothing else....

...his one, never used it.. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: r.olszewski at ssc-services.de >[mailto:samba-bounces at lists.samba.org] Namens Olszewski, Raphael >Verzonden: vrijdag 13 maart 2015 15:57 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] RequireSecuritySignature=1 and public >share with guest not working > >Hi Louis >I explicitly have to change on win7-client the parameter >[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWor >kstation\Parameters] >from RequireSecuritySignature=0 => RequireSecuritySignature=1 >a...

...ting my smb-messages. > > Gru? Raphael > ___________________________________________ > -----Urspr?ngliche Nachricht----- > Von: Rowland Penny [mailto:rowlandpenny at googlemail.com] > Gesendet: Montag, 16. M?rz 2015 10:39 > An: samba at lists.samba.org > Betreff: Re: [Samba] RequireSecuritySignature=1 and public share with > guest not working > > On 16/03/15 09:29, Olszewski, Raphael wrote: > > > > Hi Rowland > > > > In former time there was ?security=share?, now i have to use > > ?RequireSecuritySignature=1? on client side. > > Documentation for...

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

...parm > client signing = required > server signing = required > > That shows me: testparm is interpreting the conf and shows me, what it > is using really. > > BUT ? even with your config I get exactly the same picture as in my > countless tries before: > RequireSecuritySignature=0 (old value) => share is working > RequireSecuritySignature=1 (needed value) => share is NOT working, and > I get the client-error 1240 or 0x80004005 (the only change is this > flag from 0 to 1) > > To clarify: on client side i ONLY change this value > RequireSecuri...

...llo 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 log file = /var/log/sam...

...at home for my kodi server. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: r.olszewski at ssc-services.de >[mailto:samba-bounces at lists.samba.org] Namens Olszewski, Raphael >Verzonden: donderdag 12 maart 2015 18:17 >Aan: samba at lists.samba.org >Onderwerp: [Samba] RequireSecuritySignature=1 and public share >with guest not working > >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\...

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 messages from the servers and the...

...; FileNotFoundCacheEntriesMax : 32768 > FileNotFoundCacheLifetime : 60 > KeepConn : 600 > MaxCmds : 32768 > MaximumConnectionCountPerServer : 64 > OpLocksDisabled : False > RequireSecuritySignature : False > SessionTimeout : 60 > UseOpportunisticLocking : True > WindowSizeThreshold : 1 > > PS C:\Users > > > Any advice on the optimal SMB tuning parameters and their respective values > for both the...

...heLifetime : 60 FileNotFoundCacheEntriesMax : 32768 FileNotFoundCacheLifetime : 60 KeepConn : 600 MaxCmds : 32768 MaximumConnectionCountPerServer : 64 OpLocksDisabled : False RequireSecuritySignature : False SessionTimeout : 60 UseOpportunisticLocking : True WindowSizeThreshold : 1 PS C:\Users > Any advice on the optimal SMB tuning parameters and their respective values for both the SMB client and server sides would be hi...

...ith windows client am getting following error in my server. " Unexpected RPC Fragment size! (0)" In client side am getting "Remote procedure call failed and did not execute" And the samba share not mounted. So far i tried regedit with Lanman workstation "parameter". RequireSecuritySignature = 0 and server side , smb.conf i added, server signing =disabled client signing = disabled. Also tried in gpedit.msc with windows security setting to disabled client side. Using the same patch even i can mount and copy data across samba share in all linux client. What is the problem with wi...

...k. The time (estimated) to copy 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 w...