Jim Myers wrote: > > Andrew, you mentioned that Samba should produce the same error codes > as a Windows remote share. > Here's an interesting case: The test below runs correctly on native > NTFS, but fails as shown below with a remote Win2K share. > Samba produces the same error code as the remote case which means it > fails IFSTEST as well. > > So it appears even Microsoft doesn't produce identical results with > local and remote NTFS disks/shares.
It's probably a case of the leading slash being eaten by the protocol - we probably never see it at the server. > +++Microsoft (R) Installable File System Test for Windows NT/2000+++ > +++Test SW Build 0007 Init Wednesday July 31, 2002 17:09:31+++ > > Test :FileRelativePathCreationTest > Group :OpenCreateGeneral > File :g:\ifstest\code\opcreatg\frelpath.c > Line :500 > Status :24 (IFSTEST_TEST_NTAPI_FAILURE_CODE) > LastNtStatus :C000003B STATUS_OBJECT_PATH_SYNTAX_BAD > ExpectedNtStatus :C000000D STATUS_INVALID_PARAMETER > Description : > An attempt was made at a relative file creation. This operation > is identical to a previous relative file creation, execept > here the filename is specified with a leading slath. This > is illegal and should return an invalid parameter status. This looks like a *very* intersting tool. Particulary with the NTSTATUS codes displayed etc. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
