samba - Sep 2003 - Problem with a dos program running from a samba share.

I'm having troubles with a DOS program running from a samba 3 share.
When I close the program it tells:

General failure reading drive F
Abort, Retry, Fail?

(F is a network drive mapped on the samba share)

I have increased smbd debug level and after retrying I have this in the log:

[2003/09/28 11:19:56, 3] lib/util.c:unix_clean_name(580)
  unix_clean_name [/TTN02/RESHET1/DOJ]
[2003/09/28 11:19:56, 3] lib/util.c:unix_clean_name(580)
  unix_clean_name [ttn02/reshet1/DOJ]
[2003/09/28 11:19:56, 3] smbd/error.c:error_packet(94)
  error string = Not a directory
[2003/09/28 11:19:56, 3] smbd/error.c:error_packet(129)
  error packet at smbd/reply.c(443) cmd=16 (SMBchkpth) eclass=1 ecode=267

(There is more but I thought that this is what relevant).

The client machine is win98, the server is Mandrake 9.1,
the file ttn02/reshet/DOJ exist and the win98 user has read and write 
permission for it.

Does anyone have an idea?

On Sun, Sep 28, 2003 at 11:50:05AM +0300, Amir Hardon
wrote:
> I'm having troubles with a DOS program running from a samba 3 share.
> When I close the program it tells:
> 
> General failure reading drive F
> Abort, Retry, Fail?
> 
> (F is a network drive mapped on the samba share)
> 
> I have increased smbd debug level and after retrying I have this in the
log:
> 
> [2003/09/28 11:19:56, 3] lib/util.c:unix_clean_name(580)
>   unix_clean_name [/TTN02/RESHET1/DOJ]
> [2003/09/28 11:19:56, 3] lib/util.c:unix_clean_name(580)
>   unix_clean_name [ttn02/reshet1/DOJ]
> [2003/09/28 11:19:56, 3] smbd/error.c:error_packet(94)
>   error string = Not a directory
> [2003/09/28 11:19:56, 3] smbd/error.c:error_packet(129)
>   error packet at smbd/reply.c(443) cmd=16 (SMBchkpth) eclass=1 ecode=267
> 
> (There is more but I thought that this is what relevant).
> 
> The client machine is win98, the server is Mandrake 9.1,
> the file ttn02/reshet/DOJ exist and the win98 user has read and write 
> permission for it.
> 
> Does anyone have an idea?
Probably we are returning an incorrect error code in a DOS case.
Can you send me the DOS program and the steps needed to reproduce
the bug ? I should be able to fix it for 3.0.1 if so.

Thanks,

	Jeremy.