[bug] multibyte sharename becomes broken when default service is enable

Jeremy Allison jeremy at valinux.com
Tue Jun 12 18:24:25 GMT 2001

Samba-JP TAKAHASHI Motonobu wrote:
> Hello,
> There is a bug under multibyte environment with Windows NT/2000
> For example, if we connect to a share named [:8a:bf:8e:9a:8a:bf:8e:9a]
> on Samba with following smb.conf from Windows NT/2000, then a new
> share named [:8a:bf:8e:9a:8a:bf] is created for the client with using
> default service function.
> This does not depend on 'coding system' and this problem affects any
> Japanese share name (that mean multi byte share name).
> This is a very severe problem in Japan and we fixed this in our Samba
> 2.0.9 Japanese Edition.
> There are similar coding in dos_buffer2_to_str() and
> dos_buffer2_to_multistr(), we suspect there is another bug...

Patch looks good. I've applied it to HEAD and 2.2. I also
fixed the same errors in the other two functions. Please
check out the 2.2 CVS and see if it fixes the problem.

Thanks a *lot*,


Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.

More information about the samba-technical mailing list