All, If the post "Samba 3.6 -> 4.1 change that prevent sharing / - mount error(13)" makes it to the list, I apologize, but it has been over a day and I have no indication that the post ever made it to the list. The issue is that in versions prior to 4.x, I was able to create a root share in samba, but now, something prevents it from being mounted. The relevant smb.conf is: security = user admin users = david [config] comment = Phoinix Config (Archlinux) path = / valid users = david force user = root force group = root browseable = no writeable = Yes With 3.6.6-1 all works as expected. However in 4.1.2-1 a mount error(13) is received when attempting to mount the share on a remote linux host: 16:07 alchemy:~> sudo mount.cifs //phoinix/config /mnt/phix-cfg -o username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm mount error(13): Permission denied (yes-credentials are correct, all other shares mount fine) Was there a change in 4.x that prevents doing this? If so, what? -- David C. Rankin, J.D.,P.E.
On Thu, 2013-12-05 at 16:53 -0600, David C. Rankin wrote:> All, > > If the post "Samba 3.6 -> 4.1 change that prevent sharing / - mount error(13)" > makes it to the list, I apologize, but it has been over a day and I have no > indication that the post ever made it to the list. > > The issue is that in versions prior to 4.x, I was able to create a root share > in samba, but now, something prevents it from being mounted. The relevant > smb.conf is: > > security = user > admin users = david > > [config] > comment = Phoinix Config (Archlinux) > path = / > valid users = david > force user = root > force group = root > browseable = no > writeable = Yes > > With 3.6.6-1 all works as expected. However in 4.1.2-1 a mount error(13) is > received when attempting to mount the share on a remote linux host: > > 16:07 alchemy:~> sudo mount.cifs //phoinix/config /mnt/phix-cfg -o > username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm > mount error(13): Permission denied > > (yes-credentials are correct, all other shares mount fine) > > Was there a change in 4.x that prevents doing this? If so, what?Very interesting. Nothing deliberately prevents this. Is there anything in the server-side logs? Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
can you try it like this. ( watch the end of the line ) sudo mount.cifs //phoinix/config /mnt/phix-cfg -o username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm,sec=ntlmv2>-----Oorspronkelijk bericht----- >Van: drankinatty at suddenlinkmail.com >[mailto:samba-bounces at lists.samba.org] Namens David C. Rankin >Verzonden: donderdag 5 december 2013 23:53 >Aan: samba >Onderwerp: [Samba] What in samba 4.1 prevents a '/' share? > >All, > > If the post "Samba 3.6 -> 4.1 change that prevent sharing / >- mount error(13)" >makes it to the list, I apologize, but it has been over a day >and I have no >indication that the post ever made it to the list. > > The issue is that in versions prior to 4.x, I was able to >create a root share >in samba, but now, something prevents it from being mounted. >The relevant >smb.conf is: > > security = user > admin users = david > >[config] > comment = Phoinix Config (Archlinux) > path = / > valid users = david > force user = root > force group = root > browseable = no > writeable = Yes > > With 3.6.6-1 all works as expected. However in 4.1.2-1 a >mount error(13) is >received when attempting to mount the share on a remote linux host: > >16:07 alchemy:~> sudo mount.cifs //phoinix/config /mnt/phix-cfg -o >username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm >mount error(13): Permission denied > >(yes-credentials are correct, all other shares mount fine) > > Was there a change in 4.x that prevents doing this? If so, what? > >-- >David C. Rankin, J.D.,P.E. >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba > >
Andrew, this happens after upgrading to at least kernel 3.2.x AND some upgrades samba 3.6.x i have seen this on all my servers ( debian/ubuntu ) adding the sec= fixes this. same with lower samba versions, i have 1 Sco6 server with samba 3.0.x for that one, i've set sec=ntlm, All others now have sec=ntlmv2 without the sec, same error and impossible to mount. Louis>-----Oorspronkelijk bericht----- >Van: abartlet at samba.org [mailto:samba-bounces at lists.samba.org] >Namens Andrew Bartlett >Verzonden: vrijdag 6 december 2013 8:41 >Aan: David C. Rankin >CC: samba >Onderwerp: Re: [Samba] What in samba 4.1 prevents a '/' share? > >On Thu, 2013-12-05 at 16:53 -0600, David C. Rankin wrote: >> All, >> >> If the post "Samba 3.6 -> 4.1 change that prevent sharing >/ - mount error(13)" >> makes it to the list, I apologize, but it has been over a >day and I have no >> indication that the post ever made it to the list. >> >> The issue is that in versions prior to 4.x, I was able to >create a root share >> in samba, but now, something prevents it from being mounted. >The relevant >> smb.conf is: >> >> security = user >> admin users = david >> >> [config] >> comment = Phoinix Config (Archlinux) >> path = / >> valid users = david >> force user = root >> force group = root >> browseable = no >> writeable = Yes >> >> With 3.6.6-1 all works as expected. However in 4.1.2-1 a >mount error(13) is >> received when attempting to mount the share on a remote linux host: >> >> 16:07 alchemy:~> sudo mount.cifs //phoinix/config /mnt/phix-cfg -o >> >username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm >> mount error(13): Permission denied >> >> (yes-credentials are correct, all other shares mount fine) >> >> Was there a change in 4.x that prevents doing this? If so, what? > >Very interesting. Nothing deliberately prevents this. Is there >anything in the server-side logs? > >Andrew Bartlett > >-- >Andrew Bartlett http://samba.org/~abartlet/ >Authentication Developer, Samba Team http://samba.org >Samba Developer, Catalyst IT >http://catalyst.net.nz/services/samba > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba > >
Apparently Analagous Threads
- upgrade 4.4 -> 4.5 broke standalone server smbmount of drives?
- kernel update to 3.12.5-1, now: upsd[617]: getaddrinfo: Servname not supported for ai_socktype
- kernel update to 3.12.5-1, now: upsd[617]: getaddrinfo: Servname not supported for ai_socktype
- kernel update to 3.12.5-1, now: upsd[617]: getaddrinfo: Servname not supported for ai_socktype
- SOLVED Re: kernel update to 3.12.5-1, now: upsd[617]: getaddrinfo: Servname not supported for ai_socktype