(Seems to be closely related to closed bug #1606) Server: Debian GNU/Linux 3.1 (testing) Clients: DOS (Lanman 2.1) We are using bootdisks (www.netbootdisk.com) to access a samba share for ghost imaging, for this we use a mix of MS-DOS 6.22 and bootdisks created in Windows XP (reported dos version Windows Millenium [Version 4.90.3000]). This all worked great until we upgraded from samba 3.0.10 to 3.0.14a, after this the MS-DOS 6.22 based disks couldnt execute any binaries or scripts anymore ('Bad command or file name'), whereas the disks built with Windows XP dos continued to work normally.
Created attachment 1204 [details] smb.conf The used smb.conf
(In reply to comment #0) > (Seems to be closely related to closed bug #1606) > > Server: Debian GNU/Linux 3.1 (testing) > Clients: DOS (Lanman 2.1) > > We are using bootdisks (www.netbootdisk.com) to access a samba share for ghost > imaging, for this we use a mix of MS-DOS 6.22 and bootdisks created in Windows > XP (reported dos version Windows Millenium [Version 4.90.3000]). > > This all worked great until we upgraded from samba 3.0.10 to 3.0.14a, after > this the MS-DOS 6.22 based disks couldnt execute any binaries or scripts > anymore ('Bad command or file name'), whereas the disks built with Windows XP > dos continued to work normally.
... what I wanted to say: I see this too with DOS 6.22 disks but not with Windows 95 disks.
Test this against the 3.0.20rc2 code. I think this is fixed. Jeremy.
closing.