Files Not showing in Windows (foreign character in file name)

[ralphy]

Generally, I don't seem to have a problem with foreign characters displayed in filenames on Windows 10 with my SMB share, however for one specific set of files that show in FreeNAS as

Code:

drwxrws---  6 nobody  ray      9 Nov 15  2009 .svn
-rwxrwx---  1 nobody  ray    410 Feb 27  2009 0.8?W Thor 3_5-S2.ini
-rwxrwx---  1 nobody  ray   2326 Feb 27  2009 0.8?W Thor 3_5.ini
-rwxrwx---  1 nobody  ray   2575 Feb 27  2009 10.0?E EuroBird 10.ini
-rwxrwx---  1 nobody  ray   1298 Feb 27  2009 100.5?E Asiasat 2.ini
-rwxrwx---  1 nobody  ray    567 Feb 27  2009 101.0?W AMC 4.ini
-rwxrwx---  1 nobody  ray    341 Feb 27  2009 103.0?E Gorizont 31.ini
-rwxrwx---  1 nobody  ray    965 Feb 27  2009 103.0?W AMC 1.ini
-rwxrwx---  1 nobody  ray   1558 Feb 27  2009 105.0?W AMC 15.ini
-rwxrwx---  1 nobody  ray    237 Feb 27  2009 105.5?E Asiastar.ini
-rwxrwx---  1 nobody  ray    522 Feb 27  2009 107.3?W Anik F1.ini
-rwxrwx---  1 nobody  ray    246 Feb 27  2009 107.7?E Cakrawarta 1.ini

(from Mediaportal - TvEngine3/TVLibrary/TVServer.Base/TuningParameters)

With the ? I believe representing \#260 -

none of these files display in windows explorer or powershell "Normally" named files without special characters display in windows, as does the .svn folder

System Details
Versions FreeNAS-11.1-U7
Samba config
enable SMB1 yes
DOS Charset CP437
Unix Charset UTF-8

I was thinking of changing the DOS charset to UTF-8 but was concerned if this might cause some collateral damage from which I may not be able to recover (eg corrupting all the file names) And then this assumes that the bug https://redmine.ixsystems.com/issues/36833 has been fixed.

The problem actually became evident during rsync from FreeNAS to drive mounted in Windows, where all these files had protocol errors. On closer examination, I found that none of my windows machines connected to the SMB share would show these files.

So the fundamental question is, how can I see these files in Windows?
Can I change the DOS Charset at will, restart the service, and not have any collateral damage?
Is there another charset I should use?

 

[anodos]

You can change the DOS charset without problem. Just don't try to set it to an invalid one and you should be fine. The default in 11.3 is "dos charset = CP850", you can set it under Services->SMB as an auxiliary parameter. I don't believe that UTF-8 will ever be a valid DOS charset.

Code:

        if (strcasecmp(dos_charset, "UTF8") == 0 || strcasecmp(dos_charset, "UTF-8") == 0) {
                DEBUG(0,("ERROR: invalid DOS charset: 'dos charset' must not be UTF8, using (default value) CP850 inst
ead\n"));
                dos_charset = "CP850";
        }

Even if you managed to set it to UTF-8, it would be switched to CP850 behind the scenes.

 

[ralphy]

Thanks for the information and confirmation that the character set can be changed without problem.

Unfortunately, changing to CP850 didn't make these file visible in Windows. I wonder what could be causing Windows to not show these files that are visible in a FreeNAS SSH session.

 

[anodos]

Thanks for the information and confirmation that the character set can be changed without problem.

Unfortunately, changing to CP850 didn't make these file visible in Windows. I wonder what could be causing Windows to not show these files that are visible in a FreeNAS SSH session.

Post output of "testparm -s"