Yes, I have the same problem. Is there another fix then putting Samba 2.0 on? I am using Beta 6.0 and kernel 2.2.1. Hope somone has an answer, as not being able to mount or NT servers is annoying. -----Original Message----- From: Rachel Greenham <rachel@epinet.co.uk> at Internet <IMCEACCMAIL-Rachel+20Greenham+20+3Crachel+40epinet+2Eco+2Euk+3E+20at+20Inte rnet@mail.crc.com> To: suse-linux-e@suse.com at Internet <IMCEACCMAIL-suse-linux-e+40suse+2Ecom+20at+20Internet@mail.crc.com> Date: Tuesday, February 09, 1999 8:48 AM Subject: [SuSE Linux] Problems with smbmount - SuSE 6.0 with 2.2.1
Eek! Suddenly I find I can't mount our NT servers!
OK, I had the Samba 1.9-something as installed from SuSE 6.0, and I'm running kernel 2.2.1. I can print fine to a Samba printer (except from Word Perfect but that's another story), and I can log on using smbclient. But attempting to mount NT shares fails, with "Invalid argument". The exact same smbmount command on the system rebooted with SuSE 2.0.36 works fine. I tried upgrading to Samba 2.0 (2.0.0 as there's a SuSE rpm available for it, but smbmount itself reports version 2.0.2) but it made no difference. I tried taking SMB support out of the 2.2.1 kernel, and making it available as a module - with the module not loaded I get, unsurprisingly "Operation not supported by device", then I insmod it and as before, "Invalid argument".
Username/password definitely correct, by the way. And no difference no matter how pedantic I get with the other options.
Now, another mystery: I tried downloading and installing Samba 2.0.0 before, when I was still on SuSE 6.0 beta. That time I did a make-and-install rather than from an rpm, (and never did finish installing eg: man pages which were also very different) and the smbmount I got was *completely* different - different syntax, different man pages etc. (eg: instead of
smbmount //<server>/<service> <mount-point> -U <smbusername> -P <smbpassword> -u <username>
it was
smbmount "\\\\<server>\\<service>" <smbpassword> -c 'mount <mount-point> -u <username>'
Very odd, but it worked (except that it didn't keep the sessions alive).
But now, when I've reinstalled this 2.0.0, it's just as it was before.
Confused.
-- Rachel - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>