| 1 | SMB Client Shares |
SMB Client Shares |
| 3 | 此计数器集显示有关客户端使用 SMB 协议版本 2 或更高版本访问的服务器共享的信息。 |
This counter set displays information about server shares that are being accessed by the client using SMB protocol version 2 or higher. |
| 9 | Read Bytes/sec |
Read Bytes/sec |
| 11 | 从此共享中读取字节的速率。 |
The rate at which bytes are being read from this share. |
| 17 | Write Bytes/sec |
Write Bytes/sec |
| 19 | 将字节写入此共享的速率。 |
The rate at which bytes are being written to this share. |
| 25 | Read Requests/sec |
Read Requests/sec |
| 27 | 将读取请求发送到此共享的速率。 |
The rate at which read requests are being sent to this share. |
| 33 | Write Requests/sec |
Write Requests/sec |
| 35 | 将写入请求发送到此共享的速率。 |
The rate at which write requests are being sent to this share. |
| 37 | Avg. Bytes/Read |
Avg. Bytes/Read |
| 39 | 每个读取请求的平均字节数。 |
The average number of bytes per read request. |
| 41 | Avg. Bytes/Write |
Avg. Bytes/Write |
| 43 | 每个写入请求的平均字节数。 |
The average number of bytes per write request. |
| 45 | Avg. sec/Read |
Avg. sec/Read |
| 47 | 发送读取请求与收到请求响应之间的平均时间延迟。 |
The average latency between the time a read request is sent and when its response is received. |
| 49 | Avg. sec/Write |
Avg. sec/Write |
| 51 | 发送写入请求与收到请求响应之间的平均时间延迟。 |
The average latency between the time a write request is sent and when its response is received. |
| 53 | Data Bytes/sec |
Data Bytes/sec |
| 55 | 将字节读入或写入此共享的速率。 |
The rate at which bytes are being read or written to this share. |
| 57 | Data Requests/sec |
Data Requests/sec |
| 59 | 将读取或写入请求发送到此共享的速率。 |
The rate at which read or write requests are being sent to this share. |
| 61 | Avg. Data Bytes/Request |
Avg. Data Bytes/Request |
| 63 | 每个读取或写入请求的平均字节数。 |
The average number of bytes per read or write request. |
| 65 | Avg. sec/Data Request |
Avg. sec/Data Request |
| 67 | 发送读取或写入请求与收到请求响应之间的平均时间延迟。 |
The average latency between the time a read or write request is sent and when its response is received. |
| 69 | Current Data Queue Length |
Current Data Queue Length |
| 71 | 此共享上当前未完成的读取或写入请求数。 |
The current number of read or write requests outstanding on this share. |
| 73 | Avg. Read Queue Length |
Avg. Read Queue Length |
| 75 | 为此共享列队的平均读取请求数。 |
The average number of read requests that were queued for this share. |
| 77 | Avg. Write Queue Length |
Avg. Write Queue Length |
| 79 | 为此共享列队的平均写入请求数。 |
The average number of write requests that were queued for this share. |
| 81 | Avg. Data Queue Length |
Avg. Data Queue Length |
| 83 | 为此共享列队的平均读写请求数。 |
The average number of both read and write requests that were queued for this share. |
| 89 | Metadata Requests/sec |
Metadata Requests/sec |
| 91 | 将元数据请求发送到此共享的速率。 |
The rate at which metadata requests are being sent to this share. |
| 93 | Credit Stalls/sec |
Credit Stalls/sec |
| 95 | 由于此共享的信用不足，每秒延迟的请求数。 |
The number of requests per second delayed based on insufficient credits for this share. |
| 0x30000000 | 信息 |
Info |
| 0x3000000B | 服务器错误 |
Server Error |
| 0x3000000C | 缓存的错误 |
Cached Error |
| 0x3000000D | 初始化安全上下文错误 |
Initialize Security Context Error |
| 0x3000000E | 安全签名错误 |
Security Signature Error |
| 0x300000B4 | 开始状态 |
Start State |
| 0x300000B5 | 结束状态 |
End State |
| 0x50000002 | 错误 |
Error |
| 0x50000003 | 警告 |
Warning |
| 0x50000005 | 详细 |
Verbose |
| 0x90000001 | Microsoft-Windows-SMBClient |
Microsoft-Windows-SMBClient |
| 0x90000002 | Microsoft-Windows-SMBClient/HelperClassDiagnostic |
Microsoft-Windows-SMBClient/HelperClassDiagnostic |
| 0x90000003 | Microsoft-Windows-SMBClient/ObjectStateDiagnostic |
Microsoft-Windows-SMBClient/ObjectStateDiagnostic |
| 0x90000004 | Microsoft-Windows-SMBClient/Operational |
Microsoft-Windows-SMBClient/Operational |
| 0x90000005 | Microsoft-Windows-SMBClient/XPerfAnalytic |
Microsoft-Windows-SMBClient/XPerfAnalytic |
| 0x90000006 | Microsoft-Windows-SMBClient/Diagnostic |
Microsoft-Windows-SMBClient/Diagnostic |
| 0x90000007 | Microsoft-Windows-SMBClient/Connectivity |
Microsoft-Windows-SMBClient/Connectivity |
| 0x90000008 | Microsoft-Windows-SMBClient/Security |
Microsoft-Windows-SMBClient/Security |
| 0xB0000065 | 创建 SrvCall 错误:%1 位置:%2 上下文:%3 |
Create SrvCall Error: %1 Location: %2 Context: %3 |
| 0xB00000C9 | 会话设置错误:%1 位置:%2 上下文:%3 |
Session Setup Error: %1 Location: %2 Context: %3 |
| 0xB000012D | 树连接错误:%1 位置:%2 上下文:%3 |
Tree Connect Error: %1 Location: %2 Context: %3 |
| 0xB0000191 | 创建 VNetRoot 错误:%1 位置:%2 上下文:%3 |
Create VNetRoot Error: %1 Location: %2 Context: %3 |
| 0xB00001F5 | 创建文件错误:%1 位置:%2 上下文:%3 |
Create File Error: %1 Location: %2 Context: %3 |
| 0xB00007D0 | 数据包碎片(%2 个字节) |
Packet Fragment (%2 bytes) |
| 0xB0004E21 | 转换为状态: %1 上下文: %2 |
Transitioned to State: %1 Context: %2 |
| 0xB0007597 | SMB 交换已暂停: RxContext %1 交换 %2 ListHead %3 |
SMB exchange suspended: RxContext %1 Exchange %2 ListHead %3 |
| 0xB0007598 | SMB 交换已恢复: RxContext %1 交换 %2 ExchangeState %3 ExchangeStatus %4 |
SMB exchange resumed: RxContext %1 Exchange %2 ExchangeState %3 ExchangeStatus %4 |
| 0xB0007599 | SMB 缓冲区上下文已暂停: BufferCtxt %1 交换 %2 MidCharge %3 窗口 %4 CurrentWindowLimit %5 ThrottlingWindowLimit %6 CurrentWindowSize %7 |
SMB buffer context suspended: BufferCtxt %1 Exchange %2 MidCharge %3 Window %4 CurrentWindowLimit %5 ThrottlingWindowLimit %6 CurrentWindowSize %7 |
| 0xB000759A | SMB 缓冲区上下文已恢复: BufferCtxt %1 交换 %2 MidCharge %3 窗口 %4 CurrentWindowLimit %5 ThrottlingWindowLimit %6 CurrentWindowSize %7 |
SMB buffer context resumed: BufferCtxt %1 Exchange %2 MidCharge %3 Window %4 CurrentWindowLimit %5 ThrottlingWindowLimit %6 CurrentWindowSize %7 |
| 0xB000759C | SMB 中间窗口已阻止: 窗口 %1 HungSession %2 |
SMB Mid window blocked: Window %1 HungSession %2 |
| 0xB000759D | SMB 重新划分区块多信用请求: BufferCtxt %1 交换 %2 MidCharge %3 窗口 %4 CurrentWindowLimit %5 ThrottlingWindowLimit %6 CurrentWindowSize %7 |
SMB rechunk multi-credit request: BufferCtxt %1 Exchange %2 MidCharge %3 Window %4 CurrentWindowLimit %5 ThrottlingWindowLimit %6 CurrentWindowSize %7 |
| 0xB000759E | SMB 初始化中间窗口: 服务器 %2 窗口 %3 |
SMB initialize Mid window: Server %2 Window %3 |
| 0xB000759F | SMB 中间窗口状态: 窗口 %1 CurrentWindowSize %2 CurrentWindowLimit %3 ThrottlingWindowLimit %4 OldestPendingMid %5 NextAvailableMid %6 CreditsGranted %7 |
SMB Mid window state: Window %1 CurrentWindowSize %2 CurrentWindowLimit %3 ThrottlingWindowLimit %4 OldestPendingMid %5 NextAvailableMid %6 CreditsGranted %7 |
| 0xB00075A0 | SMB 拆卸中间窗口: 服务器 %2 窗口 %3 |
SMB teardown Mid window: Server %2 Window %3 |
| 0xB00075A1 | SMB 复制数据完成: 状态 %1 VcEndpoint %2 |
SMB copy data completion: Status %1 VcEndpoint %2 |
| 0xB00075A2 | SMB 发送完成: 状态 %1 VcEndpoint %2 |
SMB send completion: Status %1 VcEndpoint %2 |
| 0xB00075FB | WSK 连接: SocketAddress %2 VcEndpoint %3 套接字 %4 |
WSK connect: SocketAddress %2 VcEndpoint %3 Socket %4 |
| 0xB00075FC | WSK 连接完成: VcEndpoint %1 套接字 %2 状态 %3 |
WSK connect completion: VcEndpoint %1 Socket %2 Status %3 |
| 0xB00075FD | WSK 发送: VcEndpoint %1 套接字 %2 SendMdl %3 SendLength %4 |
WSK send: VcEndpoint %1 Socket %2 SendMdl %3 SendLength %4 |
| 0xB00075FE | WSK 发送完成: VcEndpoint %1 套接字 %2 SendMdl %3 SendLength %4 状态 %5 |
WSK send completion: VcEndpoint %1 Socket %2 SendMdl %3 SendLength %4 Status %5 |
| 0xB00075FF | WSK 接收: VcEndpoint %1 套接字 %2 ReceiveMdl %3 ReceiveLength %4 |
WSK receive: VcEndpoint %1 Socket %2 ReceiveMdl %3 ReceiveLength %4 |
| 0xB0007600 | WSK 接收完成: VcEndpoint %1 套接字 %2 ReceiveMdl %3 ReceiveLength %4 状态 %5 |
WSK receive completion: VcEndpoint %1 Socket %2 ReceiveMdl %3 ReceiveLength %4 Status %5 |
| 0xB00076C1 | SMB 会话已过期: SessionEntry %1 ServerName %3 |
SMB session expired: SessionEntry %1 ServerName %3 |
| 0xB00076C2 | SMB 3 部分 SPN 重新身份验证: SessionEntry %1 ServiceName %3 |
SMB 3 part SPN reauth: SessionEntry %1 ServiceName %3 |
| 0xB00076C3 | SMB 重新连接持久打开: Fcb %1 SrvOpen %2 |
SMB reconnect durable open: Fcb %1 SrvOpen %2 |
| 0xB00076C4 | SMB 延迟打开: Fcb %1 SrvOpen %2 |
SMB defer open: Fcb %1 SrvOpen %2 |
| 0xB00076C5 | SMB 未延迟打开: Fcb %1 SrvOpen %2 |
SMB undefer open: Fcb %1 SrvOpen %2 |
| 0xB00076C6 | SMB 发送[%1]: [%2] (Mid/Sid/Tid) (%3/%4/%5) MidCharge %6 凭据 %7 SendLengh %8 VcEndpoint %9 |
SMB send[%1]: [%2] (Mid/Sid/Tid) (%3/%4/%5) MidCharge %6 Creds %7 SendLengh %8 VcEndpoint %9 |
| 0xB00076C7 | SMB 接收: [%1] (Mid/Sid/Tid) (%2/%4/%5) 凭据 %6 状态 %7 VcEndpoint %8 |
SMB receive: [%1] (Mid/Sid/Tid) (%2/%4/%5) Creds %6 Status %7 VcEndpoint %8 |
| 0xB00076C8 | SMB 接收中期: [%1] (Mid/AsyncId/Sid/Tid) (%2/%3/%4/%5) 凭据 %6 状态 %7 VcEndpoint %8 |
SMB receive interim: [%1] (Mid/AsyncId/Sid/Tid) (%2/%3/%4/%5) Creds %6 Status %7 VcEndpoint %8 |
| 0xB00076C9 | SMB 异步接收: [%1] (AsyncId/Sid/Tid) (%3/%4/%5) 凭据 %6 状态 %7 VcEndpoint %8 |
SMB receive async: [%1] (AsyncId/Sid/Tid) (%3/%4/%5) Creds %6 Status %7 VcEndpoint %8 |
| 0xB00076CA | SMB 注册表项: %1 = %2 |
SMB registry key: %1 = %2 |
| 0xB0007725 | SMB 更新文件信息缓存: RxContext %1 Fcb %2 FileName %4 |
SMB update file info cache: RxContext %1 Fcb %2 FileName %4 |
| 0xB0007726 | SMB 获取文件信息缓存: RxContext %1 Fcb %2 FileName %4 状态 %5 |
SMB fetch file info cache: RxContext %1 Fcb %2 FileName %4 Status %5 |
| 0xB0007727 | SMB 失效文件信息缓存: RxContext %1 Fcb %2 FileName %4 |
SMB invalidate file info cache: RxContext %1 Fcb %2 FileName %4 |
| 0xB0007728 | SMB 更新文件未找到缓存: RxContext %1 Fcb %2 FileName %4 |
SMB update file not found cache: RxContext %1 Fcb %2 FileName %4 |
| 0xB0007729 | SMB 获取文件未找到缓存: RxContext %1 Fcb %2 FileName %4 结果 %5 |
SMB fetch file not found cache: RxContext %1 Fcb %2 FileName %4 Result %5 |
| 0xB000772A | SMB 失效文件未找到缓存: RxContext %1 Fcb %2 FileName %4 |
SMB invalidate file not found cache: RxContext %1 Fcb %2 FileName %4 |
| 0xB000772B | SMB 填充目录缓存: RxContext %1 Fcb %2 DirName %4 |
SMB populate dir cache: RxContext %1 Fcb %2 DirName %4 |
| 0xB000772C | SMB 获取目录缓存: RxContext %1 Fcb %2 FileName %4 状态 %5 |
SMB fetch dir cache: RxContext %1 Fcb %2 FileName %4 Status %5 |
| 0xB0007788 | %6 的会话 %1 已从 [%2] 转换为 [%3]，状态为 %4 |
Session %1 to %6 transitioned from [%2] to [%3] with Status %4 |
| 0xB0007789 | %6 的共享连接 %1 已从 [%2] 转换为 [%3]，状态为 %4 |
Share connection %1 to %6 transitioned from [%2] to [%3] with Status %4 |
| 0xB000778B | %10%12 的开放句柄 %1 已从 [%5] 转换为 [%6]，状态为 %7 |
Open handle %1 to %10%12 transitioned from [%5] to [%6] with Status %7 |
| 0xB0007795 | 无法打开持久句柄。%n%n错误: %7%n%nFileId: %2:%3%nCreateGUID: %4%n路径: %10%12%n%n原因: %8%n%n指导:%n持久句柄允许 Windows 文件服务器群集上存在透明故障转移。此事件有多种起因，它并不总是表示 SMB 存在问题。请检查联机文档，以了解疑难解答信息。 |
Failed to open a persistent handle.%n%nError: %7%n%nFileId: %2:%3%nCreateGUID: %4%nPath: %10%12%n%nReason: %8%n%nGuidance:%nA persistent handle allows transparent failover on Windows File Server clusters. This event has many causes and does not always indicate an issue with SMB. Review online documentation for troubleshooting information. |
| 0xB00077ED | 服务器 %2 发送了一个无效的 FSCTL_QUERY_NETWORK_INTERFACE_INFO 响应 |
An invalid FSCTL_QUERY_NETWORK_INTERFACE_INFO response was sent by the server %2 |
| 0xB00077EE | 客户端无法通过 TCP 传输连接到服务器 %2 (从本地 IP 地址 %4 到远程 IP 地址 %6)。错误: %7 |
The client failed to connect to the server %2 from the local IP address %4 to the remote IP address %6 over TCP transport. Error: %7 |
| 0xB00077EF | 客户端无法通过 RDMA 传输连接到服务器 %2 (从本地 IP 地址 %4 到远程 IP 地址 %6)。错误: %7 |
The client failed to connect to the server %2 from the local IP address %4 to the remote IP address %6 over RDMA transport. Error: %7 |
| 0xB00077F0 | 客户端已成功通过 TCP 传输连接到服务器 %2 (从本地 IP 地址 %4 到远程 IP 地址 %6) |
The client connected to the server %2 from the local IP address %4 to the remote IP address %6 over TCP transport successfully |
| 0xB00077F1 | 客户端已成功通过 RDMA 传输连接到服务器 %2 (从本地 IP 地址 %4 到远程 IP 地址 %6) |
The client connected to the server %2 from the local IP address %4 to the remote IP address %6 over RDMA transport successfully |
| 0xB0007850 | 服务器名称无法解析。%n%n错误: %2%n%n服务器名称: %4%n%n指导:%n客户端无法解析 DNS 或 WINS 中的服务器地址。此问题通常会在将计算机加入域后立即显现，因为此时客户端的 DNS 注册可能尚未传播到所有 DNS 服务器。当指向主 DNS 本身的 DNS 服务器(例如域控制器)上的系统启动时，也可能发生此事件。你应当使用 IPCONFIG /ALL 和 NSLOOKUP 验证此计算机上的 DNS 客户端设置。 |
The server name cannot be resolved.%n%nError: %2%n%nServer name: %4%n%nGuidance:%nThe client cannot resolve the server address in DNS or WINS. This issue often manifests immediately after joining a computer to the domain, when the client's DNS registration may not yet have propagated to all DNS servers. You should also expect this event at system startup on a DNS server (such as a domain controller) that points to itself for the primary DNS. You should validate the DNS client settings on this computer using IPCONFIG /ALL and NSLOOKUP. |
| 0xB0007851 | %1。%n%n错误: %2%n%n服务器名称: %4 |
%1.%n%nError: %2%n%nServer name: %4 |
| 0xB0007853 | 无法建立网络连接。%n%n错误: %2%n%n服务器名称: %4%n服务器地址: %6%n连接类型: %7%n%n指导:%n这表明基础网络或传输(例如 TCP/IP)出现问题，而不是 SMB 的问题。使用 iWARP RDMA 适配器时，阻止 TCP 端口 445 或 5445 的防火墙也可能导致此问题。 |
Failed to establish a network connection.%n%nError: %2%n%nServer name: %4%nServer address: %6%nConnection type: %7%n%nGuidance:%nThis indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks TCP port 445, or TCP port 5445 when using an iWARP RDMA adapter, can also cause this issue. |
| 0xB0007854 | 网络连接已断开。%n%n服务器名称: %4%n服务器地址: %6%n连接类型: %7%n%n指导:%n这表明客户端与服务器之间的连接已断开。%n%n在使用基于融合以太网的 RDMA (RoCE)适配器时，如果经常出现意外的连接断开，则可能表明网络配置不当。RoCE 要求为 RoCE 网络上的每个主机、交换机和路由器配置优先级流量控制(PFC)。不正确配置 PFC 会导致丢失数据包、连接频繁断开和性能不良。 |
A network connection was disconnected.%n%nServer name: %4%nServer address: %6%nConnection type: %7%n%nGuidance:%nThis indicates that the client's connection to the server was disconnected.%n%nFrequent, unexpected disconnects when using an RDMA over Converged Ethernet (RoCE) adapter may indicate a network misconfiguration. RoCE requires Priority Flow Control (PFC) to be configured for every host, switch and router on the RoCE network. Failure to properly configure PFC will cause packet loss, frequent disconnects and poor performance. |
| 0xB0007859 | 请求超时，因为服务器没有响应。%n%n服务器名称: %6%n会话 ID:%3%n树 ID:%4%n消息 ID:%2%n命令: %1%n%n指导:%n服务器通过 TCP 而不是 SMB 做出响应。请确保服务器服务正在运行并且可响应，而且磁盘没有很高的每 IO 延迟(该延迟会使磁盘看起来好像无法响应 SMB)。此外，还要确保服务器的整体响应性，并且没有暂停；例如，确保你能够登录到该服务器。 |
A request timed out because there was no response from the server.%n%nServer name: %6%nSession ID:%3%nTree ID:%4%nMessage ID:%2%nCommand: %1%n%nGuidance:%nThe server is responding over TCP but not over SMB. Ensure the Server service is running and responsive, and the disks do not have high per-IO latency, which makes the disks appear unresponsive to SMB. Also, ensure the server is responsive overall and not paused; for instance, make sure you can log on to it. |
| 0xB000785A | 已添加一个 TCP/IP 传输接口。%n%n名称: %2%nInterfaceIndex: %3%n%n指导:%n已向 SMB 客户端的指定网络适配器添加了一个 TCP/IP 绑定。SMB 客户端当前可使用 TCP/IP 发送和接收此网络适配器上的 SMB 流量。当计算机重新启动或之前禁用的网络适配器被重新启用时，可能会发生此事件。无需任何用户操作。 |
Added a TCP/IP transport interface.%n%nName: %2%nInterfaceIndex: %3%n%nGuidance:%nA TCP/IP binding was added to the specified network adapter for the SMB client. The SMB client can now send and receive SMB traffic on this network adapter using TCP/IP. You should expect this event when a computer restarts or when a previously disabled network adaptor is re-enabled. No user action is required. |
| 0xB000785B | 已删除一个 TCP/IP 传输接口。%n%n名称: %2%nInterfaceIndex: %3%n%n指导:%n已从 SMB 客户端的指定网络适配器中删除了一个 TCP/IP 绑定。当计算机关机或之前启用的网络适配器被禁用时，可能会发生此事件。无需任何用户操作。 |
Deleted a TCP/IP transport interface.%n%nName: %2%nInterfaceIndex: %3%n%nGuidance:%nA TCP/IP binding was removed from the specified network adapter for the SMB client. You should expect this event when a computer shuts down or when a previously enabled network adaptor is disabled. No user action is required. |
| 0xB000785C | 已添加一个 TDI 传输接口。%n%n名称: %2%n%n指导:%n已向 SMB 客户端的指定网络适配器添加了一个 TDI (NetBIOS)绑定。SMB 当前可使用 TDI 发送和接收此网络适配器上的 SMB 流量。当计算机重新启动或之前禁用的网络适配器被重新启用时，可能会发生此事件。无需任何用户操作。 |
Added a TDI transport interface.%n%nName: %2%n%nGuidance:%nA TDI (NetBIOS) binding was added to the specified network adapter for the SMB client. The SMB client can now send and receive SMB traffic on this network adapter using TDI. You should expect this event when a computer restarts or when a previously disabled network adaptor is re-enabled. No user action is required. |
| 0xB000785D | 已删除一个 TDI 传输接口。%n%n名称: %2%n%n指导:%n已从 SMB 客户端的指定网络适配器删除了一个 TDI (NetBIOS)绑定。当计算机关机或之前启用的网络适配器被禁用时，可能会发生此事件。无需任何用户操作。 |
Deleted a TDI transport interface.%n%nName: %2%n%nGuidance:%nA TDI (NetBIOS) binding was removed from the specified network adapter for the SMB client. You should expect this event when a computer shuts down or when a previously enabled network adaptor is disabled. No user action is required. |
| 0xB000785E | 见证注册已完成。%n%n状态: %1%n%n群集共享名称: %4%n群集共享类型: %2%n文件服务器群集地址: %6%n%n指导:%n客户端已成功注册使用 TCP 并通过 RPC (端口 135，然后是 1023 以上的终结点端口)的 SMB 见证。无需任何用户操作。 |
Witness registration has completed.%n%nStatus: %1%n%nCluster share name: %4%nCluster share type: %2%nFile server cluster address: %6%n%nGuidance:%nThe client successfully registered with the SMB Witness through RPC using TCP (port 135, then an endpoint port above 1023). No action is required. |
| 0xB000785F | 见证注销已完成。%n%n状态: %1%n%n群集共享名称: %4%n群集共享类型: %2%n%n指导:%n客户端已成功注销使用 TCP 并且通过 RPC (端口 135，然后是 1023 以上的终结点端口)的 SMB 见证。无需任何用户操作。 |
Witness deregistration has completed.%n%nStatus: %1%n%nCluster share name: %4%nCluster share type: %2%n%nGuidance:%nThe client successfully de-registered with the SMB Witness through RPC using TCP (port 135, then an endpoint port above 1023). No action is required. |
| 0xB0007860 | 服务器无法协商请求。%n%n错误: %2%n%n服务器名称: %4%n%n指导:%n服务器不支持客户端正在尝试协商的任何方言，例如客户端已禁用 SMB2/SMB3，而服务器禁用了 SMB1。 |
The server failed the negotiate request.%n%nError: %2%n%nServer name: %4%n%nGuidance:%nThe server does not support any dialect that the client is trying to negotiate, such as the client has SMB2/SMB3 disabled and the server has SMB1 disabled. |
| 0xB0007861 | 关闭请求失败。%n%n错误: %2%n%n路径: %4%6%n%n指导:%n持久句柄(连续可用性)或弹性句柄无法关闭。 |
Close request failed.%n%nError: %2%n%nPath: %4%6%n%nGuidance:%nA persistent handle (Continuous Availability) or a resilient handle failed to close. |
| 0xB0007862 | 有可用的 RDMA 接口，但客户端无法通过 RDMA 传输连接到服务器。%n%n服务器名称: %2%n%n指导:%n客户端和服务器都有 RDMA (SMB 直通)适配器，但是连接存在问题，因此客户端不得不回退以使用 TCP/IP SMB (非-RDMA)。 |
RDMA interfaces are available but the client failed to connect to the server over RDMA transport.%n%nServer name: %2%n%nGuidance:%nBoth client and server have RDMA (SMB Direct) adaptors but there was a problem with the connection and the client had to fall back to using TCP/IP SMB (non-RDMA). |
| 0xB0007866 | 无法建立 SMB 多通道网络连接。%n%n错误: %2%n%n服务器名称: %4%n服务器地址: %6%n客户端地址: %7%n实例名称: %9%n连接类型: %10%n%n指导: %n这表示基础网络或传输出现问题(例如，TCP/IP 出现问题)，而不是 SMB 有问题。使用 iWARP RDMA 适配器时会阻止 TCP 端口 445 或 TCP 端口 5445 的防火墙也可能会导致此问题。由于该错误是在尝试连接附加通道时发生的，因此不会导致应用程序出错。此事件仅用于诊断。 |
Failed to establish an SMB multichannel network connection.%n%nError: %2%n%nServer name: %4%nServer address: %6%nClient address: %7%nInstance name: %9%nConnection type: %10%n%nGuidance:%nThis indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks TCP port 445, or TCP port 5445 when using an iWARP RDMA adapter, can also cause this issue. Since the error occurred while trying to connect extra channels, it will not result in an application error. This event is for diagnostics only. |
| 0xB00078BA | 请求永久/弹性句柄失败，因为句柄无效或已超过超时期限。%n%n状态: %7%n%n类型: %1%n路径: %4%6%n重新启动计数: %2%n%n指导:%n在重试请求连续可用(永久)句柄或弹性句柄之后，客户端无法重新连接句柄。此事件是由于句柄恢复失败而导致的。请查看其他事件以了解详情。 |
A request on persistent/resilient handle failed because the handle was invalid or it exceeded the timeout.%n%nStatus: %7%n%nType: %1%nPath: %4%6%nRestart count: %2%n%nGuidance:%nAfter retrying a request on a Continuously Available (Persistent) handle or a Resilient handle, the client was unable to reconnect the handle. This event is the result of a handle recovery failure. Review other events for more details. |
| 0xB00078BB | SMB 多通道注册表值未配置为默认设置。%n%n默认注册表值:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"DisableMultiChannel\"=dword:0%n已配置的注册表值:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"DisableMultiChannel\"=dword:%2%n%n指导:%n你可以使用 Windows PowerShell cmdlet Set-SmbClientConfiguration 配置客户端上的 SMB 多通道。不推荐配置为禁用 SMB 客户端多通道支持，因为在某个通道或网络路径失败时，它可能导致性能和可靠性的降低。 |
The SMB Multichannel registry value is not configured with default settings.%n%nDefault Registry Value:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"DisableMultiChannel\"=dword:0%nConfigured Registry Value:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"DisableMultiChannel\"=dword:%2%n%nGuidance:%nYou can configure SMB Multichannel on the client using the Windows PowerShell cmdlet Set-SmbClientConfiguration. Disabling SMB client multichannel support is not a recommended configuration, as it can lead to degraded performance and decreased reliability if one channel or network path fails. |
| 0xB00078BC | SMB 3 和 SMB 2 驱动程序未配置为默认启动类型。%n%n默认启动类型: DEMAND_START%n已配置的启动类型: 禁用%n%n指导:%n通过使用 SC.EXE 或编辑 Windows 注册表以禁用客户端的 SMB2/SMB3，可能会发生此事件。Microsoft 不建议禁用 SMB2/SMB3。如果禁用 SMB2/SMB3，则你将无法使用 SMB 透明故障转移、SMB 横向扩展、SMB 多通道、SMB 直通(RDMA)、SMB 加密、SMB 文件共享的 VSS 和 SMB 目录租赁等功能。在大多数情况下，SMB 提供一套替代故障排除解决方法，用于禁用 SMB2/SMB3。 |
The SMB 3 and SMB 2 driver is not configured with the default start type.%n%nDefault Start Type: DEMAND_START%nConfigured Start Type: DISABLED%n%nGuidance:%nYou should expect this event when disabling SMB2/SMB3 for the client using SC.EXE or editing the Windows registry. Microsoft does not recommend disabling SMB2/SMB3. Disabling SMB2/SMB3 prevents use of features such as SMB Transparent Failover, SMB Scale Out, SMB Multichannel, SMB Direct (RDMA), SMB Encryption, VSS for SMB file shares, and SMB Directory Leasing. SMB provides alternative troubleshooting workarounds to disabling SMB2/SMB3 in most cases. |
| 0xB00078BD | 客户端支持 SMB 直通(RDMA)，并且 SMB 签名正在使用中。%n%n共享名称: %2%n%n指导:%n要获取最佳的 SMB 直通性能，你可以禁用 SMB 签名。此配置的安全性较低，只有在具有严格访问控制的可靠的专用网络上，才会考虑此配置。 |
The client supports SMB Direct (RDMA) and SMB Signing is in use.%n%nShare name: %2%n%nGuidance:%nFor optimal SMB Direct performance, you can disable SMB Signing. This configuration is less secure and you should only consider this configuration on trustworthy private networks with strict access control. |
| 0xB00078BE | 客户端支持 SMB 直通(RDMA)，并且 SMB 加密正在使用中。%n%n共享名称: %2%n%n指导:%n要获取最佳的 SMB 直通性能，你可以在此客户端访问的共享服务器上禁用 SMB 加密。此配置的安全性较低，只有在具有严格访问控制的可靠的专用网络上，才会考虑此配置。 |
The client supports SMB Direct (RDMA) and SMB Encryption is in use.%n%nShare name: %2%n%nGuidance:%nFor optimal SMB Direct performance, you can disable SMB Encryption on the server for shares accessed by this client. This configuration is less secure and you should only consider this configuration on trustworthy private networks with strict access control. |
| 0xB00078BF | 密码套件顺序组策略设置无效。%n%n指导:%n%n此事件表明管理员为“Computer Configuration\\Administrative Templates\\Network\\Lanman Workstation\\Cipher Suite Order”组策略设置配置了无效值。在解决此错误之前，客户端将使用默认的密码套件顺序“%1”。 |
The Cipher Suite Order group policy setting is invalid.%n%nGuidance:%n%nThis event indicates that an administrator has configured an invalid value for the \"Computer Configuration\\Administrative Templates\\Network\\Lanman Workstation\\Cipher Suite Order\" group policy setting. The client will use the default cipher suite order \"%1\" until this error is resolved. |
| 0xB00078C0 | 已删除 RequireSecureNegotiate 设置。%n%n注册表项: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters%n注册表值: RequireSecureNegotiate%n%n指导:%n%n当管理员配置了 RequireSecureNegotiate 设置时，你应该预料到会发生此事件。安全协商可以阻止对 SMB 连接建立过程发起中间人攻击。早期的 Windows 版本允许禁用安全协商。现在不再允许禁用安全协商。客户端从注册表中删除了该设置。无需用户操作。 |
The RequireSecureNegotiate setting has been removed.%n%nRegistry Key: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters%nRegistry Value: RequireSecureNegotiate%n%nGuidance:%n%nYou should expect this event when an administrator configures the RequireSecureNegotiate setting. Secure negotiate prevents man-in-the-middle attacks against SMB connection establishment. Previous versions of Windows allowed secure negotiate to be disabled. Disabling secure negotiate is no longer allowed. The client removed the setting from the registry. No user action is required. |
| 0xB0007918 | %1。%n%n错误: %2%n%n安全状态: %3%n用户名: %10%n登录 ID: %4%n服务器名称: %6 |
%1.%n%nError: %2%n%nSecurity status: %3%nUser name: %10%nLogon ID: %4%nSerrver name: %6 |
| 0xB0007919 | %1。%n%n错误: %2%n%n安全状态: %3%n用户名: %10%n登录 ID: %4%n服务器名称: %6%n主体名称: %8 |
%1.%n%nError: %2%n%nSecurity status: %3%nUser name: %10%nLogon ID: %4%nServer name: %6%nPrincipal name: %8 |
| 0xB000791A | 使用网络令牌进行出站身份验证失败。%n%n错误: %2%n%n服务器名称: %4%n%n指导:%n这通常表示必须为 Kerberos 双跃点方案配置委派。如果配置了委派，请确认服务已在中间层服务器上进行了正确的配置。 |
The outbound authentication failed using a network token.%n%nError: %2%n%nServer name: %4%n%nGuidance:%nThis typically indicates that delegation must be configured for a Kerberos double-hop scenario. If delegation is configured, confirm that the services are configured correctly on the middle-tier server. |
| 0xB000791B | LmCompatibilityLevel 值不同于默认值。%n%n已配置的 LM 兼容级别: %2%n默认的 LM 兼容级别: 3%n%n指导:%nLAN Manager (LM)身份验证是用于对执行网络操作的 Windows 客户端进行身份验证的协议。它包括加入域、访问网络资源、以及对用户或计算机进行身份验证。它决定在客户端和服务器计算机之间协商哪些质询/响应身份验证协议。具体来说，LM 身份验证级别决定客户端将尝试协商或服务器将接受哪些身份验证协议。LmCompatibilityLevel 的值集决定哪些质询/响应身份验证协议将被用于网络登录。此值会影响客户端所使用的身份验证协议的级别、协商的会话安全级别、以及服务器可接受的身份验证级别。%n%n值(设置) - 描述%n%n0 (发送 LM 和 NTLM 响应) - 客户端使用 LM 和 NTLM 身份验证，并且从不使用 NTLMv2 会话安全。域控制器接受 LM、NTLM 和 NTLMv2 身份验证。%n%n1 (发送 LM 和 NTLM - 如果已协商，则使用 NTLMv2 会话安全) - 客户端使用 LM 和 NTLM 身份验证，并使用受服务器支持的 NTLMv2 会话安全。域控制器接受 LM、NTLM 和 NTLMv2 身份验证。%n%n2 (只发送 NTLM 响应) - 客户端只使用 NTLM 身份验证，并使用受服务器支持的 NTLMv2 会话安全。域控制器接受 LM、NTLM 和 NTLMv2 身份验证。%n%n3 (只发送 NTLM v2 响应) - 客户端只使用 NTLMv2 身份验证，并使用受服务器支持的 NTLMv2 会话安全。域控制器接受 LM、NTLM 和 NTLMv2 身份验证。%n%n4 (只发送 NTLMv2 响应/拒绝 LM) - 客户端只使用 NTLMv2 身份验证，并使用受服务器支持的 NTLMv2 会话安全。域控制器拒绝 LM 而只接受 NTLM 和 NTLMv2 身份验证。%n%n5 (只发送 NTLM v2 响应/拒绝 LM 和 NTLM) - 客户端只使用 NTLMv2 身份验证，并使用受服务器支持的 NTLMv2 会话安全。域控制器拒绝 LM 和 NTLM 而只接受 NTLMv2 身份验证。%n%n客户端和服务器之间配置不兼容的 LmCompatibility 级别(例如客户端上是 0 而服务器上是 5)会阻止访问服务器。非 Microsoft 客户端和服务器也提供这些配置设置。 |
The LmCompatibilityLevel value is different from the default.%n%nConfigured LM Compatibility Level: %2%nDefault LM Compatibility Level: 3%n%nGuidance:%nLAN Manager (LM) authentication is the protocol used to authenticate Windows clients for network operations. This includes joining a domain, accessing network resources, and authenticating users or computers. This determines which challenge/response authentication protocol is negotiated between the client and the server computers. Specifically, the LM authentication level determines which authentication protocols the client will try to negotiate or the server will accept. The value set for LmCompatibilityLevel determines which challenge/response authentication protocol is used for network logons. This value affects the level of authentication protocol that clients use, the level of session security negotiated, and the level of authentication accepted by servers.%n%nValue (Setting) - Description%n%n0 (Send LM & NTLM responses) - Clients use LM and NTLM authentication and never use NTLMv2 session security. Domain controllers accept LM, NTLM, and NTLMv2 authentication.%n%n1 (Send LM & NTLM - use NTLMv2 session security if negotiated) - Clients use LM and NTLM authentication, and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.%n%n2 (Send NTLM response only) - Clients use NTLM authentication only and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.%n%n3 (Send NTLM v2 response only) - Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.%n%n4 (Send NTLMv2 response only/refuse LM) - Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it. Domain controllers refuse LM and accept only NTLM and NTLMv2 authentication.%n%n5 (Send NTLM v2 response only/refuse LM & NTLM) - Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it. Domain controllers refuse LM and NTLM and accept only NTLMv2 authentication.%n%nIncompatibly configured LmCompatibility levels between a client and server (such as 0 on a client and 5 on a server) prevent access to the server. Non-Microsoft clients and servers also provide these configuration settings. |
| 0xB0007922 | SMB 无法连接到共享。%n%n错误: %2%n%n路径: %4%6 |
The SMB client failed to connect to the share.%n%nError: %2%n%nPath: %4%6 |
| 0xB0007924 | 协商验证失败。%n%n来自协商响应:%n方言: %1%nSecurityMode: %2%n功能: %3%nServerGuid: %4%n%n来自 FSCTL_VALIDATE_NEGOTIATE_INFO 响应:%n方言: %5%nSecurityMode: %6%n功能: %7%nServerGuid: %8%n%n指导:%n客户端已成功与服务器协商 SMB 方言、安全模式、功能和服务器 GUID，但是在连接到共享后对这些值的验证失败。这可能是由于“中间人”泄露尝试所致。 |
The negotiate validation failed.%n%nFrom negotiate response:%nDialect: %1%nSecurityMode: %2%nCapabilities: %3%nServerGuid: %4%n%nFrom FSCTL_VALIDATE_NEGOTIATE_INFO response:%nDialect: %5%nSecurityMode: %6%nCapabilities: %7%nServerGuid: %8%n%nGuidance:%nThe client successfully negotiated SMB dialect, security mode, capabilities and server GUID with the server, but the validation of these values then failed after connecting to a share. This may be due to a \"man-in-the-middle\" compromise attempt. |
| 0xB0007925 | 签名验证失败。%n%n错误:%7%n%n服务器名称: %6%n会话 ID:%3%n树 ID:%4%n消息 ID:%2%n命令: %1%n%n指导:%n此错误表示 SMB 消息在从服务器到客户端的横跨网络的传输过程中被修改。这可能是由于服务器上的会话结束、网络问题、第三方 SMB 服务器问题或“中间人”泄露尝试所致。 |
The signing validation failed.%n%nError:%7%n%nServer name: %6%nSession ID:%3%nTree ID:%4%nMessage ID:%2%nCommand: %1%n%nGuidance:%nThis error indicates that SMB messages are being modified in transit across the network from the server to the client. This may be due to the session ending on the server, a problem with the network, a problem with a third-party SMB server, or a \"man-in-the-middle\" compromise attempt. |
| 0xB0007926 | 客户端期望收到加密信息，但实际上收到了未加密信息。%n%n服务器名称: %6%n会话 ID:%3%n树 ID:%4%n消息 ID:%2%n命令: %1%n%n指导:%n此错误表示 SMB 消息在从服务器到客户端的横跨网络的传输过程中被修改。这可能是由于服务器上的会话结束、网络问题、第三方 SMB 服务器问题或“中间人”泄露尝试所致。 |
The client received an unencrypted message when encryption was expected.%n%nServer name: %6%nSession ID:%3%nTree ID:%4%nMessage ID:%2%nCommand: %1%n%nGuidance:%nThis error indicates that SMB messages are being modified in transit across the network from the server to the client. This may be due to the session ending on the server, a problem with the network, a problem with a third-party SMB server, or a \"man-in-the-middle\" compromise attempt. |
| 0xB0007927 | 无法解密已加密的 SMB 消息。%n%n错误:%7%n%n服务器名称: %6%n会话 ID:%3%n%n指导:%n客户端收到加密的 SMB 消息，但无法解密数据。这通常表示此通信来自不再存在的上一个会话。在客户端和服务器之间的网络上，加密标头可能也已损坏或遭到篡改。 |
Failed to decrypt an encrypted SMB message.%n%nError:%7%n%nServer name: %6%nSession ID:%3%n%nGuidance:%nThe client received an encrypted SMB message but cannot decrypt the data. This typically means that the communication came from a previous session that no longer exists. The encryption header may also have been damaged or tampered with on the network between the client and server. |
| 0xB0007928 | SMB 签名注册表值未配置为默认设置。%n%n默认注册表值:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"EnableSecuritySignature\"=dword:1%n已配置的注册表值:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"EnableSecuritySignature\"=dword:0%n%n指导:%n即使你可以禁用、启用或要求 SMB 签名，协商规则仍从 SMB 2 开始更改，并且不是所有组合的操作方式都类似于 SMB1。%n%nSMB2/SMB3 的有效行为是:%n需要的客户端和需要的服务器 = 已签名%n不需要的客户端和需要的服务器 = 已签名%n需要的服务器和不需要的客户端 = 客户端%n不需要的服务器和不需要的客户端 = 未签名%n%n若要求 SMB 加密，则无论设置如何，都不使用 SMB 签名。SMB 加密隐式提供与 SMB 签名相同的完整性保证。 |
The SMB Signing registry value is not configured with default settings.%n%nDefault Registry Value:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"EnableSecuritySignature\"=dword:1%nConfigured Registry Value:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"EnableSecuritySignature\"=dword:0%n%nGuidance:%nEven though you can disable, enable, or require SMB Signing, the negotiation rules changed starting with SMB2 and not all combinations operate like SMB1.%n%nThe effective behavior for SMB2/SMB3 is:%nClient Required and Server Required = Signed%nClient Not Required and Server Required = Signed%nServer Required and Client Not Required = Signed%nServer Not Required and Client Not Required = Not Signed%n%nWhen requiring SMB Encryption, SMB Signing is not used, regardless of settings. SMB Encryption implicitly provides the same integrity guarantees as SMB Signing. |
| 0xB0007929 | 拒绝了不安全的来宾登录。%n%n用户名: %2%n服务器名称: %4%n%n指导:%n此事件表明，服务器尝试以未经身份验证的来宾身份将用户登录，并且已被客户端拒绝。来宾登录不支持签名和加密等标准安全功能。因此，来宾登录容易遭受中间人攻击，这种攻击会在网络上公开敏感数据。Windows 会按默认禁用不安全的来宾登录。Microsoft 也不建议启用不安全的来宾登录。 |
Rejected an insecure guest logon.%n%nUser name: %2%nServer name: %4%n%nGuidance:%nThis event indicates that the server attempted to log the user on as an unauthenticated guest and was denied by the client. Guest logons do not support standard security features such as signing and encryption. As a result, guest logons are vulnerable to man-in-the-middle attacks that can expose sensitive data on the network. Windows disables insecure guest logons by default. Microsoft does not recommend enabling insecure guest logons. |
| 0xB000792A | 未使用默认设置配置 %1 注册表值。%n%n默认的注册表值:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"%1\"=dword:0%n配置的注册表值:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"%1\"=dword:%2%n%n指导:%n此事件表明管理员已启用不安全的来宾登录。当服务器以未经身份验证的来宾身份将用户登录(通常是为了对身份验证失败做出响应)时，就会发生不安全的来宾登录。来宾登录不支持签名和加密等标准安全功能。因此，允许来宾登录将使客户端容易遭受中间人攻击，这种攻击会在网络上公开敏感数据。Windows 会按默认禁用不安全的来宾登录。Microsoft 也不建议启用不安全的来宾登录。 |
The %1 registry value is not configured with default settings.%n%nDefault Registry Value:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"%1\"=dword:0%nConfigured Registry Value:%n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]%n\"%1\"=dword:%2%n%nGuidance:%nThis event indicates that an administrator has enabled insecure guest logons. An insecure guest logon occurs when a server logs the user on as an unauthenticated guest, typically in response to an authentication failure. Guest logons do not support standard security features such as signing and encryption. As a result, allowing guest logons makes the client vulnerable to man-in-the-middle attacks that can expose sensitive data on the network. Windows disables insecure guest logons by default. Microsoft does not recommend enabling insecure guest logons. |
| 0xB000792B | 在 %6 上重新进行身份验证后，相互身份验证意外丢失。%n用户 %10%nLogonID %4%n状态 %2%n |
Mutual authentication was unexpectedly lost after re-authenticating to %6%nUser %10%nLogonID %4%nStatus %2%n |
| 0xB0009C40 | 数据包(%4 个字节) |
Packet (%4 bytes) |
| 0xB0027793 | 无法重新连接持久句柄。%n%n错误: %7%n%nFileId: %2:%3%nCreateGUID: %4%n路径: %10%12%n%n原因: %8%n%n上一个重新连接错误: %13%n上一个重新连接原因: %14%n%n指导:%n持久句柄允许 Windows 文件服务器群集上存在透明故障转移。此事件有多种起因，它并不总是表示 SMB 存在问题。请检查联机文档，以了解疑难解答信息。 |
Failed to reconnect a persistent handle.%n%nError: %7%n%nFileId: %2:%3%nCreateGUID: %4%nPath: %10%12%n%nReason: %8%n%nPrevious reconnect error: %13%nPrevious reconnect reason: %14%n%nGuidance:%nA persistent handle allows transparent failover on Windows File Server clusters. This event has many causes and does not always indicate an issue with SMB. Review online documentation for troubleshooting information. |
| 0xB0027794 | 无法重新连接弹性句柄。%n%n错误: %7%n%n文件 ID: %2:%3%n路径: %10%12%n%n原因: %8。%n%n上一个重新连接错误: %13%n上一个重新连接原因: %14%n%n指导:%n弹性句柄为请求它的应用程序提供保证。此事件有多种起因，它并不总是表示 SMB 存在问题。请检查联机文档，以了解疑难解答信息。 |
Failed to reconnect a resilient handle.%n%nError: %7%n%nFileId: %2:%3%nPath: %10%12%n%nReason: %8.%n%nPrevious reconnect error: %13%nPrevious reconnect reason: %14%n%nGuidance:%nA resilient handle provides guarantees to applications requesting it. This event has many causes and does not always indicate an issue with SMB. Review online documentation for troubleshooting information. |
| 0xB0027853 | 无法建立网络连接。%n%n错误: %2%n%n服务器名称: %4%n服务器地址: %6%n实例名称: %9%n连接类型: %10%n%n指导:%n这表明基础网络或传输出现问题(例如 TCP/IP 出现问题)，而不是 SMB 有问题。使用 iWARP RDMA 适配器时会阻止 TCP 端口 445 或TCP 端口 5445 的防火墙也可能会导致此问题。 |
Failed to establish a network connection.%n%nError: %2%n%nServer name: %4%nServer address: %6%nInstance name: %9%nConnection type: %10%n%nGuidance:%nThis indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks TCP port 445, or TCP port 5445 when using an iWARP RDMA adapter, can also cause this issue. |
| 0xB0027855 | 客户端丢失了与服务器的会话。%n%n错误: %1%n%n服务器名称: %5%n会话 ID: %2%n%n指导:%n如果服务器是 Windows 故障转移群集文件服务器，则当文件共享在各群集节点之间移动时，会发生此消息。还可能发生反事件 30806，它表示已重新建立与服务器的会话。如果服务器不是故障转移群集，则很可能该服务器之前处于联机状态，但现在却无法通过网络访问。 |
The client lost its session to the server.%n%nError: %1%n%nServer name: %5%nSession ID: %2%n%nGuidance:%nIf the server is a Windows Failover Cluster file server, then this message occurs when the file share moves between cluster nodes. There should also be an anti-event 30806 indicating the session to the server was re-established. If the server is not a failover cluster, it is likely that the server was previously online, but it is now inaccessible over the network. |
| 0xB0027856 | 客户端重新建立了与服务器的会话。%n%n服务器名称: %5%n服务器地址: %7%n会话 ID: %2%n%n指导:%n如果存在上一个事件 30805，则可能会发生此事件，但是客户端在超时时间到期之前成功恢复了缓存的连接。 |
The client re-established its session to the server.%n%nServer name: %5%nServer address: %7%nSession ID: %2%n%nGuidance:%nYou should expect this event if there was a previous event 30805, but the client successfully resumed the cached connection before the timeout expired. |
| 0xB0027857 | 到共享的连接已丢失。%n%n错误: %1%n%n共享名称: %5%n会话 ID: %2%n树 ID: %3%n%n指导:%n如果服务器是 Windows 故障转移群集文件服务器，则当文件共享在各群集节点之间移动时，会发生此消息。还可能发生反事件 30808，它表示已重新建立与服务器的会话。如果服务器不是故障转移群集，则很可能该服务器之前处于联机状态，但现在却无法通过网络访问。 |
The connection to the share was lost.%n%nError: %1%n%nShare name: %5%nSession ID: %2%nTree ID: %3%n%nGuidance:%nIf the server is a Windows Failover Cluster file server, then this message occurs when the file share moves between cluster nodes. There should also be an anti-event 30808 indicating the session to the server was re-established. If the server is not a failover cluster, it is likely that the server was previously online, but it is now inaccessible over the network. |
| 0xB0027858 | 已重新建立与共享的连接。%n%n共享名称: %5%n服务器地址: %7%n会话 ID: %2%n树 ID: %3%n%n指导:%n如果存在上一个事件 30807，则可能会发生此事件，但是客户端在超时时间到期之前成功恢复了缓存的连接。 |
The connection to the share was re-established.%n%nShare name: %5%nServer address: %7%nSession ID: %2%nTree ID: %3%n%nGuidance:%nYou should expect this event if there was a previous event 30807, but the client successfully resumed the cached connection before the timeout expired. |
| 0xB0027863 | SMB 客户端收到了移至文件服务器群集上其他节点的请求。%n%n文件服务器群集名称: %4%n新文件服务器群集地址: %6%n%n指导:%n连续可用性(透明故障转移)正在使用中，客户端计算机即将在使用 TCP 并通过 RPC (首先联系端口 135，然后联系 1023 以上的终结点端口)的 SMB 见证请求之后移至其他节点。无需任何用户操作。 |
The SMB client received a request to move to a different node on a file server cluster.%n%nFile server cluster name: %4%nNew file server cluster address: %6%n%nGuidance:%nContinuous Availability (Transparent Failover) is in use and the client computer is going to move to a different node after an SMB witness request over RPC using TCP (first contacting port 135, then contacting an endpoint port above 1023). No user action is required. |
| 0xB0027864 | SMB 客户端已成功移至文件服务器群集上的其他节点。%n%n文件服务器群集名称: %4%n 新文件服务器群集地址: %6%n%n指导:%n连续可用性(透明故障转移)正在使用中，客户端计算机即将在使用 TCP 并通过 RPC (首先联系端口 135，然后联系 1023 以上的终结点端口)的 SMB 见证请求之后成功移至其他节点。无需任何用户操作。 |
The SMB client successfully moved to a different node on a file server cluster.%n%nFile server cluster name: %4%n New file server cluster address: %6%n%nGuidance:%nContinuous Availability (Transparent Failover) is in use and the client computer successfully moved to a different node after an SMB witness request over RPC using TCP (first contacting port 135, then contacting an endpoint port above 1023). No user action is required. |
| 0xB0027865 | SMB 客户端无法移至文件服务器群集上的其他节点。%n%n错误: %1%n%n文件服务器群集名称: %4%n%n指导:%n连续可用性(透明故障转移)正在使用中，客户端计算机无法在使用 TCP 并通过 RPC (首先联系端口 135，然后联系 1023 以上的终结点端口)的 SMB 见证请求之后移至其他节点。尝试连接到目标服务器失败，这通常是由于网络配置问题所致。例如，在目标节点的 IP 地址无法解析，或目标节点在防火墙后面，或不存在从客户端到节点的网络路由这几种情况下，可能会发生此问题。 |
The SMB client failed to move to a different node on a file server cluster.%n%nError: %1%n%nFile server cluster name: %4%n%nGuidance:%nContinuous Availability (Transparent Failover) is in use and the client computer failed to move to a different node after an SMB witness request over RPC using TCP (first contacting port 135, then contacting an endpoint port above 1023). The attempt to connect to the destination server failed, which is typically due to a network configuration issue. For example, this issue may occur if the destination node's IP address cannot be resolved, if the destination node is behind a firewall, or if there is no network route from the client to the node. |
| 0xB00278B4 | 已创建非持久句柄。%n%n文件 ID: %2:%3%nCreateGUID: %4%n路径: %10%12%n%n指导:%n服务器支持连续可用性(持久句柄)，并且创建句柄的请求已成功。但是服务器未授予持久性。你应当验证恢复密钥筛选器是否正在服务器上运行并且已连接到目标卷。 |
The handle was created without persistence.%n%nFile ID: %2:%3%nCreateGUID: %4%nPath: %10%12%n%nGuidance:%nThe server supports Continuous Availability (persistent handles) and the request to create the handle succeeded. However, the server did not grant persistence. You should verify that the Resume Key Filter is running on the server and is attached to the target volume. |
| 0xB00278B8 | 服务器不支持多通道。%n%n服务器名称: %2%n%n指导:%n客户端尝试使用 SMB 多通道，但是管理员已在服务器上禁用了多通道支持。这也可能是不支持多通道或禁用了多通道的非 Microsoft 文件服务器。你可以使用以下 Windows PowerShell cmdlet 在服务器上启用 SMB 多通道: Set-SmbServerConfiguration -EnableMultiChannel:$true。此事件不适用于 SMB 客户端的多通道设置，它是由 Set-SmbClientConfiguration Windows PowerShell cmdlet 控制的。无论启用还是禁用客户端多通道支持都不会影响服务器多通道支持。 |
The server does not support multichannel.%n%nServer name: %2%n%nGuidance:%nThe client attempted to use SMB Multichannel, but an administrator has disabled multichannel support on the server. This may also be a non-Microsoft file server that does not support multichannel or has multichannel disabled. You can enable SMB Multichannel on the server using this Windows PowerShell cmdlet: Set-SmbServerConfiguration -EnableMultiChannel:$true. This event does not apply to the multichannel settings of SMB client, which are controlled by the Set-SmbClientConfiguration Windows PowerShell cmdlet. Enabling or disabling client multichannel support does not affect server multichannel support. |
| 0xB00278B9 | 由于多通道约束注册表设置，客户端无法连接到服务器%n%n服务器名称: %2%n%n指导:%n客户端尝试使用 SMB 多通道，但是管理员已配置多通道支持，以阻止客户端上的多通道。你可以使用以下两个 Windows PowerShell cmdlet 来配置客户端上的 SMB 多通道: New-SmbMultichannelConstraint 和 Remove-SmbMultichannelConstraint。 |
The client cannot connect to the server due to a multichannel constraint registry setting.%n%nServer name: %2%n%nGuidance:%nThe client attempted to use SMB Multichannel, but an administrator has configured multichannel support to prevent multichannel on the client. You can configure SMB Multichannel on the client using the Windows PowerShell cmdlets: New-SmbMultichannelConstraint and Remove-SmbMultichannelConstraint. |
| 0xD0000001 | 活动 |
Active |
| 0xD0000002 | 已断开连接 |
Disconnected |
| 0xD0000003 | 已暂停 |
Suspended |
| 0xD0000004 | 正在构建 |
Construction in progress |
| 0xD0000005 | 正在恢复 |
Recovery in progress |
| 0xD0000006 | 正在断开连接 |
Disconnect in progress |
| 0xD0000007 | 正在失效 |
Invalidation in progress |
| 0xD0000008 | 无效 |
Invalid |
| 0xD0000009 | 已删除 |
Deleted |
| 0xD000000A | Tdi |
Tdi |
| 0xD000000B | Wsk |
Wsk |
| 0xD000000C | Rdma |
Rdma |
| 0xD000000D | 未指定原因 |
The reason is not specified |
| 0xD000000E | 无法解析服务器名称 |
The server name cannot be resolved |
| 0xD000000F | 设置套接字安全失败 |
Set socket security failed |
| 0xD0000010 | 连接尝试失败，出现了 IPSec 错误 |
The connection attempt failed with an IPSec error |
| 0xD0000011 | 连接尝试失败，出现了网络错误 |
The connection attempt failed with a network error |
| 0xD0000012 | 协商验证失败 |
The negotiate validation failed |
| 0xD0000013 | 由于交换过期，连接已断开 |
Disconnected because the exchange expired |
| 0xD0000014 | 由于存在网络断开连接指示，连接已断开 |
Disconnected because there was a network disconnect indication |
| 0xD0000015 | 由于目标服务器名称出现在无法访问的服务器缓存中，连接尝试失败 |
The connect attempt failed because the unreachable server cache contains the destination server name |
| 0xD0000016 | 尝试获取凭据句柄失败 |
An attempt to acquire a credential handle failed |
| 0xD0000017 | 尝试初始化安全性上下文失败 |
An attempt to initialize a security context failed |
| 0xD0000018 | 服务器无法完成会话设置请求 |
The server failed a session setup request |
| 0xD0000019 | 服务器已拒绝共享连接请求 |
The server denied the share connect request |
| 0xD000001A | 验证协商 FSCTL 请求失败 |
The validate negotiate FSCTL request failed |
| 0xD000001B | 无法重新连接句柄 |
Failed to reconnect the handle |
| 0xD000001C | 服务器拒绝创建请求 |
The server denied the create request |
| 0xD000001D | 请求已被客户端取消 |
The request was canceled by the client |
| 0xD000001E | 连接对象已被客户端暂停 |
The connection object was suspended by the client |
| 0xD000001F | The connection was disconnected by a user or application |
The connection was disconnected by a user or application |
| 0xD0000020 | The file handle was closed by the application |
The file handle was closed by the application |
| 0xD0000021 | Negotiate |
Negotiate |
| 0xD0000022 | Session setup |
Session setup |
| 0xD0000023 | Logoff |
Logoff |
| 0xD0000024 | Tree connect |
Tree connect |
| 0xD0000025 | Tree disconnect |
Tree disconnect |
| 0xD0000026 | Create |
Create |
| 0xD0000027 | Close |
Close |
| 0xD0000028 | Flush |
Flush |
| 0xD0000029 | Read |
Read |
| 0xD000002A | Write |
Write |
| 0xD000002B | Lock |
Lock |
| 0xD000002C | Ioctl |
Ioctl |
| 0xD000002D | Cancel |
Cancel |
| 0xD000002E | Echo |
Echo |
| 0xD000002F | Query directory |
Query directory |
| 0xD0000030 | Change notify |
Change notify |
| 0xD0000031 | Query info |
Query info |
| 0xD0000032 | Set info |
Set info |
| 0xD0000033 | Oplock break |
Oplock break |
| 0xD0000038 | Query information |
Query information |
| 0xD0000039 | Set information |
Set information |
| 0xD000003A | Query EA |
Query EA |
| 0xD000003B | Set EA |
Set EA |
| 0xD000003C | Flush buffers |
Flush buffers |
| 0xD000003D | Query volume information |
Query volume information |
| 0xD000003E | Set volume information |
Set volume information |
| 0xD000003F | Directory control |
Directory control |
| 0xD0000040 | File system control |
File system control |
| 0xD0000041 | Device control |
Device control |
| 0xD0000042 | Internal device control |
Internal device control |
| 0xD0000043 | Lock control |
Lock control |
| 0xD0000044 | Cleanup |
Cleanup |
| 0xD0000045 | Query security |
Query security |
| 0xD0000046 | Set security |
Set security |
| 0xD0000047 | 查询配额信息 |
Query quota information |
| 0xD0000048 | 设置配额信息 |
Set quota information |
| 0xD0000049 | 内部探测 I/O |
Internal probe I/O |
| 0xD000004A | 对称 |
Symmetric |
| 0xD000004B | 不对称 |
Asymmetric |