Samba not handling sharename folding to uppercase for some charsets?

[Richard Sharpe]

On Thu, Mar 11, 2010 at 4:02 PM, Richard Sharpe
<realrichardsharpe at gmail.com> wrote:
> Hi,
>
> We have just experienced something weird and I wanted to see if this
> is known or if there is a way around it.
>
> We were testing share names containing non-ASCII chars (French u-grave
> or something). We could see the correct characters being sent back in
> a NetShareEnum, and the Windows Client first tried to get an MSDFS
> referral, which we refused (NOT IMPLEMENTED). Then the client tried a
> TreeConnect&X with the uppercase version of the share name, which we
> refused because it did not match what we knew.
>
> If we use the upper-case version of the share name, all is fine,
> although the Mac SMB client does not case fold share names before
> sending them over, so this is hardly a solution.
>
> I have tracked the problem down to strlower_m in
> source3/lib/util_str.c which explicitly says that it is optimized for
> ASCII. In making a connection Samba 3 converts the share name to
> 'lower case' using strlower_m and it seems that the possibility that
> characters above 128 might need conversion.
>
> Has anyone worked around this? (Of course, for character sets that do
> not have upper-case characters, this is not a problem :-)

Problem solved. We were not copying the files in
samba-<version>/codepages to the target.

-- 
Regards,
Richard Sharpe