Sungpill Han
asked on
SMB troubleshooting
I have a very weird problem with SMB shares, never have experienced this.
From some branch offices, Windows 10 users cannot access shares on Windows 2012 servers. But Windows 7 users don't have issue on accessing shares.
If the testing is done from another branch office, both Windows 7 and 10 users dont' have issue on accessing shares.
It seems it's obvious it's network issue, but as the same test is done while all ports open temporary in firewall, windows 10 users can't access the shares from the branch to the file server. We have man-in-the-middle device, Riverbed, but as I confirmed with the Riverbed maintainer, SMB Optimization is turned off.
I ran wireshark for analyzing, but it doesn't show much. The only thing shows is, the user side 'reset' session right after 3 way handshakes.
I drilled down SMB signing matters, it's not the issue, just to rule out it.
Both client and servers are set as singing allowed, but not required. In fact, Windows 10 users in the branch where the file servers are located, have no same issue accessing shares.
Is there any tool other than Wireshark which can analyze and troubleshoot SMB traffic in detail?
It seems network issue, but can't pinpoint the issue.
From some branch offices, Windows 10 users cannot access shares on Windows 2012 servers. But Windows 7 users don't have issue on accessing shares.
If the testing is done from another branch office, both Windows 7 and 10 users dont' have issue on accessing shares.
It seems it's obvious it's network issue, but as the same test is done while all ports open temporary in firewall, windows 10 users can't access the shares from the branch to the file server. We have man-in-the-middle device, Riverbed, but as I confirmed with the Riverbed maintainer, SMB Optimization is turned off.
I ran wireshark for analyzing, but it doesn't show much. The only thing shows is, the user side 'reset' session right after 3 way handshakes.
I drilled down SMB signing matters, it's not the issue, just to rule out it.
Both client and servers are set as singing allowed, but not required. In fact, Windows 10 users in the branch where the file servers are located, have no same issue accessing shares.
Is there any tool other than Wireshark which can analyze and troubleshoot SMB traffic in detail?
It seems network issue, but can't pinpoint the issue.
Zaheer Iqbal
Do you use any WAN optimisation at all ?
Sorry missed that I would turn off your riverbeds and test again.
Have see this issue with Riverbeds before.
ASKER
When you say, turn off? does it mean that there are more than only SMB Optimization?
We can't turn off the device, it's company security policy.
What in Riverbed did you find causes the issue?
We can't turn off the device, it's company security policy.
What in Riverbed did you find causes the issue?
Its been a while since I have started a new Job, it was definatley optimisation. I think we turned off optimisation at the central location ie DC and the issue was fixed. Eventually Riverbeds were removed from the network altogether after major line upgrades.
ASKER
Disabling SMB Optimization didn't do.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It seems like our Riverbed firmware is outdated, doesn't recognize SMB 3.11 for Windows 10.
The SMB Optimization option for SMB 3 is missing.
I can't confirm if this causes the issue, but will come back and post for other viewers in future.
The SMB Optimization option for SMB 3 is missing.
I can't confirm if this causes the issue, but will come back and post for other viewers in future.