search for: shareb

I have the following smb.conf file. Note the "guestaccount" parameter, and the guest parameters in shareA, shareB, and shareC. # # Generated by modify_samba_config.pl # [global] adminusers = Administrator, root logonhome = \\%L\%U\.9xprofile addsharecommand = /usr/local/autobench/sources/samba/util/modify_samba_config.pl addgroupscript...

...## Section - [profiles] [profiles] directorymask = 0700 createmask = 0600 readonly = No storedosattributes = Yes comment = Network Profiles Service path = %H ## Section - [shareB] [shareB] path = /tmp/shareB guestok = yes writelist = user1 # # end of generated smb.conf # Sincerely, Don Watson Linux Technology and Solutions; Beaverton, OR 503-578-4861/TL: 775-4861; dwatson@us.ibm.com

I see *things* happening here. XP. Trying to access \\host\sharea. works fine \\host\shareb - pops up password window shares a and ba may vary between reboots. I spent 15 minutes scratching my head and finally tossed out "snoop port 445" So what I've seen. On shares I can access wxp do: 1. Send: Tree Connect AndX Request \\host\sharea 2. Receive: Tree Connect AndX Response...

Hi, i have a smba 3 working, and I? m trying to build dfs .When I set up my dfs this way: ln ?s msdfs:serverA\\shareA name, or ln-s msdfs:serverA\\shareB, it is working! But if I try ln-s msdfs:serverA\\shareA,serverA\\shareB name, I only can get the first share (shareA) in the network. Have someone did it and how can I succeed ? Daniel

> Which smb version are you using (mount option)? Support for DFS on smb2+ > was only added in linux 4.11. smbstatus shows the connection as NT1. DFS links do work like this: serverA_msdfsrootYES => serverB_msdfsrootNO But not like this: serverA_msdfsrootYES => serverB_msdfsrootYES Somehow the destination having 'msdfsroot yes' prevents the cifs kernel module from

...link        full_audit:failure = mkdir rmdir write pwrite rename unlink        full_audit:facility = local5        full_audit:priority = info [ShareA]        path = /data/sharea        admin users = @"DOMAIN-LO\LocalAdmins"        valid users = @"DOMAIN-LO\Domain Users" [ShareB]        path = /data/shareb        admin users = @"DOMAIN-LO\LocalAdmins"        valid users = @"DOMAIN-LO\Domain Users" Does anyone had similar issues? It seems the problem is not with samba 4.7.7 upgrade because one of test virtual hosts with almost identical configurat...

...to me the link is not properly substituted and there might some issues with Unix Extensions mixing path separators. I couldn't reproduce this on recent master kernel but I'll give it a try on v4.9 which you seem to be using. My setup is cifs.ko connecting to sambaA/shareA -> sambaB/shareB -> sambaB/shareC using unix extensions and both servers having 'msdfs host = yes' and shareA, shareB with 'msdfs root = yes'. Also, how did you create your symbolic links on the samba machine? (exact command). Just a hunch at this point but you might want to check you properl...

...write pwrite rename unlink >        full_audit:facility = local5 >        full_audit:priority = info > > [ShareA] >        path = /data/sharea >        admin users = @"DOMAIN-LO\LocalAdmins" >        valid users = @"DOMAIN-LO\Domain Users" > > [ShareB] >        path = /data/shareb >        admin users = @"DOMAIN-LO\LocalAdmins" >        valid users = @"DOMAIN-LO\Domain Users" > Eventually log.wb-LO reports: [2018/08/06 16:30:36.602929, 50, pid=1218, effective(0, 0), real(0, 0), class=tevent] ../lib/util/te...

...le = /etc/samba/smbpasswd socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 local master = no dns proxy = no syslog only = yes #============================ Share Definitions ============================== [sharea$] path = /a writeable = no write list = @group create mask = 775 [shareb$] path = /b writeable = no write list = @group create mask = 775 [sharec$] path = /c writeable = no write list= @group create mask = 775