3.2.4 Message Processing Events and Sequencing Rules
When a method completes, the values returned by RPC MUST be returned unmodified to the upper layer.
The client MUST ignore errors returned from the RPC server and MUST notify the higher-layer software of the error received in the higher layer. Otherwise, no special message processing is required on the client beyond the processing required in the underlying RPC protocol.
This protocol SHOULD indicate to the RPC runtime that it is to perform a strict NDR data consistency check at target level 6.0, as specified in [MS-RPCE] section 3.<145>
This interface includes the following methods.
Methods in RPC Opnum Order
|
Method |
Description |
|---|---|
|
A callback method called by the server in response to a client call to S_DSQMSetMachineProperties. Through this method, the server provides a challenge that the client must sign to authenticate itself. Opnum: 0 |
|
|
A callback method called by the server in response to a client call to S_DSQMGetObjectSecurity. Through this method, the server provides a challenge that the client must sign to authenticate itself. Opnum: 1 |
|
|
A callback method called by the server in response to a client call to S_DSValidateServer. This method is called for each leg of a mutual authentication security context negotiation. Opnum: 2 |
All methods MUST NOT throw exceptions.