[cifs-protocol] [EXTERNAL] [MS-APDS] NETLOGON_TICKET_LOGON_INFO message - TrackingID#2405210040011397

[Jeff McCashland (He/him)]

[DocHelp to BCC, support on CC, SR ID on Subject]

Hi Jo,

Thank you for your question. We have created SR 2405210040011397 to track this issue. One of our engineers will response and provide workspace information to upload your traces.


Best regards,
Jeff McCashland (He/him) | Senior Escalation Engineer | Microsoft Corporation

Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada)

Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300



________________________________
From: Jo Sutton <jsutton at samba.org>
Sent: Monday, May 20, 2024 9:49 PM
To: cifs-protocol at lists.samba.org <cifs-protocol at lists.samba.org>; Interoperability Documentation Help <dochelp at microsoft.com>
Subject: [EXTERNAL] [MS-APDS] NETLOGON_TICKET_LOGON_INFO message

[Some people who received this message don't often get email from jsutton at samba.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

Hi dochelp,

I’m trying to follow [MS-APDS] 2.2.2.1, “NETLOGON_TICKET_LOGON_INFO
Message”, in order to create a NETLOGON_TICKET_LOGON_INFO message that
will be accepted by Windows Server 2019. However, in my attempts so far,
all I’ve got is STATUS_INVALID_PARAMETER codes from NetrLogonSamLogonEx.

Although [MS-APDS] doesn’t mention it, I assume
NETLOGON_TICKET_LOGON_INFO should contain an unsigned 32‐bit MessageType
field, set to 0x00000026, that indicates the message is a
NETLOGON_TICKET_LOGON_INFO message. Other than that, I’m not sure what
I’m doing wrong. Are the ticket fields arrays, are depicted in the
diagram, or pointers, as claimed in the documentation?

I can provide traces showing the problem if you would like.

Cheers,
Jo (she/her)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20240521/6bc7266f/attachment.htm>