You are not logged in.
Greetings all,
Have done the Google search in regards to this issue, tried some things that I have read but no dice.
I have been doing the same thing for quite a while now, mounting the SAMBA share with mount -t cifs but now I all of a sudden get a Permission denied error.
# mount -t cifs //192.168.0.10/storage /mnt/server -o username=ichase
Password for ichase@//192.168.0.10/storage:
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
When ever I reboot the laptop after a kernel update or for what ever reason, I simply add the above mentioned line and alas I have access to my SAMBA server shares. Yesterday was no different except now I get the permission denied error.
Here is what I have tried thus far.
Have rebooted both the laptop and the server.
I have downgraded the samba and smbclient packages on the server (running Arch) to see if an update caused the issue (has happened in the past) no dice. Have everything updated to current packages as of this morning. Same permission denied error.
I have seen some threads that stated instead of using mount -t cifs to use mount.cifs but I get the same error.
Also have seen to try mount -t smbfs but I get a
mount: unknown filesystem type 'smbfs'
<-----thought this was part of the smbclient package, may be wrong.
Also read to replace the IP with the hostname, that did not work either. Except for keeping my packages up to date with pacman -Syu I have not touched the smb.conf file because everything has been working flawlessly.
To answer the question that I am sure is going to be asked. Yes, I still have access to the share drive and printer via Windows.
Thanks ahead of time for any suggestions or guidance you may offer.
All the best,
Ian
Last edited by ichase (2013-03-23 02:09:56)
Offline
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Thank you for the guidance alphaniner. Will need to try and add; sec=ntlm to the end of the line this evening. From what I am reading from the link you provided, this should hopefully do the trick.
Thanks again, will update post as solved if this fixes the issue or add addiitonal info.
All the best,
Ian
Offline
I had the same issue on two Arch installs and the sec=ntlm flag fixed both machines. I just wonder why this was necessary. There seems to be a lot of concern about using that flag, in regards to security. Anyone have any idea why this is now required?
Offline
Thanks again for pointing me in the right direction alphaniner. Adding the sec=ntlm at the end allowed me to mount my Samba share.
# mount -t cifs //192.168.0.10/storage /mnt/server -o username=ichase,sec=ntlm
Now as you mentioned Beezlebud, I am currious as to why and if there is a bug in place to eliminate the need for this additional flag that I am reading is not very secure.
Thanks again,
Ian
Last edited by ichase (2013-03-23 02:16:50)
Offline
Updated from FC9 to F20.
Command that stopped working:
mount -t cifs //192.168.1.1/share0 /mnt/share0 -o username=xyz.abc.corporate.com/chico,password=swordfish,file_mode=0777,dir_mode=0777,noserverin
Command that works:
mount -t cifs //192.168.1.1/share0 /mnt/share0 -o username=chico,password=swordfish,file_mode=0777,dir_mode=0777,noserverin
Offline
Thanks for the additional info ewdudley
Last edited by ichase (2014-07-29 23:44:48)
Offline