SMBFS(FC4) to CIFS(FC5) tranition problem

[sbonar]

I was running just fine with FC4 and smbfs and now since smbfs is not supported in FC5 I am having issues with cifs. I'm trying to mount a Samba server on another Linux box and I am getting a "mount error 1 = Operation not permitted" error.

On the server side (which by the way is setup as server=share and encrypt passwords = no) I am seeing the following in the log:

[2006/03/30 15:13:19, 2] auth/pampass.c:smb_pam_auth(514)
smb_pam_auth: PAM: Athentication Error for user sbonar
[2006/03/30 15:13:19, 2] auth/pampass.c:smb_pam_error_handler(73)
smb_pam_error_handler: PAM: Authentication Failure : Authentication failure
[2006/03/30 15:13:19, 0] auth/pampass.c:smb_pam_passcheck(810)
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User sbonar !
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(235221s247,^T241241216372253351211^P31226 5^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(221s247,^T241241216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(247,^T241241216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(241241216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(241216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(235221s247,^T241241216372253351211^P31226 5^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(221s247,^T241241216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(247,^T241241216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(241241216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(241216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(216372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(372253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(253351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(351211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] lib/charcnv.c:convert_string_internal(236)
convert_string_internal: Conversion error: Illegal multibyte sequence(211^P312265^T[YESC88w/)
[2006/03/30 15:13:19, 3] smbd/sec_ctx.c:pop_sec_ctx(403)
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
[2006/03/30 15:13:19, 2] auth/auth.c:check_ntlm_password(312)
check_ntlm_password: Authentication for user [sbonar] -> [sbonar] FAILED with error NT_STATUS_WRONG_PASSWORD

Like I said I had no problems with FC4 and smbfs and nothing has changed on the server side. Also, the smbclient user app works just fine.

Help is much appreciated.

[galland]

I'm not having much fun with the new way of doing it either. After mucking around for a few hours I figured out that one must be logged in to the actual root account and not just be Super User. So login to root and type something like this in a terminal


mkdir /mnt/myshare
mount.cifs //192.168.1.100/myshare/ /mnt/myshare --verbose -o username=myname password=mypass


To make it 'stick', put it in /etc/fstab like this


//192.168.1.100/myshare/ /mnt/myshare cifs username=myname,password=mypass

[sbonar]

Unfortunately, I have been doing all my testing as root. So your suggestion will not work. Thanks anyway. :-s

[jhetrick62]

Take a look at this smb.conf file. It works like a champ for me! I get back and forth from my FC3 and my FC5, both directions and to and fr my windoze laptop also.

Jeff

[sbonar]

Thanks for the help.

However, I believe I've found the issue. In searching around somemore I found out that CIFS does not support plain text passwords so it is acutally encypting the password even though the server is requesting it not to.

[Neuropa]

I have permissions problems with CIFS and fstab in FC5...

Server Fedora Core 4 - Samba installed, configured and running.
I have many users in my LAN, all registerd in "Samba Users" with password on the Server.
On the FC4 Server there are 2 shares with read/write permissions for all users.

From Windows clients I can access to the shares without problems.
From FC4 clients I can access too, with smbfs. This is the /etc/fstab entry:
//192.168.1.1/Shared /mnt/shared smbfs username=xxxxx,password=xxxxx,umask=2,dmask=777,fm ask=777 0 0

The new Fedora Core 5 client can't use smbfs, so I have modified /etc/fstab in this way:
//192.168.1.1/Shared /mnt/shared cifs auto,user,username=xxxxx,workgroup=xxxxx,password= xxxxx,uid=500,gid=500,rw 0 0

I can mount the partition, without errors, but I don't have write permissions!
When I create a new folder, this folder has read only permissions... so I can rename or delete it only from FC4 (or Windows) clients...
And even... if I create a text file in the share with an FC4 client, this file can't be read or modified by FC5!!

Can you help me, please?

Thanks...

[rkelly]

I have permissions problems with CIFS and fstab in FC5...

Server Fedora Core 4 - Samba installed, configured and running.
I have many users in my LAN, all registerd in "Samba Users" with password on the Server.
On the FC4 Server there are 2 shares with read/write permissions for all users.

From Windows clients I can access to the shares without problems.
From FC4 clients I can access too, with smbfs. This is the /etc/fstab entry:
//192.168.1.1/Shared /mnt/shared smbfs username=xxxxx,password=xxxxx,umask=2,dmask=777,fm ask=777 0 0

The new Fedora Core 5 client can't use smbfs, so I have modified /etc/fstab in this way:
//192.168.1.1/Shared /mnt/shared cifs auto,user,username=xxxxx,workgroup=xxxxx,password= xxxxx,uid=500,gid=500,rw 0 0

I can mount the partition, without errors, but I don't have write permissions!
When I create a new folder, this folder has read only permissions... so I can rename or delete it only from FC4 (or Windows) clients...
And even... if I create a text file in the share with an FC4 client, this file can't be read or modified by FC5!!

Can you help me, please?

Thanks...


I had the same problems.
Adding te parameter 'unix extensions = no' to the global part of the samba config file solved my problem.

[Neuropa]

I had the same problems.
Adding te parameter 'unix extensions = no' to the global part of the samba config file solved my problem.

Thanks! This solved my problem too... :)