NT status/error codes instead of DOS error codes - bug 3.0.0

Michael B Allen mba2000 at ioplex.com
Mon Dec 1 20:09:32 GMT 2003


>> 1) With NT 4.0, a redundant negotiate with Flags2 NTSTATUS32 on returns
>> with Flags2 NTSTATUS32 on but with a dos errorcode ERRSVR/ERRerror
>> (which
>> is what you would get had DOS error codes been requested).
>
> What do you mean by a "redundant negotiate"?  A second NegProt on the same
> connection?  Curious...  I didn't know that you could get away with doing
> that.

Of course you can. *Why* you would want to I don't know.

>
>> 2) With NT 4.0, with an STATUS_DFS_PATH_NOT_COVERED condition, if DOS
>> error codes were negotiated, an ERRSRV/ERRreserved is returned which
>> near
>> as I can tell works just fine for triggering DFS referrals from a wide
>> variety of operations.
>
> Urq.  I don't see ERRreserved in the list at the back of the SNIA doc.
> What number is it?

Oh, maybe I got the "reserved" from Ethereal. The specific error code is
ERRSRV/3.

Mike

-- 
A program should be written to  model the concepts of the task it
performs rather than the physical world or a process because this
maximizes the  potential for it  to be applied  to tasks that are
conceptually similar and, more  important, to tasks that have not
yet been conceived.



More information about the samba-technical mailing list