868 Views 6 Replies Latest reply: Dec 29, 2007 8:43 AM by brainslice
Looks like it's an NLS setting on the Linux box.
Make sure you're running the latest Samba and configure smb.conf to use utf-8.
Here's a link to a page that discusses this: http://www.nslu2-linux.org/wiki/Optware/Samba
International character support or Unicode support
If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.
Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients
unix charset = UTF-8
display charset = UTF-8
dos charset = 866
I use these settings for support of Norwegian and Portugeese characters in filenames under Unslung 6.8 (samba 3): unix charset = UTF-8 dos charset = CP850 display charset = ISO-8859-1 I put these settings into /unslung/smb.conf and put the rc.samba in the same directory (comment away the first line). You also have to change the config file name in /unslung/smb.conf.
Have you tried watching your syslogs when the failure happens? This may give some indication on what's going on. I agree with the above posts that this is likely an issue with the the version and/or configuration of your smbd.
fwiw, samba 3.0.24-2.28 running on SLES10 works with Leopard no problem. If you don't have any luck with your current setup you may want to have a look at openSuSE http://www.opensuse.org It's a nice distro and is very easy to set up samba and other network services.