mkdir from Windows 2000

[Jeremy Allison]

Tine Smukavec wrote:
> 
> Hi all,
> 
> we found out something interesting when trying to create directory along
> with unexisting intermediate ones from Windows 2000 client.
> We are using Samba 2.0.7 on
> "SunOS 5.6 Generic_105181-17 sun4u sparc SUNW,Ultra-4".
> 
> Command: cmd /x /E:ON mkdir \\<samba server>\<share name>\a\b\c
>          (Neither of directories in the path exists.)
> 
> Reply from NT client:
> ---------------------
> OK.
> 
> Reply from Windows 2000 client:
> -------------------------------
> "The system cannot find the file specified"
> 
> Important debug entries:
> ========================
> - in both cases we got: Selected protocol NT LM 0.12
> 
> Command sequence on Windows 2000:
> ---------------------------------
> - SMBntcreateX(/a/b/c)
>   Reply:   open_directory: unable to create a/b/c.
>            Error was No such file or directory
>            error string = No such file or directory
> 
> - NOTHING ELSE!!!
> 
> Command sequence on NT:
> -----------------------
> - SMBmkdir(/a/b/c)
>   Reply: error string = No such file or directory
> 
> - SMBmkdir(/a)
>   Reply: New file a
> 
> - SMBmkdir(/a/b)
>   Reply: New file b
> 
> - SMBmkdir(/a/b/c)
>   Reply: New file c
> 
> - OPERATION SUCCEEDED!!!
> 
> Does anybody know where such a difference come from. Is this a bug in
> Windows 2000 or should open_directory() function behaves differently,
> i.e. should create intermediate directories if they do not exist?

Can you do the same operation against an NT server and
get a packet trace please. My guess is that it will be
the specific error code returned on the first mkdir that
triggers the mkdir heirarchy calls.

It would help to know what that was...

Thanks,

	Jeremy Allison,
	Samba Team.
-- 
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------