使用SMB3而不是SMB2时收到SAMR STATUS_WRONG_PASSWORD [英] SAMR STATUS_WRONG_PASSWORD Received When Using SMB3 Instead of SMB2

问题描述

我们使用域控制器的SAMR命名管道将计算机添加到域中。

如果计算机已存在于我们使用SamrSetInformationUser2和UserInternal5InformationNew的域中。

此代码已成功使用多年。

最近我们添加了SMB3 （0x0300）连接到SAMR命名管道时SMB2_NEGOTIATE中支持的协议列表。

如果域控制器是Windows Server 2012，它将选择SMB3和  SamrSetInformationUser2 / UserInternal5InformationNew方法调用将失败并接收STATUS_WRONG_PASSWORD。在我们到达SamrSetInformationUser2 / UserInternal5InformationNew之前，其他SAMR方法调用成功。

总之，当传输是SMB2时，我们正在进行SAMR方法调用当运输是SMB3时失败。

当运输是SMB3时，任何关于为什么行为应该不同的想法将不胜感激。

Matt

解决方案

Hi Matt，

感谢您关于使用STATUS_WRONG_PASSWORD的SamrSetInformationUser2失败的请求。其中一个开放规范团队将尽快与您合作。

最好的问候，

Tom Jebo

Sr Escalation Engineer

Microsoft Open Specifications

Hi,

We use the SAMR named pipe of a domain controller to add a computer to a domain.

If the computer already exists in the domain we use SamrSetInformationUser2 with UserInternal5InformationNew.

This code has been used successfully for a number of years.

Recently we added SMB3 (0x0300) to the list of supported protocols in the SMB2_NEGOTIATE when connecting to the SAMR named pipe.

If the domain controller is Windows Server 2012 it will select SMB3 and the  SamrSetInformationUser2/UserInternal5InformationNew method call will fail and receive STATUS_WRONG_PASSWORD. Other SAMR method calls succeed before we get to SamrSetInformationUser2/UserInternal5InformationNew.

In summary, we're making a SAMR method call that succeeds when the transport is SMB2 and fails when the transport is SMB3.

Any thoughts about why the behaviour should be different when the transport is SMB3 would be greatly appreciated.

Matt

解决方案

Hi Matt,

Thank you for your request regarding SamrSetInformationUser2 failure with STATUS_WRONG_PASSWORD. One of the Open Specifications team will respond to begin working with you shortly.

Best regards,
Tom Jebo
Sr Escalation Engineer
Microsoft Open Specifications

这篇关于使用SMB3而不是SMB2时收到SAMR STATUS_WRONG_PASSWORD的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！