mount cifs error

[hikohan]

I can mount windows share folder in Precise 5.4.3 with :

Code: Select all

mount -t cifs //192.168.10.55/u$ -o username=foo,password=fooPass,codepage=950,iocharset=utf8 /mnt/i

But in precise 5.5 beta, returns error code 22 and mount fail.

Thanks for your notice!!

--

Precise is the next LTS version replacement of WARY,
I would like keep on testing latest Precise and report bug
as possible.

[rcrsn51]

But in precise 5.5 beta, returns error code 22 and mount fail.

Which Beta are you using? The standard one or the version with the 3.8.0 kernel?

[hikohan]

Thanks rcrsn51, the version I'm testing is 5.4.92 k3.8.0.

Download from here:
http://puppylinux.com/test/precise-5.4. ... se-k3.8.0/

Thanks for your help.

[rcrsn51]

There were other reports of cifs problems with this kernel. On the end of your options list, add "sec=ntlm"

Code: Select all

-o username=foo,password=fooPass,codepage=950,iocharset=utf8,sec=ntlm

If that doesn't work, try one of

Code: Select all

sec=
       none attempt to connection as a null user (no name)
       krb5 Use Kerberos version 5 authentication
       krb5i Use Kerberos authentication and packet signing
       ntlm Use NTLM password hashing (default)
       ntlmi Use NTLM password hashing with signing (if /proc/fs/cifs/PacketSigningEnabled on or if server requires signing also can be the default)
       ntlmv2 Use NTLMv2 password hashing
       ntlmv2i Use NTLMv2 password hashing with packet signing

[hikohan]

hi rcrsn51! I'd try all the options above but still get the mesage.

Code: Select all

# mount -t cifs //192.168.10.55/u$ /mnt/i -o username=vega,password=5wizards,codepage=950,iocharset=utf8,sec=ntlmv2i
mount error 22 = Invalid argument
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

Thanks rcrsn51!

[hikohan]

one more strange thing is those icon links I'd appended all gone
after OS upgrade from 5.4.3 to 5.4.93.

search from google, seems cifs function or kernel someing else
need patch?! is that?

Thanks for your help, rcrsn51.

I'll keep both 5.4.3 and beta running
until the latest PRECISE stable announce.

Although I still use WARY previous stable version at home.