WindowsProtocolTestSuites : STATUS_LOGON_FAILURE

[shloro]

WindowsProtocolTestSuites : STATUS_LOGON_FAILURE

[Dingshouqing]

Hi shloro,

Thanks for contacting us, Could you provide a network capture for both NTLM and Kerberos to us for further investigation?

From the exception log it seems caused by your driver machine cannot resolve the Ip address by SMB server name or Domain name, you can try if you could ping your SUT and domain by machine name or NetBios name.

We did a bug fix for both NTLM and Kerberos recently, so you can try if the issue still exists after using our latest code.
you can find how to build our TestSuite code from our Github portal https://github.com/microsoft/WindowsProtocolTestSuites

Best Regards,
Windows Protocol Test Suites Development Team

[shloro]

Hi,
So I did some fixes on DNS record side.
Now I get error STATUS_LOGON_FAILURE, due to GSS error (frame #306, 13:18:26.273892).
TCP Dump attached.

• ignore dialect SMB 2.02 errors, we currently support only SMB2.1.
  vast_proto_test_suite_logon_failure_mykola.pcapng.zip

[Dingshouqing]

Hi shloro,

Thanks for sending the network capture!

“STATUS_LOGON_FAILURE” may be caused by a different reason. Could you help try below:

1. Please check if the time difference between client, server, and domain (>5 minutes)
2. Try if NTLM SSP can work, if not could you send us the network capture?
3. I have attached a private build that will use windows native SSP to do authentication, please also have a try and send us the network capture whether it can work or not.

Could you also give us more details about your test environment? Such as OS type, version, network structure.
We may need your test credential to parse some of the content in Kerberos token from the capture file, However, Let’s try with the above steps first.

FileServerPrivateBuild

Best Regards,
Windows Protocol Test Suites Development Team

[Dingshouqing]

@shloro, have you tried the above steps, and does this issue still exists?

[lumengyanhelen]

Since this thread has been inactive for a long time, we will close for now. Feel free to reactivate the issue if you still have any questions.

Best Regards,
Windows Protocol Test Suites Development Team