search

cptaffe / plan9front

Automatically exported from code.google.com/p/plan9front
0 stars 0 forks source link

cifs can't mount UTF-8 shares with accents #165

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi.
I have a cifs share (among others) on a samba server that's named
Téléchargements (Downloads). That's the only one share that can't
be mounted by cifs. Here is the error message:

cifs: 192.168.0.1 T[]l[]chargements - can't connect to share, bad network name

(the [] here is a square character typical for utf8 mis-handling).

The /n/192.168.0.1/Shares file have the same utf8 problem for comments.

Original issue reported on code.google.com by nemeth.t...@gmail.com on 9 Jan 2013 at 3:37

GoogleCodeExporter commented 9 years ago 
can you make a wireshark capture? cifs supports unicode, but it might be that
that for some reason, the server didnt reply with CAP_UNICODE in the 
SMBnegotiate
rpc, then it will use ascii. maybe samba thinks we'r windows 98? you should 
contact the author directly. he's steve simon (steve AT quintile DOT net)

Original comment by cinap_le...@felloff.net on 11 Jan 2013 at 3:36

GoogleCodeExporter commented 9 years ago 
ah, it looks like the RAP protocol that (network neigbourhood) doesnt
use unicode, but we interpret the string as utf-8 but its probably in
some wired local encoding. (RAP is pretty old sub protocol)

Original comment by cinap_le...@felloff.net on 11 Jan 2013 at 3:42

GoogleCodeExporter commented 9 years ago 
ah, yes:

Localization: The Remote Administration Protocol does not support localization 
or 
internationalization. Text strings are encoded in ASCII and are always 
transmitted as octets the octets are outside the ASCII range, 0x20-0x7F, the 
characters are interpreted in the code page of the processing system.

Original comment by cinap_le...@felloff.net on 11 Jan 2013 at 3:48

GoogleCodeExporter commented 9 years ago 
whats the setting for "dos charset" in smb.conf? you could try this:

[global]
dos charset = UTF8

Original comment by cinap_le...@felloff.net on 11 Jan 2013 at 3:55

GoogleCodeExporter commented 9 years ago 
Yes, that was that. There wasn't any dos charset set. Now it works. Thanks !

Original comment by nemeth.t...@gmail.com on 11 Jan 2013 at 5:24

GoogleCodeExporter commented 9 years ago

Original comment by cinap_le...@felloff.net on 11 Jan 2013 at 11:59