| 1 | SMB Client Shares |
SMB Client Shares |
| 3 | This counter set displays information about server shares that are being accessed by the client using SMB protocol version 2 or higher. |
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. |
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. |
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. |
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. |
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. |
The average number of bytes per read request. |
| 41 | Avg. Bytes/Write |
Avg. Bytes/Write |
| 43 | The average number of bytes per write request. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
The number of requests per second delayed based on insufficient credits for this share. |
| 0x30000000 | Info |
Info |
| 0x3000000B | Server Error |
Server Error |
| 0x3000000C | Cached Error |
Cached Error |
| 0x3000000D | Initialize Security Context Error |
Initialize Security Context Error |
| 0x3000000E | Security Signature Error |
Security Signature Error |
| 0x300000B4 | Start State |
Start State |
| 0x300000B5 | End State |
End State |
| 0x50000002 | Error |
Error |
| 0x50000003 | Warning |
Warning |
| 0x50000004 | Information |
Information |
| 0x50000005 | Verbose |
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 | Create SrvCall Error: %1 Location: %2 Context: %3 |
Create SrvCall Error: %1 Location: %2 Context: %3 |
| 0xB00000C9 | Session Setup Error: %1 Location: %2 Context: %3 |
Session Setup Error: %1 Location: %2 Context: %3 |
| 0xB000012D | Tree Connect Error: %1 Location: %2 Context: %3 |
Tree Connect Error: %1 Location: %2 Context: %3 |
| 0xB0000191 | Create VNetRoot Error: %1 Location: %2 Context: %3 |
Create VNetRoot Error: %1 Location: %2 Context: %3 |
| 0xB00001F5 | Create File Error: %1 Location: %2 Context: %3 |
Create File Error: %1 Location: %2 Context: %3 |
| 0xB00007D0 | Packet Fragment (%2 bytes) |
Packet Fragment (%2 bytes) |
| 0xB0004E21 | Transitioned to State: %1 Context: %2 |
Transitioned to State: %1 Context: %2 |
| 0xB0007597 | SMB exchange suspended: RxContext %1 Exchange %2 ListHead %3 |
SMB exchange suspended: RxContext %1 Exchange %2 ListHead %3 |
| 0xB0007598 | SMB exchange resumed: RxContext %1 Exchange %2 ExchangeState %3 ExchangeStatus %4 |
SMB exchange resumed: RxContext %1 Exchange %2 ExchangeState %3 ExchangeStatus %4 |
| 0xB0007599 | SMB buffer context suspended: BufferCtxt %1 Exchange %2 MidCharge %3 Window %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 buffer context resumed: BufferCtxt %1 Exchange %2 MidCharge %3 Window %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 window blocked: Window %1 HungSession %2 |
SMB Mid window blocked: Window %1 HungSession %2 |
| 0xB000759D | SMB rechunk multi-credit request: BufferCtxt %1 Exchange %2 MidCharge %3 Window %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 initialize Mid window: Server %2 Window %3 |
SMB initialize Mid window: Server %2 Window %3 |
| 0xB000759F | SMB Mid window state: Window %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 teardown Mid window: Server %2 Window %3 |
SMB teardown Mid window: Server %2 Window %3 |
| 0xB00075A1 | SMB copy data completion: Status %1 VcEndpoint %2 |
SMB copy data completion: Status %1 VcEndpoint %2 |
| 0xB00075A2 | SMB send completion: Status %1 VcEndpoint %2 |
SMB send completion: Status %1 VcEndpoint %2 |
| 0xB00075FB | WSK connect: SocketAddress %2 VcEndpoint %3 Socket %4 |
WSK connect: SocketAddress %2 VcEndpoint %3 Socket %4 |
| 0xB00075FC | WSK connect completion: VcEndpoint %1 Socket %2 Status %3 |
WSK connect completion: VcEndpoint %1 Socket %2 Status %3 |
| 0xB00075FD | WSK send: VcEndpoint %1 Socket %2 SendMdl %3 SendLength %4 |
WSK send: VcEndpoint %1 Socket %2 SendMdl %3 SendLength %4 |
| 0xB00075FE | WSK send completion: VcEndpoint %1 Socket %2 SendMdl %3 SendLength %4 Status %5 |
WSK send completion: VcEndpoint %1 Socket %2 SendMdl %3 SendLength %4 Status %5 |
| 0xB00075FF | WSK receive: VcEndpoint %1 Socket %2 ReceiveMdl %3 ReceiveLength %4 |
WSK receive: VcEndpoint %1 Socket %2 ReceiveMdl %3 ReceiveLength %4 |
| 0xB0007600 | WSK receive completion: VcEndpoint %1 Socket %2 ReceiveMdl %3 ReceiveLength %4 Status %5 |
WSK receive completion: VcEndpoint %1 Socket %2 ReceiveMdl %3 ReceiveLength %4 Status %5 |
| 0xB00076C1 | SMB session expired: SessionEntry %1 ServerName %3 |
SMB session expired: SessionEntry %1 ServerName %3 |
| 0xB00076C2 | SMB 3 part SPN reauth: SessionEntry %1 ServiceName %3 |
SMB 3 part SPN reauth: SessionEntry %1 ServiceName %3 |
| 0xB00076C3 | SMB reconnect durable open: Fcb %1 SrvOpen %2 |
SMB reconnect durable open: Fcb %1 SrvOpen %2 |
| 0xB00076C4 | SMB defer open: Fcb %1 SrvOpen %2 |
SMB defer open: Fcb %1 SrvOpen %2 |
| 0xB00076C5 | SMB undefer open: Fcb %1 SrvOpen %2 |
SMB undefer open: Fcb %1 SrvOpen %2 |
| 0xB00076C6 | SMB send[%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 receive: [%1] (Mid/Sid/Tid) (%2/%4/%5) Creds %6 Status %7 VcEndpoint %8 |
SMB receive: [%1] (Mid/Sid/Tid) (%2/%4/%5) Creds %6 Status %7 VcEndpoint %8 |
| 0xB00076C8 | SMB receive interim: [%1] (Mid/AsyncId/Sid/Tid) (%2/%3/%4/%5) Creds %6 Status %7 VcEndpoint %8 |
SMB receive interim: [%1] (Mid/AsyncId/Sid/Tid) (%2/%3/%4/%5) Creds %6 Status %7 VcEndpoint %8 |
| 0xB00076C9 | SMB receive async: [%1] (AsyncId/Sid/Tid) (%3/%4/%5) Creds %6 Status %7 VcEndpoint %8 |
SMB receive async: [%1] (AsyncId/Sid/Tid) (%3/%4/%5) Creds %6 Status %7 VcEndpoint %8 |
| 0xB00076CA | SMB registry key: %1 = %2 |
SMB registry key: %1 = %2 |
| 0xB0007725 | SMB update file info cache: RxContext %1 Fcb %2 FileName %4 |
SMB update file info cache: RxContext %1 Fcb %2 FileName %4 |
| 0xB0007726 | SMB fetch file info cache: RxContext %1 Fcb %2 FileName %4 Status %5 |
SMB fetch file info cache: RxContext %1 Fcb %2 FileName %4 Status %5 |
| 0xB0007727 | SMB invalidate file info cache: RxContext %1 Fcb %2 FileName %4 |
SMB invalidate file info cache: RxContext %1 Fcb %2 FileName %4 |
| 0xB0007728 | SMB update file not found cache: RxContext %1 Fcb %2 FileName %4 |
SMB update file not found cache: RxContext %1 Fcb %2 FileName %4 |
| 0xB0007729 | SMB fetch file not found cache: RxContext %1 Fcb %2 FileName %4 Result %5 |
SMB fetch file not found cache: RxContext %1 Fcb %2 FileName %4 Result %5 |
| 0xB000772A | SMB invalidate file not found cache: RxContext %1 Fcb %2 FileName %4 |
SMB invalidate file not found cache: RxContext %1 Fcb %2 FileName %4 |
| 0xB000772B | SMB populate dir cache: RxContext %1 Fcb %2 DirName %4 |
SMB populate dir cache: RxContext %1 Fcb %2 DirName %4 |
| 0xB000772C | SMB fetch dir cache: RxContext %1 Fcb %2 FileName %4 Status %5 |
SMB fetch dir cache: RxContext %1 Fcb %2 FileName %4 Status %5 |
| 0xB0007788 | Session %1 to %6 transitioned from [%2] to [%3] with Status %4 |
Session %1 to %6 transitioned from [%2] to [%3] with Status %4 |
| 0xB0007789 | Share connection %1 to %6 transitioned from [%2] to [%3] with Status %4 |
Share connection %1 to %6 transitioned from [%2] to [%3] with Status %4 |
| 0xB000778B | Open handle %1 to %10%12 transitioned from [%5] to [%6] with Status %7 |
Open handle %1 to %10%12 transitioned from [%5] to [%6] with Status %7 |
| 0xB0007795 | 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. |
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 | An invalid FSCTL_QUERY_NETWORK_INTERFACE_INFO response was sent by the server %2 |
An invalid FSCTL_QUERY_NETWORK_INTERFACE_INFO response was sent by the server %2 |
| 0xB00077EE | 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 |
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 | 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 |
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 | The client connected to the server %2 from the local IP address %4 to the remote IP address %6 over TCP transport successfully |
The client connected to the server %2 from the local IP address %4 to the remote IP address %6 over TCP transport successfully |
| 0xB00077F1 | The client connected to the server %2 from the local IP address %4 to the remote IP address %6 over RDMA transport successfully |
The client connected to the server %2 from the local IP address %4 to the remote IP address %6 over RDMA transport successfully |
| 0xB0007850 | 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. |
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%nError: %2%n%nServer name: %4 |
%1.%n%nError: %2%n%nServer name: %4 |
| 0xB0007853 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | Close request failed.%n%nError: %2%n%nPath: %4%6%n%nGuidance:%nA persistent handle (Continuous Availability) or a resilient handle failed to close. |
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 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). |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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%nError: %2%n%nSecurity status: %3%nUser name: %10%nLogon ID: %4%nSerrver name: %6 |
%1.%n%nError: %2%n%nSecurity status: %3%nUser name: %10%nLogon ID: %4%nSerrver name: %6 |
| 0xB0007919 | %1.%n%nError: %2%n%nSecurity status: %3%nUser name: %10%nLogon ID: %4%nServer name: %6%nPrincipal name: %8 |
%1.%n%nError: %2%n%nSecurity status: %3%nUser name: %10%nLogon ID: %4%nServer name: %6%nPrincipal name: %8 |
| 0xB000791A | 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. |
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 | 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. |
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 | The SMB client failed to connect to the share.%n%nError: %2%n%nPath: %4%6 |
The SMB client failed to connect to the share.%n%nError: %2%n%nPath: %4%6 |
| 0xB0007924 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | Mutual authentication was unexpectedly lost after re-authenticating to %6%nUser %10%nLogonID %4%nStatus %2%n |
Mutual authentication was unexpectedly lost after re-authenticating to %6%nUser %10%nLogonID %4%nStatus %2%n |
| 0xB0009C40 | Packet (%4 bytes) |
Packet (%4 bytes) |
| 0xB0027793 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 | 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. |
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 |
Active |
| 0xD0000002 | Disconnected |
Disconnected |
| 0xD0000003 | Suspended |
Suspended |
| 0xD0000004 | Construction in progress |
Construction in progress |
| 0xD0000005 | Recovery in progress |
Recovery in progress |
| 0xD0000006 | Disconnect in progress |
Disconnect in progress |
| 0xD0000007 | Invalidation in progress |
Invalidation in progress |
| 0xD0000008 | Invalid |
Invalid |
| 0xD0000009 | Deleted |
Deleted |
| 0xD000000A | Tdi |
Tdi |
| 0xD000000B | Wsk |
Wsk |
| 0xD000000C | Rdma |
Rdma |
| 0xD000000D | The reason is not specified |
The reason is not specified |
| 0xD000000E | The server name cannot be resolved |
The server name cannot be resolved |
| 0xD000000F | Set socket security failed |
Set socket security failed |
| 0xD0000010 | The connection attempt failed with an IPSec error |
The connection attempt failed with an IPSec error |
| 0xD0000011 | The connection attempt failed with a network error |
The connection attempt failed with a network error |
| 0xD0000012 | The negotiate validation failed |
The negotiate validation failed |
| 0xD0000013 | Disconnected because the exchange expired |
Disconnected because the exchange expired |
| 0xD0000014 | Disconnected because there was a network disconnect indication |
Disconnected because there was a network disconnect indication |
| 0xD0000015 | The connect attempt failed because the unreachable server cache contains the destination server name |
The connect attempt failed because the unreachable server cache contains the destination server name |
| 0xD0000016 | An attempt to acquire a credential handle failed |
An attempt to acquire a credential handle failed |
| 0xD0000017 | An attempt to initialize a security context failed |
An attempt to initialize a security context failed |
| 0xD0000018 | The server failed a session setup request |
The server failed a session setup request |
| 0xD0000019 | The server denied the share connect request |
The server denied the share connect request |
| 0xD000001A | The validate negotiate FSCTL request failed |
The validate negotiate FSCTL request failed |
| 0xD000001B | Failed to reconnect the handle |
Failed to reconnect the handle |
| 0xD000001C | The server denied the create request |
The server denied the create request |
| 0xD000001D | The request was canceled by the client |
The request was canceled by the client |
| 0xD000001E | The connection object was suspended by the client |
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 |
Query quota information |
| 0xD0000048 | Set quota information |
Set quota information |
| 0xD0000049 | Internal probe I/O |
Internal probe I/O |
| 0xD000004A | Symmetric |
Symmetric |
| 0xD000004B | Asymmetric |
Asymmetric |