I have a Samba server installed on FreeBSD (latest releases of both), and an old Windows application that uses the 8.3 short names in directory listings. I have the problem that the 8.3 file names returned are quite strange, and hardly resemble the originals. Some examples: "Hy Energy" -> "HIl81N~K" "5700_files" -> "5s2IOA~P" "KWJ ENG" -> "KA7YD3_N" "CPS-100" -> "" (blank) I used an Ethereal trace to verify that these are indeed the short file names coming from the server (in the Trans2 FindFirst2 response). This seems to affect both directory names and files. I have no problems with long file names. The files were originally created on a Windows PC, and were then copied to my FreeBSD machine by putting them onto an external USB hard drive, and then mounting this hard drive on the FreeBSD box. Any idea why the 8.3 names are so weird? Is this typical for Samba now? I can open the files no problem, but it will be a pain for my engineer to figure out which file is which. Thanks, Dave
Dave Abouav pisze:> I have a Samba server installed on FreeBSD (latest releases of both), > and an old Windows application that uses the 8.3 short names in > directory listings. I have the problem that the 8.3 file names > returned are quite strange, and hardly resemble the originals. Some > examples: > > "Hy Energy" -> "HIl81N~K" > "5700_files" -> "5s2IOA~P" > "KWJ ENG" -> "KA7YD3_N" > "CPS-100" -> "" (blank) > > I used an Ethereal trace to verify that these are indeed the short > file names coming from the server (in the Trans2 FindFirst2 response). > This seems to affect both directory names and files. I have no > problems with long file names. > > The files were originally created on a Windows PC, and were then > copied to my FreeBSD machine by putting them onto an external USB hard > drive, and then mounting this hard drive on the FreeBSD box. > > Any idea why the 8.3 names are so weird? Is this typical for Samba > now? I can open the files no problem, but it will be a pain for my > engineer to figure out which file is which. > > Thanks, > Dave > >HI. I have exactly the same problem, but i use samba with linux Any infos are welcome ! Irens.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dave Abouav wrote:> Any idea why the 8.3 names are so weird? Is this typical > for Samba now?It is by design. You might want to look at the mangling method option in smb.conf(5). cheers, jerry ====================================================================Samba ------- http://www.samba.org Centeris ----------- http://www.centeris.com "What man is a man who does not make the world better?" --Balian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5DJuIR7qMdg1EfYRAjcvAJ9eFe7GjECNu0nkP0uyx5wTcB6jAACdHtHT bzlkq3aob5m464Z1Vtd4Dkk=keNJ -----END PGP SIGNATURE-----
Gerald (Jerry) Carter napisa?(a):> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Dave Abouav wrote: > > >> Any idea why the 8.3 names are so weird? Is this typical >> for Samba now? >> > > It is by design. You might want to look at the > mangling method option in smb.conf(5). > >so to use: magling method = hash instead mangling method = hash2 (default for samba 3.x) ?? cheers, Irens> > > > cheers, jerry > ====================================================================> Samba ------- http://www.samba.org > Centeris ----------- http://www.centeris.com > "What man is a man who does not make the world better?" --Balian > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFF5DJuIR7qMdg1EfYRAjcvAJ9eFe7GjECNu0nkP0uyx5wTcB6jAACdHtHT > bzlkq3aob5m464Z1Vtd4Dkk> =keNJ > -----END PGP SIGNATURE----- >