similar to: RequireSecuritySignature=1 and public share with guest not working

Hai, Try these settings in global settings. ####### Authentication ####### ## stand alone everything open. security = user guest ok = yes map to guest = bad password add these to the share. guest ok = yes Sets samba open without pasword prompt. I use it at home for my kodi server. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: r.olszewski at ssc-services.de

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

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

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

Due to security reasons smb signing has to be activated and this share between linux and windows is now dead. And I do not find the correct settings to do a public share in this szenario. It has to be public, because the linux is'nt allowed to join the domain and on the other way, the win-clients cannot leave their domains. And I think, just signing smb-messages should not speek against a

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

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 Rowland i've made the config exactly like you sent. Doing testparm gives me Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[pub]" Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions [global] netbios name = ME

We've a Samba 4 domain (no AD, just DC) with LDAP backend on Ubuntu 14.04. This server has been migrated from files backend to LDAP by the previous maintainer, I know the version is pretty old but we cannot update at the moment. The domain works fine with some W7 and W10 (updated from 7) computers, but we have purchased a new Lenovo laptop with Win10 which joined the domain seamlessly but

check the output of : echo "\n" | testparm -vv | grep signing and echo "\n" | testparm -vv | grep protocol for my the default is : client max protocol = NT1 but i dont use signing. but i "think" you need to set the client signing = manadatory and client max protocol = SMB2 ( from man smb.conf ) but if anyone know this better on the list, please

On 16/03/15 07:56, Olszewski, Raphael wrote: > 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. >

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

On 16/03/15 09:52, Olszewski, Raphael wrote: > > Due to security reasons smb signing has to be activated and this share > between linux and windows is now dead. > > And I do not find the correct settings to do a public share in this > szenario. > > It has to be public, because the linux is?nt allowed to join the > domain and on the other way, the win-clients cannot

On 16/03/15 15:00, Olszewski, Raphael wrote: > > 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

On 17/03/15 09:02, Olszewski, Raphael wrote: > > Hi Rowland > i?ve made the config exactly like you sent. > > Doing testparm gives me > Load smb config files from /etc/samba/smb.conf > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) > Processing section "[pub]" > Loaded services file OK. > Server role: ROLE_STANDALONE > Press

Hello Well I am relatively new so some of these issues may not fall under the subject that I have used. 1. How do I do a Pareto. Following is the approach I took. My data looks like this df2_9 Reaason.for.failure Frequency 1 Phy Conn 1 2 Power failure 3 3 Server software 29 4 Server hardware 2 5 Server out of mem 32

Hi, I'm new here and I've got a problem. OK this is evident. Running OpenSuSE 13.1 as SAMBA4-PDC with openLdap-backend. All from SuSE Repos. Works fine except joining a Windows-Client to the domain. This means also no shared-profiles. I'm able to use the shares from the PDC on the windows-clients. User- and group-permissions are working. smb.conf: [global] workgroup = BIH

Our samba server in ap-east-1 is running very slow today I noticed three things in log.smb, and I don't understand any of them ---------- #1 roughly every 80 seconds what appears to be a reconnect loop [2020/11/19 17:35:46.283315, 2] ../../source3/lib/tallocmsg.c:87(register_msg_pool_usage) Registered MSG_REQ_POOL_USAGE [2020/11/19 17:35:46.287132, 1]

Hello, Came across a crash on samba-server(4.4) RHEL-7.3. (gdb) bt #0 0x00007f8e1e4821d7 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007f8e1e4838c8 in __GI_abort () at abort.c:90 #2 0x00007f8e1fde2c4b in dump_core () at ../source3/lib/dumpcore.c:322 #3 0x00007f8e1fdd6007 in smb_panic_s3 (why=<optimized out>) at ../source3/lib/util.c:814 #4

W dniu 24.08.2018 o 13:10, Charles Lepple pisze: > Sorry, I didn't mean to imply that the master branch was necessarily going to be different, just wanted to make sure you had everything set up to recompile. The real test is to see if things change after commenting out that line (such as by changing it to start with "//"): > > // { "shutdown.return", 0, 0,