GarenTsen
04-04-2004, 05:57 AM
Hi,
I've upgraded my RH8 server to Fedora Core 1 and everything went fine. What I did was to install FC1 on another disk and when everything worked I removed the disk with RH8.
But... it seems that Samba 3 works a bit differently with international characters. My swedish characters (åäö) worked fine in my older system, now I just get garbled filenames when browsing files and directories from my Win XP client.
After som digging around I found that Samba 3 uses Unicode but I don't understand why this should be a problem. I've tried alot of different settings in smb.conf but nothing seems to rectify the situation.
If I create a file with these characters from my winXP client it works. It is just the older ones that won't show correctly. I'd fix it by hand but my LVM volume is about 650 GB with files and folders with these charactes all over the place.
Is there anyone out there that has experienced the same and managed to fix it (or can give me any pointers towards a solution)?
Here's what I've done in smb.conf:
[global]
character set = iso8859-1
valid chars = 206:217 204:216 224:231 32
client codepage = 850
I've upgraded my RH8 server to Fedora Core 1 and everything went fine. What I did was to install FC1 on another disk and when everything worked I removed the disk with RH8.
But... it seems that Samba 3 works a bit differently with international characters. My swedish characters (åäö) worked fine in my older system, now I just get garbled filenames when browsing files and directories from my Win XP client.
After som digging around I found that Samba 3 uses Unicode but I don't understand why this should be a problem. I've tried alot of different settings in smb.conf but nothing seems to rectify the situation.
If I create a file with these characters from my winXP client it works. It is just the older ones that won't show correctly. I'd fix it by hand but my LVM volume is about 650 GB with files and folders with these charactes all over the place.
Is there anyone out there that has experienced the same and managed to fix it (or can give me any pointers towards a solution)?
Here's what I've done in smb.conf:
[global]
character set = iso8859-1
valid chars = 206:217 204:216 224:231 32
client codepage = 850