Good morning Andrew. Thank you for your question! I have created a new case for
this (info below); one of my colleagues will take ownership of this and contact
you soon.
SRX080903600015 [MS-APDS] 2.2.2.1 valid Kerberos message types
Regards,
Bill Wesse
MCSE / Escalation Engineer, US-CSS DSC PRO
Good morning Andrew. Thank you for your question! I have created a new case for
this (info below); one of my colleagues will take ownership of this and contact
you soon.
SRX080903600016 [MS-ADTS] 3.1.1.4.5.16 kvno for trusted domain entities
Regards,
Bill Wesse
MCSE / Escalation Engineer, US-C
Andrew,
I have completed my research on LsarSetSecret. The documentation provides
information when you have an exception case such as when one updates
EncryptedCurrentValue. I have included a scenario that might help clarify the
behavior:
Scenario:
I have a secret object with old and new sec
Andrew:
Thanks for your suggestion. We will add the information about
AuthenticationOptions to [MS-KILE] and then create a cross reference in
[MS-LSAD]. We will also keep the names consistent among documents ([MS-KILE]
and [MS-LSAD]) because they are basically for the same purpose.
On Wed, 2008-09-03 at 12:38 -0700, Richard Guthrie wrote:
> Andrew,
>
> I have completed my research on LsarSetSecret. The documentation
> provides information when you have an exception case such as when one
> updates EncryptedCurrentValue. I have included a scenario that might
> help clarify t
Stefan,
The traces you sent seems to show a correct security context negotiation but
something is failing when we go to use that context which is why we see
RPC_NT_SEC_PKG_ERROR. I would like to start with getting some more detailed
error info from the windows machine by doing the following:
