External File Systems: SMB Filenames Using Reserved Windows Characters Cause Corruptions
Posted by Aly Essa on 29 April 2019 08:06 AM

This initial report of this issue to the FileCatalyst Support team outlined that the filenames being transferred from a Samba location to a storage destination on Windows was corrupting filenames.

Upon further investigation, we found that the original filename contained reserved characters (in Windows) were not preserved when the listing is passed off from the SMB driver to our application(s).

For example, a file with Windows reserved characters in the filename like <>{[}]|^~_file770.pdf in a samba share in Linux would end up as _9H1AW~8.pdf


FileCatalyst Server v3.7.3
SMB Mounts


The solution to this issue was found on a StackExchange Article.

Modify the Samba configuration file as per the solution posted and this will keep the original filename throughout the transfer. Before you perform any modifications please make a copy of the smb.conf file.

If you require any other information please submit a ticket to the Support Team and an engineer will be there to assist.