When I tried to create tar file for existing service '\тест' ("test" in Russian), I got NT_STATUS_OBJECT_NAME_INVALID error. There is command which I used: $ smbclient -s smb.conf //JOKER/pub -A ~/credfile -Tc /tmp/test.tar '\тест' Domain=[TEST] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] NT_STATUS_OBJECT_NAME_INVALID listing \QP5QQ tar: dumped 0 files and directories Total bytes written: 0 My locale is set to "ru_RU.utf8" and smb.conf file contains only two lines: display charset = UTF8 unix charset = UTF8
It looks like smbclient parses tar command parameters first and only then reads smb.conf file (see attachment). As result service name parsed as ASCII string and corrupted by unfixtarname() function.
Created attachment 1732 [details] smbclient error log Processing an item, \тест [...] Processed an item, QP5QQ Cliplist is: \тест lp_load: refreshing parameters Initialising global parameters params.c:pm_process() - Processing configuration file "smb.conf" doing parameter display charset = UTF8 doing parameter unix charset = UTF8
Created attachment 1733 [details] Quick hack to default to UTF-8 instead of ASCII I made quick hack to default to UTF-8 instead of ASCII. Why default to UTF-8? 1. UTF-8 is backwards compatible with ASCII 2. I'm using UTF-8 :)
this is no problem any more these days, sorry for the long lack of feedback.