> Hi everyone. I have noticed that error handling in smb and dcerpc seems > to fall over itself when there is an error value set in both the smb > packet and the dcerpc packet encapsulated within.
I.e., the cases where the SMB "error" just means "you didn't give me a big enough buffer to send back the RPC reply, so go read some more stuff from the named pipe in order get the rest of the reply"?