| 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 Exchange 擱置: RxContext %1 Exchange %2 ListHead %3 |
SMB exchange suspended: RxContext %1 Exchange %2 ListHead %3 |
| 0xB0007598 | SMB Exchange 恢復: RxContext %1 Exchange %2 ExchangeState %3 ExchangeStatus %4 |
SMB exchange resumed: RxContext %1 Exchange %2 ExchangeState %3 ExchangeStatus %4 |
| 0xB0007599 | SMB 緩衝區內容擱置: BufferCtxt %1 Exchange %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 Exchange %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 Mid 視窗封鎖: 視窗 %1 HungSession %2 |
SMB Mid window blocked: Window %1 HungSession %2 |
| 0xB000759D | SMB 重新劃分多額度要求: BufferCtxt %1 Exchange %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 初始化 Mid 視窗: 伺服器 %2 視窗 %3 |
SMB initialize Mid window: Server %2 Window %3 |
| 0xB000759F | SMB Mid 視窗狀態: 視窗 %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 分割 Mid 視窗: 伺服器 %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 Creds %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) Creds %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) Creds %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) Creds %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%n欄位: %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 或 TCP 連接埠 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工作階段識別碼: %3%n樹狀目錄識別碼: %4%n訊息識別碼: %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指示: %nTCP/IP 繫結已新增至 SMB 用戶端的指定網路介面卡。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指示: %nTDI (NetBIOS) 繫結已新增至 SMB 用戶端的指定網路介面卡。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設定的啟動類型: DISABLED%n%n指示: %n為使用 SC.EXE 的用戶端停用 SMB2/SMB3，或編輯 Windows 登錄時，可能會發生此事件。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此事件表示系統管理員設定的「電腦設定\\系統管理範本\\網路\\Lanman 工作站\\加密套件順序」群組原則設定無效。在解決此錯誤之前，用戶端將使用預設的加密套件順序 \"%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工作階段識別碼: %3%n樹狀目錄識別碼: %4%n訊息識別碼: %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工作階段識別碼: %3%n樹狀目錄識別碼: %4%n訊息識別碼: %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工作階段識別碼: %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 簽署」，但交涉規則自 SMB2 起已有所變更，且並非所有的組合都可像 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%n登入識別碼 %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%n欄位: %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欄位: %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工作階段識別碼: %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工作階段識別碼: %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工作階段識別碼: %2%n樹狀目錄識別碼: %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工作階段識別碼: %2%n樹狀目錄識別碼: %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檔案識別碼: %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 |