As part of the Distributed Name Resolution algorithm, a DFS client may discover a knowledge inconsistency between the referral server (i.e., the server that handed out a referral), and the storage server (i.e., the server to which the client was redirected to by the referral server). When such an inconsistency is discovered, the DFS client optionally sends this SMB to the referral server, allowing the referral server to take corrective action.
| Client Request ================================== |
Description ================================== |
| WordCount | 15 |
| MaxParameterCount | 0 |
| SetupCount | 1 |
| Setup[0] | TRANS2_REPORT_DFS_INCONSISTENCY |
| Parameter Block Encoding ================================== |
Description ================================== |
| UNICODESTRING RequestFileName; | DFS Name of file for which referral was sought |
The data part of this request contains the referral element (Version 1 format only) believed to be in error. These are encoded as described in the TRANS2_GET_DFS_REFERRAL response. If the server returns success, the client can resubmit the TRANS2_GET_DFS_REFERRAL request to this server to get a new referral. It is not mandatory for the DFS knowledge to be automatically repaired – the client must be prepared to receive further errant referrals and must not wind up looping between this request and the TRANS2_GET_DFS_REFERRAL request.
Bit15 of Flags2 in the SMB header must be set, indicating this is a UNICODE request.