search for: sharec

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 = /usr/sbi...

.... Thanks for any help anyone can give. Here is the complete smb.conf file (note guest parameters): # # Generated by /root/samba_iiosb/testing/util/modify_samba_config.pl # [global] adminusers = Administrator, root logonhome = \\%L\%U\.9xprofile addsharecommand = /root/samba_iiosb/testing/util/modify_samba_config.pl addgroupscript = /usr/sbin/groupadd -p "%g" deletesharecommand = /root/samba_iiosb/testing/util/modify_samba_config.pl include = /etc/samba/dhcp.conf deleteu...

...dir that's on hdb1 on another Fedora 4 machine. Can mount any dir from hda just fine. Only problem is the one on hdb1. File permissions and everything else I can think of checking is identical. Just refuses to mount hdb1. Here is the error message: # mount -t smbfs -o ip=10.0.0.4 //BASEMENT/sharec /share Password: 3108: tree connect failed: ERRDOS - ERRnosuchshare (You specified an invalid share name) SMB connection failed Here is smb.conf: [global] workgroup = Home-Network server string = Basement Router netbios name = basement security = SHARE...

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

> 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

...ot 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 properly used _two_ backsla...