search for: sharecent

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

Hi, I am testing share parameters, and have the following share definition: ## Section - [shareA] [shareA] path = /tmp/shareA writelist = user1 and do not understand why user1 cannot write files in the share when connected as user1. Unix permissions for the share files are rw for everyone, and the share directory has wide-open permissions. Samba version is 3.0.20b-3.4-SUSE.

Hi All, Running Samba on a Fedora 4 machine in a mixed home environment. Domain=[HOME-NETWORK] OS=[Unix] Server=[Samba 3.0.14a-2] Trying unsuccessfully to mount the 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

I get these repeated errors from my windows server but cannot understand why. I am running samba on fedora 4 boxes and my servers run on windows 2000. Whenever someone attempts to manually access a shared volume on a linux box and use the right credentials we never experience the 1326 error. I included the samba config file below and more details of both errors from event viewer. Does anyone have

> 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

(Let's keep this on the list) Aurélien Aptel via samba <samba at lists.samba.org> writes: > Chad William Seys <cwseys at physics.wisc.edu> writes: >> Somehow the destination having 'msdfsroot yes' prevents the cifs kernel >> module from following the link. I've taken a look at your traces and right off the bat I see things like this: [...]