大网数据广告活动
服务器运维问答

SMB Client Error

· 52CE 我爱测

Using HyperV Server 2016 with a Scale Out File Server (storing the VHDX files on the file server) makes the following error appearing in the hypervisor's Event Log (SMB Client - Connectivity): Failed to establish a network connec…

问题原文

原帖链接 · tomcsanyid · CC BY-SA 3.0

Using HyperV Server 2016 with a Scale Out File Server (storing the VHDX files on the file server) makes the following error appearing in the hypervisor's Event Log (SMB Client - Connectivity):

Failed to establish a network connection.

Error: {Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.

Server name: storage.DOMAIN
Server address: IP_OF_STORAGE2:445
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.

The environment feels unstable, virtual machines keep having I/O errors so the storage is indeed failing.

The environment looks like this:

  • HyperV 2016 Server with NIC teaming (dual 10G ethernet interfaces) with VLAN tagging
  • Dual storage head servers with HyperV 2016 Server and File Services enabled, combined into a Failover Cluster with the role Scale Out Fileserver (Storage1 and Storage 2). As storage backend we have an EMC storage unit hooked up via iSCSI to the head nodes.

Between the nodes we have a Cisco Nexus network running with active etherchannel/LACP on the teamed interfaces.

I'd be more than happy to provide any information if needed.

The only relevant hit I found while Googling was this technet thread without any solutions https://social.technet.microsoft.com/Forums/en-US/ef3e9243-5a22-4020-97a0-219595666cd7/smbclient-errors?forum=winserver8gen

已采纳解答

原帖链接 · tomcsanyid · CC BY-SA 3.0

We decided to take the suggestions we got here and modify our network based on them:

  • We added a second VLAN tagged interface to the LBFO-team which we used to enable SMB MultiChannel
  • Modified the team's loadbalancing algorithm to Address hash instead of the default Dynamic

We did these modifications a week ago, since then we don't see this error message, and in general the SMB Client event log has less messages.

Thank you!

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-05-12)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。