From: adcromitus <adcromitus-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Accented characters not working with CIFS (but ok with smbclient)
Date: Mon, 29 Sep 2014 23:50:10 +0100 [thread overview]
Message-ID: <5429E222.4090101@gmail.com> (raw)
In-Reply-To: <5427C7A6.8080901-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
On 28/09/2014 09:32, steve wrote:
> On 28/09/14 01:23, adcromitus wrote:
>> Hello again,
>>
>> Sorry for the long time to reply.
>>
>> I've been going around on how to do this. I set up Wireshark and saw
>> what the server was transmitting. However I'm not really sure about what
>> I should send here.
>>
>> Anyway I did a "ls" on a dir with a file named "Coleção", and wireshar
>> captured "cole \247 \243o". I send a few frames from tcpdump where that
>> happens.
>>
>> How can I see if my distro defaults to UTF-8 on the client?
>>
>> I'm using:
>> Linux kernel 3.2.0-4-amd64
>> (Debian Wheezy)
>> mount.cifs version: 5.5
>>
>>
>> Thanks in advance.
>>
>>
>>
>>
>> On 22/09/2014 04:28, Steve French wrote:
>>> This seems strange because modern Linux distributions should map UCS-2
>>> (16 bit Unicode characters which cifs servers like Windows and Samba
>>> send over the wire) fine to UTF-8 which is the typical default one for
>>> local.
>>>
>>> Does you distro not default to UTF-8 on the client?
>>>
>>> Would be helpful to see a wire trace (ethereal or tcpdump) and make
>>> sure the server is sending UCS-2 (Unicode) on the wire. See
>>> https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting
>>>
>>> On Sat, Sep 20, 2014 at 5:44 PM, adcromitus <adcromitus-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>> wrote:
>>>> Hy,
>>>>
>>>> I'm not sure of what can be relevant so I'll tell the whole story.
>>>>
>>>> I have a router (that I got from my ISP) which allows the connection
>>>> of a
>>>> pen/HDD by USB. That pen is shared on the network as a Windows Share
>>>> folder.
>>>>
>>>> In Windows 7 I can see all the files name correctly, but when I mount
>>>> the
>>>> drive in Linux, with the command:
>>>>
>>>> mount -t cifs //<local share ip-address>/<shared-folder> --verbose -o
>>>> user=user,pass="",uid=1000,gid=1000
>>>>
>>>> (there is no password)
>>>>
>>>> All file names with special characters (like Çãõé...) have a question
>>>> mark
>>>> in place of the accented character and I can't open the file or
>>>> folder, as
>>>> any command responds the file doesn't exist. This happens in dolphin,
>>>> thunar
>>>> and in the command line with simple commands like cat.
>>>>
>>>> I tried adding the following option without success
>>>>
>>>> iocharset=utf-8
>>>> iocharset=utf-8,codepage=cp437
>>>> iocharset=utf-8,codepage=cp850
>>>> iocharset=iso8859-1
>>>>
>>>> This also happens if I access the share from my android device, so
>>>> I was
>>>> convinced it was a problem related to old firmware (from the router).
>>>>
>>>> However, recently I connected to the drive using smbclient and the
>>>> file
>>>> names appeared correctly. I would like to mount this share folder at
>>>> fstab,
>>>> and so smbclient is not a good solution.
>>>>
>>>> I'm using:
>>>> Linux kernel 3.2.0-4-amd64
>>>> (Debian Wheezy)
>>>> mount.cifs version: 5.5
>>>>
>>>> And I get this information from smbclient -L <local share ip address>:
>>>> (smbclient version 4.1.11-Debian)
>>>> Server=[Samba 2.2.12]
>>>>
>>>> So. Is there something else I can try?
>>>>
>>>> Thanks in advance.
> Hi
> Probably an old cifs-utils? We have 6.2 with Spanish:
> steve2@altet:~> ls
> aviñón
> barça
>
> HTH,
> Steve
Hy Steve,
So I used chroot to install the cifs-utils version from Debian next
release (cifs-utils v.6.4), and the result was the same as with my
current version.
Does the tcpdump helped in any way?
Thanks again.
>
>
>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe
>>>> linux-cifs" in
>>>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>>
>>
>
>
next prev parent reply other threads:[~2014-09-29 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 22:44 Accented characters not working with CIFS (but ok with smbclient) adcromitus
[not found] ` <541E0369.8070205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-22 3:28 ` Steve French
2014-09-27 23:23 ` adcromitus
[not found] ` <542746D9.7090007-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-28 8:32 ` steve
[not found] ` <5427C7A6.8080901-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
2014-09-29 22:50 ` adcromitus [this message]
[not found] ` <5429E222.4090101-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-30 1:32 ` Steve French
[not found] ` <CAH2r5mtwPK8_HGtxnCq5kOs-4ZaaNNR5ame=GNXLUkCtzGq+Dg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-30 1:33 ` Steve French
[not found] ` <CAH2r5msdOGbYPEW0+wNp4_qxQR5L1tHZvod2c4v1hYxjpme+Gg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-30 2:40 ` Steve French
[not found] ` <CAH2r5mt1EVo26=N8tVRgqCDGGUpJrUDpajF4T+g3weJQcYwFFw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-30 18:38 ` adcromitus
[not found] ` <542AF89C.3050707-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-10-05 6:08 ` Shirish Pargaonkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5429E222.4090101@gmail.com \
--to=adcromitus-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox