Klaus Troeger
2000-Jun-30 10:25 UTC
samba 2.0.7: option mangled names = no will chrash nt client !
HTML attachment scrubbed and removed -------------- next part -------------- A non-text attachment was scrubbed... Name: klaus.troeger.vcf Type: text/x-vcard Size: 331 bytes Desc: Card for Klaus Troeger Url : http://lists.samba.org/archive/samba/attachments/20000630/dedb54e2/klaus.troeger.vcf
Andrew Langton
2000-Jun-30 16:55 UTC
samba 2.0.7: option mangled names = no will chrash nt client !
We have had a similar problem - in our case it was files with / in the file name - they were created by Macs before we migrated to PCs. The NT systems didn't crash, but they couldn't open the files at all. The only way we found around the problem was to rename the files from the UNIX end. -----Original Message----- From: Klaus Troeger [mailto:klaus.troeger@de.origin-it.com] Sent: Friday, June 30, 2000 3:29 AM To: Multiple recipients of list SAMBA Subject: samba 2.0.7: option mangled names = no will chrash nt client ! Hello, our customers have directory names with several : in the names (created on unix). These directory's are shown, for example: test:test is shown as testt~# If i switch off mangling on the samba server, i could see the directory correctly, could go into it, could also see the file (even with :) and after 5 seconds the nt client crashes with blue screen. Test on on nt with service pack 3 and on one with service pack 5 (different machines) Our samba server is a Solaris 2.6 machine with 2.0.7 Some clues Klaus -- +--------------------------------------------+-----------------------------+ | Klaus Troeger, ORIGIN IT Deutschland GmbH | Phone : +49 911 9702 1355 | | Dept. CCC-N/SM / UNIX-System-Manager | Fax : +49 911 9702 1171 | | EMail: klaus.troeger@de.origin-it.com | Mobile : +49 170 5316150 | | Privat: klaus@linuxstar.de +-----------------------------+ | URL: http://www.linuxstar.de <http://www.linuxstar.de> | ORIGIN - now member of DELUG| +--------------------------------------------+-----------------------------+ | Remark: Optional support of LINUX is possible - call me !!! | +--------------------------------------------------------------------------+
Andrew Langton
2000-Jul-05 20:36 UTC
samba 2.0.7: option mangled names = no will chrash nt client !
We used to use a product called TAS on our Solaris box - it was basically Samba and Netatalk combined in one package. Beast of a thing - steer clear if you can is my recommendation. Anyway, we got rid of all the Macs, so we replaced it with Samba. The files would list on UNIX as :2f instead of /, but on a Mac they'd come through as a /. There were plenty of other characters the PC didn't like too - : \, etc. -----Original Message----- From: Peter Samuelson [mailto:peter@cadcamlab.org] Sent: Sunday, July 02, 2000 3:45 AM To: klaus.troeger@de.origin-it.com; andrewl@babcockbrown.com Cc: Multiple recipients of list SAMBA Subject: Re: samba 2.0.7: option mangled names = no will chrash nt client ! [Klaus Troeger <klaus.troeger@de.origin-it.com>]> > <!doctype html public "-//w3c//dtd html 4.0 transitional//en">*Please* don't do that, lest I reply in nroff. (:> > our customers have directory names with several : in the names > > (created on unix).[...]> > If i switch off mangling on the samba server, i could see the > > directory correctly, could go into it, could also see the file (even > > with :) and after 5 seconds the nt client crashes with blue screen. > > Test on on nt with service pack 3 and on one with service pack 5Sorry, but I happen to find that really funny. Here's a good summary of that class of bug. Luke Leighton wrote this on samba-ntdom a couple months ago: | *sigh*. no, it's a client-side bug. no client-side bugs have been | fixed in nt4. | | it's not considered worthwhile, by microsoft. | | after all, what would you be doing putting third party servers on | your network? [Andrew Langton <andrewl@babcockbrown.com>]> We have had a similar problem - in our case it was files with / in > the file name - they were created by Macs before we migrated to PCs. > The NT systems didn't crash, but they couldn't open the files at all.Whoa there. How on earth did you get those files onto the Unix system in the first place? '/' is one of the two illegal characters in Unix filenames (the other being '\0'). Peter