[Samba] Re: Unicode, ASCII, and Samba3 ...

I work at a university and when I upgraded from 2 to 3 only 1 user ever
complained, a professor in the foreign languages department. I started
to go down the road of conversion utilities and fiddling with code pages
and character sets. Then a potential easy solution occurred to me. We
have several Samba servers and the Unix boxes have a lot of disk in
common; I still had Samba 2 on some systems. On the UNIX side I moved
her files to where they where once again being shared by a Samba 2
server. As would be expected, from the client side, MS Windows, all the
file names where instantly intact again. I copied all her files down
from the Samba 2 server to local disk of a MS Windows box. From the MS
Windows box I then copied the files up to the Samba 3 server. Ta da. Now
they where on the Samba 3 server with file names intact.

Of course doing something like that may not be feasible in your case.
Good luck.

Tom Schaefer

On Wed, 26 Oct 2005 16:57:56 +0200
"Julien Ailhaud" <ailhaud.julien@agora.msa.fr> wrote:

>=20
>=20
> Problem summary :
> Files created with samba2 are now unreadable with samba3. I tested all
> possible settings in samba, rebuild it with libiconv, already posted here
> without reply ... without success.
>=20
> Today I analyzed the traffic between my station and the server, and I fou=
nd an
> interresting thing :
>=20
> With both version, filenames are transmited in ascii
> code 130 gives "=E9"
> code 135 gives "=E7"
> code 151 gives "=F9"
>=20
> But ...
>=20
> In packets exchanged by my Samba2 server and the stastion, the flag "uni=
code
> strings" is set to Zero ( --> ASCII )
>=20
> In packets exchanged by my Samba3 server and the stastion, the flag "uni=
code
> strings" is set to One ( --> UNICODE )
>=20
>=20
> I think that the problem is here, but I can't find how to change it, forc=
ing
> my Samba to use ASCII there.
>=20
> Any Idea ??
>=20
> Thanks.
>=20
>=20
> Ce message est prot=E9g=E9 par les r=E8gles relatives au secret des corre=
spondances. Il est donc =E9tabli =E0 destination exclusive de son destinata=
ire. Celui-ci peut donc contenir des informations confidentielles. La divul=
gation de ces informations est =E0 ce titre rigoureusement interdite. Si vo=
us avez re=E7u ce message par erreur, merci de le renvoyer =E0 l'exp=E9dite=
ur dont l'adresse e-mail figure ci-dessus et de d=E9truire le message ainsi=
que toute pi=E8ce jointe.
>=20
> This message is protected by the secrecy of correspondence rules. Therefo=
re, this message is intended solely for the attention of the addressee. Thi=
s message may contain privileged or confidential information, as such the d=
isclosure of these informations is strictly forbidden. If, by mistake, you =
have received this message, please return this message to the addressser wh=
ose e-mail address is written above and destroy this message and all files =
attached.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba