Tompkins, Michael
2016-Mar-10 16:41 UTC
[Samba] Russian(Cyrilic) names not working in smbclient 4.3.3
We are trying to use Russian(Cyrillic) names in smbclient 4.3.3 but that does not seem to work. Previously we had a problem in 4.0.7 which the location of upcase.dat changed from 3.6.5. In 4.3.3, we don't see it trying to access that file, nor do I believe that file needs to be delivered anymore. Is there a new way to configure the printer to use Russian user names ? Mike
Jeremy Allison
2016-Mar-10 17:00 UTC
[Samba] Russian(Cyrilic) names not working in smbclient 4.3.3
On Thu, Mar 10, 2016 at 04:41:46PM +0000, Tompkins, Michael wrote:> We are trying to use Russian(Cyrillic) names in smbclient 4.3.3 but that does not seem to work. Previously we had a problem in 4.0.7 which the location of upcase.dat changed from 3.6.5. In 4.3.3, we don't see it trying to access that file, nor do I believe that file needs to be delivered anymore. Is there a new way to configure the printer to use Russian user names ?More data please. What does "that does not seem to work" look like ? Logs etc. etc.
Tompkins, Michael
2016-Mar-10 21:23 UTC
[Samba] Russian(Cyrilic) names not working in smbclient 4.3.3
Thanks for the reply. Based on having a problem with 4.0.7, and I don't see upcase.dat anymore, I thought something changed in 4.3.3, which may have caused my issue. As it turns out, the password changed without me knowing it. It all works as it should. Russian is always a little tricky for me to debug! Sorry for crying wolf ... Regards, - Mike -----Original Message----- From: Jeremy Allison [mailto:jra at samba.org] Sent: Thursday, March 10, 2016 12:01 PM To: Tompkins, Michael Cc: samba at lists.samba.org; USA Xerox Samba Subject: Re: [Samba] Russian(Cyrilic) names not working in smbclient 4.3.3 On Thu, Mar 10, 2016 at 04:41:46PM +0000, Tompkins, Michael wrote:> We are trying to use Russian(Cyrillic) names in smbclient 4.3.3 but that does not seem to work. Previously we had a problem in 4.0.7 which the location of upcase.dat changed from 3.6.5. In 4.3.3, we don't see it trying to access that file, nor do I believe that file needs to be delivered anymore. Is there a new way to configure the printer to use Russian user names ?More data please. What does "that does not seem to work" look like ? Logs etc. etc.
Possibly Parallel Threads
- Samba 4.0.7 doesn't work with Russian credentials
- Samba 4.0.7 doesn't work with Russian credentials
- Building smbclient 4.3.3 as one executable without shared libraries
- smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
- cyrillic font in Transparent LanguageNow! Russian