[SOLVED] can't mount CIFS share, but smbclient and smb:// (KIO) works
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
can't mount CIFS share, but smbclient and smb:// (KIO) works
I am about to go crazy. I need to access a samba share at my university. While I have no problems accessing it using smbclient or the smb:// KIO slave from KDE, I just can't get it mounted using the "mount" command. I played around with options and googled for hours. The only threads I can find with respect to this topic go dead.
All I get from "mount" is the following error message:
mount error(5): Input/output error
The logs in /var/log, mostly don't contain any hints. Only syslog shows something when I grep it for CIFS. However, it's useless, as only the error number (5) is repeated.
Any help is greatly appreciated.
Let me mention a few more details: this is kubuntu 9.10 (karmic, 32bit). The kernel is 2.6.31-16. Turning my firewall (guarddog) off did not help either. To access the server, I tried both the IP and the hostname (netbios). To specify the credentials, I tried both a file as well as directly putting them into the options. No avail.
Thanks very much for your suggestions. I had already tried using the server IP directly, and that did not help. I was also aware of this other thread you mentioned, but there was not really any useful information there. One suggestion was referring to using IPs, another vague comment (going back to 2006) is that it was related to an old version (2.x) of the samba servers. I had already contacted our sysadmins to find out what samba version they are using -- no response yet.
What's strange is that smbclient and the smb:// KIO slave are performing very well, but cifs does not work. Let me show you what I did:
sudo mount -v -t cifs -o credentials=/home/hasi/.encfs/nanomat //***.***.***.***/nanomat$/ /media/nanomat/
The above code gives me the error (the asterisks represent the IP address given in decimal format). Smbclient, on the other hand does not have any problems:
smbclient -A /home/hasi/.encfs/nanomat //***.***.***.***/nanomat$/
With this code, I get logged in within less than a second. As you see, I am even using the same credentials file, etc. So I have really no idea what's going on. Also how do you debug something like this if you don't have any meaningful error message?
Thanks again for your quick reply.
I echoed the flags as you suggested, to no avail. (I also made sure that the 0 and 1 were successfully written using the "cat" command for the named destinations.)
I also tried
I suppose your hint with respect to WME does not apply, as I am connected via ethernet (as a matter of fact now part of the same LAN than said Samba server).
I also removed the trailing line feed using the hex editor. No success. Would any of these steps you suggested require a reboot?
OK, my subject line is a little provocative, but more and more evidence is pointing into this direction. I am now on 2.6.32 (a version that's going to be supported for a longer while), and I still have the very same problem: I cannot mount a Windows share using mount.cifs. When I try to connect via smbclient (using the same credentials file), it works. Also, I can connect via the smb:/ KIO slave from KDE. So if mount.cifs is not broken, what else could it be? I did a little more research and found that SMB error code 31 translates into "NT_STATUS_ILLEGAL_CHARACTER". Does that mean anything to anybody?