SAMBA. Unable to set character code pages

Thakowbbery · 11-11-2005, 12:29 PM

Greetings

I've been having problems with my SAMBA due to special characters that exist in my language (á, à, ã, ç, ...), and someone told me to change the option "character set" to ISO8859-1 and "client code page" to 850.
But when I test with "testparm", I get:

henrique.hcm@0l001:~> /usr/local/samba/bin/testparm
Load smb config files from /usr/local/samba/lib/smb.conf
Unknown parameter encountered: "character set"
Ignoring unknown parameter "character set"
Unknown parameter encountered: "client code page"
Ignoring unknown parameter "client code page"
Loaded services file OK.
'winbind separator = +' might cause problems with group membership.
Server role: ROLE_DOMAIN_MEMBER
Press enter to see a dump of your service definitions

My smb.conf:

[global]
workgroup = SRSP
netbios name = 0l001
realm = SRSP.DPF
server string = 0l001
security = ADS
password server = 10.11.8.28, 10.11.8.32
encrypt passwords = yes
allow trusted domains = No
log file = /usr/local/samba/var/samba.log.0l001
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
idmap uid = 10000-60000
idmap gid = 10000-60000
template homedir = /home/%U
template shell = /bin/bash
winbind separator = +
winbind use default domain = Yes
hosts allow = 10.11.8.0/255.255.252.0
character set = ISO8859-1
client code page = 850

I'm running a compiled SAMBA 3.0.14a over Suse 9.3.
Can someone please help me out?

Ygrex · 11-16-2005, 05:01 PM

They are inexistent parametres indeed. You should use:

Code:

dos charset = 850
unix charset = ISO8859-1
display charset = ISO8859-1

Add these strings into the [global] section.

Thakowbbery · 11-21-2005, 06:24 PM

Thanks
I'll try just that.

Thakowbbery · 11-23-2005, 04:24 AM

Well
That didn't work

But I managed to solve my problem.
As that shinny light came from the sky, a thought hit me: "Why don't I try mounting the shares using CIFS instead of SMB?"
And guess what? It worked \o/

Ygrex · 11-23-2005, 04:32 AM

It is good that your problem is solved, but I use SAMBA and it converts
filenames properly. I use exactly 'dos charset', 'unix charset' and
'display charset'.