问题描述
我正在将OEM SMB服务器升级到SMB2.1。我已经完成了SMB2.1多协议登录，并且启用了签名并且看起来工作正常，我正在宣传最大读/写/事务65536，现在我已经硬连线32作为积分
在所有回复中授予。 Windows10 NET USE命令继续按要求安装共享，但随后它立即通过线路发送和SMB2注销命令并打印出"系统错误53已发生"。当从Samba smbclient工具访问
或通过Linux文件管理器从正常共享安装访问
时，此相同的服务器代码工作良好，但是在尝试从mac OSX执行时不会这样，在重试和使用SMB1登录之前执行更多事务。有关为什么Win10会退出的任何想法，是否有
a方式从Win10客户端代码获得更多繁琐的诊断？
I'm upgrading an OEM SMB server to SMB2.1. I have the SMB2.1 multi protocol log in completed and signing is enabled and appears to be working correctly, I'm advertising max read/write/transactions of 65536 and for now I've hardwired 32 as the credits granted in all replies. The Windows10 NET USE command proceeds to mount the share as asked but then it immediately sends and SMB2 logoff command over the wire and prints "system error 53 has occurred". This same server code works well when accessed from the Samba smbclient tool or from a normal share mount through a Linux file manager, but not when attempted from mac OSX, which performs a lot more transactions before retrying and logging in with SMB1. Any thoughts on why Win10 would log out, and is there a way to get more chatty diagnostics from the Win10 client code perhaps ?
推荐答案
我发现您使用以下链接发布了相同的帖子。我想你会得到合适的帮助。
I found you have posted a same thread with the following links. I think you will get a suitable help in there.
最好的问候，
Best Regards,
Yohann Lu
Yohann Lu
这篇关于为什么Windows10注销我的OEM SMB2服务器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！