This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 26%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Has anyone encountered this weird event?
Being puzzled why Microsoft IP resolves as our File Server. Please enlighten me, we've been seeing this event for a while now but not sure the context of this connection. 172.168.200.101 is a MS IP Address and our File Server is accessible only internally.
Server name: servername.domain.com
Server address: 172.168.200.101:445
Client address: client.ip
Instance name: \Device\LanmanRedirector
Connection type: Wsk
Guidance:
This 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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 65%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have the same, and it doesn't make any sense. Server1 is trying to reach a subnet on an other pair of servers (ServerA, ServerB) with a direct attached network cable (iWARP).
Server1 is not supposed to know anything about that configuration.
So, why is it complaining?
Failed to establish an SMB multichannel network connection.
Error: {Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.
Server name: VHV5
Server address: 192.168.120.69:445
Client address: 192.168.20.112
Instance name: \Device\LanmanRedirector
Connection type: TCPIP
Guidance:
This indicates a problem with the underlying network or transport, such as with TCP/IP or QUIC/UDP, and not with SMB. A firewall that blocks TCP port 445 or UDP port 443 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.