We experienced a sudden drop in network share access in our environment today. Several of our users (100's) lost access to their day to day Data drive on their local office server. The issue was experienced across multiple office servers.
However the issue was sporadic and inconsistent, one user that couldn't access one share, the user next to them could but couldn't access the Data share on another office server.
We have multiple file servers each with multiple shares, our servers are running Server 2008 R2 and our workstations are Windows 7.
The issues was primarly experienced on the everyday 'Data' share, other shares on the same server were accessible. The folder was still accessible locally on the server and only appeared to be an issue for SMB connections.
We were able to identify a workaround by either restarting the client workstation which resolved the problem or by accessing the share using the FQDN instead of NETBIOS name.
We've troubleshooted name resolution and can confirm that Name resolution is working fine.
We've checked the Network provider order and this is also configured correctly on all file servers.
We've also ruled out the hotfix documented in KB2194664 as our servers and clients have a newer version of file mrxsmb10.sys and the hotfix is not applicable.
We performed a network capture on a file server that was receiving a connection attempt from a problem client and received the following results:
A successfull connection attempt to a share looks like this:
SMB2170
Tree Connect Request Tree: \\<SERVER>\IPC$
SMB2138
Tree Connect Response
SMB2222
Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Users
SMB2222
Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Users
TCP54
445→64647 [ACK] Seq=85 Ack=453 Win=256 Len=0
SMB2131
Ioctl Response, Error: STATUS_NOT_FOUND
SMB2172
Tree Connect Request Tree: \\<SERVER>\Users
SMB2138
Tree Connect Response
The connection attempt to the problem share looks like this:
SMB2170 Tree Connect Request Tree: \\<SERVER>\IPC$SMB2138 Tree Connect Response
SMB2220 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Users
SMB2220 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Users
TCP54 445→64647 [ACK] Seq=85 Ack=453 Win=256 Len=0
SMB2131 Ioctl Response, Error: STATUS_NOT_FOUND
SMB2131 Ioctl Response, Error: STATUS_NOT_FOUND
TCP60 64647→445 [ACK] Seq=449 Ack=239 Win=253 Len=0
SMB2220 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Data
SMB2131 Ioctl Response, Error: STATUS_NOT_FOUND
SMB2220 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Data
SMB2131 Ioctl Response, Error: STATUS_NOT_FOUND
SMB2220 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Data
SMB2131 Ioctl Response, Error: STATUS_NOT_FOUND
SMB2220 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Data
SMB2131 Ioctl Response, Error: STATUS_NOT_FOUND
SMB2220 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Data
SMB2131 Ioctl Response, Error: STATUS_NOT_FOUND
SMB2220 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Data
SMB2131 Ioctl Response, Error: STATUS_NOT_FOUND
We've raised a support ticket with Microsoft as this issue now has us completely at a loss and all current community suggestions for the 'The Network Name Cannot Be Found' error message have been thoroughly explored (name resolution, network provider order, KB2194664)
We'd appreciate any assistance anyone is able to offer
Kriss Milne | MCSE
*Please click 'Vote As Helpful' or 'Mark as Answer' if a post has helped you or answered your question*