Win2000 joining the domain for Samba 2.1.0 prealpha
Matt Chapman
matty at cifs.org
Mon Nov 15 15:21:52 GMT 1999
On Tue, Nov 16, 1999 at 01:48:54AM +1100, Richard Sharpe wrote:
>
> Hmmm, seems like it needs something that calls:
>
> smb_io_rpc_hdr
> smb_io_rpc_hdr_resp
>
> plus adds Status = 0x1c010002
> Reserved = 0x00000000
Yep. Most of the header is common between the response and fault PDUs,
except the fault PDU adds the above two fields. The trick is finding
a decent place to implement this in Samba, and working out what error code
to report. In this case:
/* bad operation number in call: */
const long nca_s_op_rng_error = 0x1C010002;
For the record, some other ones which might be useful:
const long nca_s_proto_error = 0x1C01000B;
const long nca_s_fault_string_too_long = 0x1C010015;
const long nca_s_fault_invalid_tag = 0x1C000006;
const long nca_s_fault_invalid_bound = 0x1C000007;
const long nca_s_rpc_version_mismatch = 0x1C000008;
const long nca_s_fault_remote_no_memory = 0x1C00001B;
const long nca_s_fault_unsupported_authn_level = 0x1C00001D;
And the generic cases:
const long nca_s_unspec_reject = 0x1C000009;
const long nca_s_fault_unspec = 0x1C000012;
In my experience these are all mapped fairly cleanly to error codes on the
Windows side, so there should be no problem using them.
Matt
--
Matthew "Austin" Chapman
SysAdmin, Developer, Samba Team Member
More information about the samba-ntdom
mailing list