File name mangling issue??? - SMB
This is a discussion on File name mangling issue??? - SMB ; First, I'm running Samba 3.0.5 on Fedora 2 and all my Windows clients
are on XP Pro SP2.
I do have some XP users that use some old DOS-based programs (i.e.
KEDIT) in an XP DOS window. Because of their ...
-
File name mangling issue???
First, I'm running Samba 3.0.5 on Fedora 2 and all my Windows clients
are on XP Pro SP2.
I do have some XP users that use some old DOS-based programs (i.e.
KEDIT) in an XP DOS window. Because of their antiquity, these programs
do some bizzare things with long filenames. For instance, lets say a
user is currently in:
F:\MERCERDELTA
where F points to a share on the Samba server. They then open KEDIT
(nice DOS-based text editor), edit some files, and then exit KEDIT,
their prompt now reads:
F:\M2MMAW~N >
This came as a surprise to me, as I expected it should read "MERCER~1"
or something similar. Furthermore, doing a DIR /X from a dos window
shows lots of these strange short filename maps (i.e. "WestSouth"
becomes "W69O8V~N").
This problem only occurs on the Samba shares. Is this the correct
behavior of Samba? Should it be mapping names like that? Is this a
Samba problem at all, or do my clients need some tweaking? The real
problem here is that these folks have to work with these short
filenames sometimes and they're unreadable. I need to find a way to
work around this issue.
Thanks!
-
Re: File name mangling issue???
RTASURVEY wrote:
> First, I'm running Samba 3.0.5 on Fedora 2 and all my Windows clients
> are on XP Pro SP2.
>
> I do have some XP users that use some old DOS-based programs (i.e.
> KEDIT) in an XP DOS window. Because of their antiquity, these programs
> do some bizzare things with long filenames. For instance, lets say a
> user is currently in:
>
> F:\MERCERDELTA
>
> where F points to a share on the Samba server. They then open KEDIT
> (nice DOS-based text editor), edit some files, and then exit KEDIT,
> their prompt now reads:
>
> F:\M2MMAW~N >
>
> This came as a surprise to me, as I expected it should read "MERCER~1"
> or something similar. Furthermore, doing a DIR /X from a dos window
> shows lots of these strange short filename maps (i.e. "WestSouth"
> becomes "W69O8V~N").
>
The default hash method has changed somehow along the way, due to
performance problems as i think. You may use the old one (mangling method =
hash) or you may change the "mangle prefix" to somewhat nearer 5 while
still using "hash2" by adding a "mangle prefix = 5" to smb.conf.
Beware, some of your applications which store short-name paths in the
backyard or registry, may break either way forcing a reinstall.
--
Longhorn error#4711: TCPA / NGSCP VIOLATION: Microsoft optical mouse
detected penguin patterns on mousepad. Partition scan in progress
*to*remove*offending*incompatible*products.**React ivate*MS*software.
Linux woodpecker.homnet.at 2.6.11-mm1[LinuxCounter#295241,ICQ#4918962]
-
Re: File name mangling issue???
Thanks for the response. I wasn't aware of the "mangle prefix" option.
This will work with the "hash2" algorithm, or should I switch to
"hash"? Will the mangled names update automatically or will I have to
recreate the files & directories?
Thanks again for the info. This one really came as a suprise!