Tridge, If possible, could you please tell us the error codes you are seeing for unsupported levels, which are not STATUS_INVALID_INFO_CLASS ? Network trace for each unsupported setInfo/getInfo level will be ideal.
Thanks ---------------------------------------------------------- Hongwei Sun - Support Escalation Engineer DSC Protocol Team, Microsoft [EMAIL PROTECTED] Tel: 469-7757027 x 57027 ----------------------------------------------------------- -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2008 9:06 PM To: Interoperability Documentation Help Cc: [EMAIL PROTECTED] Subject: CAR - missing SMB2 GetFileInfo levels Hi, MS-SMB2 section 2.2.37 says that these are the only 19 levels for getfileinfo: FileBasicInformation FileStandardInformation FileInternalInformation FileEaInformation FileAccessInformation FilePositionInformation FileFullEaInformation FileModeInformation FileAlignmentInformation FileAllInformation FileAlternateNameInformation FileStreamInformation FilePipeInformation FilePipeLocalInformation FilePipeRemoteInformation FileCompressionInformation FileQuotaInformation FileNetworkOpenInformation FileAttributeTagInformation Section 3.3.5.20.1 says that any unsupported level must respond with STATUS_INVALID_INFO_CLASS A scanner in our testsuite (the SMB2-SCANGETINFO test) shows that Vista responds to a total of 31 levels with some other error code, indicating that the level is available. The levels our scanner finds are: 4, 5, 6, 7, 8, 9, 14, 15, 16, 17, 18, 21, 22, 23, 24, 25, 26, 28, 29, 32, 33, 34, 35, 41, 43, 44, 45, 46, 47, 48, 49 Can you please document the missing levels? The scan also shows that Vista responds to 9 getfsinfo levels: 1, 3, 4, 5, 6, 7, 8, 9, 10 but the doc only lists 6 levels. Can you please document the extra 3 levels? Cheers, Tridge _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
