Description of problem: Try: mount -t cifs //$SERVER/$USERS /mnt/homedrive -o credentials=... Where $SERVER is a W2K Domain server and $USERS is the "home" directory for all users, i.e., actual home is ./"name" Attempt to connect returns message: mount error 20 = Not a directory If I change the mount to mount -t cifs //$SERVER/$USER/myname ... I get the message: mount error 6 = No such device or address Version-Release number of selected component (if applicable): samba-client 3.0.8-0.pre1.3 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This still happens under FC4 with samba-client-3.0.14a-2.
This problem may stem from limited access rights on the Windows share. From a W2K box pointing Windows Explorer to \\SERVER\HOME produces the message "\\SERVER\HOME is not accessible..." (apparently I lack rights to view files within the HOME directory). If I point explorer to \\SERVER\HOME\dir1\mydir it works and I can see/modify my files. Under linux, mounting //SERVER/HOME as "smbfs" on mount point /timmy works. I can then access my files via /timmy/dir1\\mydir (sic). The backslash between dir1 and mydir is vital, because /timmy/dir1/mydir does not work.
I have displayed the arguments being passed to the mount() system call in the source code of mount.cifs. Everything looks correct. It is the mount() call that returns "error code 20 - Not a directory". Referring to #2: The //SERVER/HOME directory is secured such that I cannot view files within it -- this is in a corporate setting. With smbclient I *can* smbclient //SERVER/HOME and then cd into my directory. I have to suspect that the mount() call is testing to see if the resulting CIFS mount is actually a directory and getting some kind of "no access" error. Again the cifs mount fails where smbfs and smbclient succeed. With the removal of smbfs support, I am no longer able to mount my corporate network "home" directory. Also, I have tried every combination of UNC I can think of: \\\\SERVER\\HOME, //SERVER/HOME, //SERVER\\HOME, and so on. Nothing works with cifs.
Additionally, I believe that this is a kernel problem or a mount() system call problem. However, I am unable to change the component or the version (which is should be FC5). The bug owner needs to change this.
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
As this works with smbfs, then this is really a kernel bug CIFS VFS module. Moved there.
If you disable Linux extensions are you then able to mount this share? # echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled ...then try the mount
No update in several months. Closing bug with resolution of INSUFFICIENT_DATA. Please reopen if you're still experiencing this problem.