[cifs-protocol] MS-PAR and MS-RPRN Issue with SPLCLIENT_INFO Bulid number rejection 
edgaro at microsoft.com
Thu Aug 23 21:27:34 UTC 2018
I will review this and follow-up soon.
From: Obaid Farooqi
Sent: Thursday, August 23, 2018 2:34 PM
To: Justin Stephenson <jstephen at redhat.com>
Cc: cifs-protocol at lists.samba.org; MSSolve Case Email <casemail at microsoft.com>
Subject: RE: MS-PAR and MS-RPRN Issue with SPLCLIENT_INFO Bulid number rejection 
Thanks for contacting Microsoft. I have created a case to track this issue. A member of The Open Specifications Team will be in touch soon.
Escalation Engineer | Microsoft
From: Justin Stephenson <jstephen at redhat.com<mailto:jstephen at redhat.com>>
Sent: Thursday, August 23, 2018 2:06 PM
To: Interoperability Documentation Help <dochelp at microsoft.com<mailto:dochelp at microsoft.com>>
Cc: cifs-protocol at lists.samba.org<mailto:cifs-protocol at lists.samba.org>
Subject: MS-PAR and MS-RPRN Issue with SPLCLIENT_INFO Bulid number rejection
I would like to ask for clarification on the rejection criteria used for the client information fields provided in the RpcAsyncOpenPrinter method, and specifically the dwBuildNum value.
Testing against Windows Server 2016 this RpcAsyncOpenPrinter method returns Access Denied when SPL_CLIENT_INFO buildnum value, as part of pClientInfo, is a value less than 6000(Windows Vista and Windows Server 2008). Higher advertised OS values greater than 6000 successfully open a printer handle. I have attached working and non-working packet captures taken for evidence of this with the build number used in the filename.
The following statement on MS-RPRN page 396/415 seems incorrect, or requires further clarification.
Windows does not use the following members: pUserName,
dwBuildNum, dwMajorVersion, dwMinorVersion, and wProcessorArchitecture.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cifs-protocol