bug in smbmount and smbclient with 8bit filenames

[Jason Haar]

I've shoved this out a couple of times in comp.protocols.smb with not a peep
- hopefully someone here will know if this is a bug or not...

It appears that files on our NT servers that have 8bit chars in the
filenames are causing "No such file or directory" errors when listed via
either smbmount'ed partitions or smbclient.

If I view a directory with the offending files under NT or Win98, the entire
contents shows up fine (with the cr*p chars in them - I must admit they
actually look like escape keys accidently shoved in there by the user who
created it), but if I mount it as the same domain user under Linux, then
these 8bit files give the "no such file" error to /bin/ls etc.

Similarly it's quite weird seeing (smbclient):

smb: \temp\SC TechNotes\> mget Handheld*.*
Get file Handheldw?screens.eps? y
ERRDOS - 123 opening remote file \temp\SC TechNotes\Handheldw?screens.eps
smb: \temp\SC TechNotes\> 

Is this a bug?


Samba 2.0.7 _and_ samba-tng (2 weeks old) under Redhat Linux 6.2

-- 
Cheers

Jason Haar

Unix/Network Specialist, Trimble NZ
Phone: +64 3 9635 377 Fax: +64 3 9635 417