When I mount the share, the Windows permissions seem to behave as expected. In fact, I can write a file to the root of the share as root. For example, sudo touch /path/to/share/test. But no matter what I do, mount would set write permission on the mount point. Very strange.
Now, I never intended for those directories to be set read-only. And in fact, they really aren't. So this surprised me. According to Microsoft:
*sigh* That comes from here: http://support.microsoft.com/kb/326549/Unlike the Read-only attribute for a file, the Read-only attribute for a folder is typically ignored by Windows, Windows components and accessories, and other programs. For example, you can delete, rename, and change a folder with the Read-only attribute by using Windows Explorer. The Read-only and System attributes is only used by Windows Explorer to determine whether the folder is a special folder, such as a system folder that has its view customized by Windows (for example, My Documents, Favorites, Fonts, Downloaded Program Files), or a folder that you customized by using the Customize tab of the folder's Properties dialog box. As a result, Windows Explorer does not allow you to view or change the Read-only or System attributes of folders.
Using the attrib command to remove the read-only flag solved the problem.
That was a fantastic find! I will update the troubleshooting section of the howto when I get home from work this evening.
new problem with a fresh install of karmic;
I have two shares on the same network drive, one is Public, and has no username/password settings, the other uses a username, but no password.
I have repeated the steps to get my Jaunty install to connect, but the one using .smbcredentials file access the drive but does not access the folder - i.e I get an empty folder.
The Public folder works fine.
I've discovered that files I move into the folder stay there and show up when logging into the folder over:
Places > Network > Windows Network > netbios > folder
Just nothing shows through the fstab option!
credentials file looks like:
password is blank, and work fine like this in Jauntyusername=xxxxxxx
Code://mss-014588/church /media/Church cifs credentials=/root/.smbcredentials,iocharset=utf8,gid=1000,uid=1000,nounix,nobrl,file_mode=0777,dir_mode=0777 0 0 //mss-014588/Public /media/Public cifs guest,rw,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
Last edited by dmizer; October 16th, 2009 at 01:31 AM. Reason: changed to code markup to avoid arbitrary space
Code://mss-014588/church /media/Church cifs user=your-username,iocharset=utf8,gid=1000,uid=1000,nounix,nobrl,file_mode=0777,dir_mode=0777 0 0
I'm having a similar problem:
my timecapsule has a guest account and I mount it using this one but I cannot see what's inside the storage but files are there because cd works fine and I can even read files if I use the appropriate sw (e.g. mplayer for .mp3) but ls doesn't show anything on the device and even nautilus behaves the same.
user=guest doesn't do the job