Forum Discussion
W10-1903 UNC path failing 0x80070043
- Jun 13, 2019
Hi everyone. We got access to the Dell KB and see the issue in Dell/EMCs 'Unity' CIFS implementation.
From the DELL EMC KB attached to thread (below), the Unity SMB Server implementation is failing on the "SMB2_NETNAME_CONTEXT" and "SMB2_COMPRESSION_CAPABILITIES" we added in 1903. These were changes designed to add some new capabilities to SMB; we make some variant of these at most OS releases. If an SMB/CIFS server doesn't recognize capabilities, it should ignore them, not fail. Otherwise Dell would have to update their SMB implementation every time we released a new SMB capability that didn't also include a protocol dialect revision (like "SMB 3.1.2"), forever and ever.
Error Messages in the Unity c4_safe_ktrace.log:
sade:SMB: 3:[nas_serverx] Unrecognized SMB2 negotiate context type 0003
sade:SMB: 3:[nas_serverx] Unrecognized SMB2 negotiate context type 0003SMB client sends the compression context before the netname context, so the server encounters the compression context first. The Unity server would probably encounter the same problem with the netname context. Instead of failing when their SMB Server version doesn't support more advanced capabilities, it should be ignoring those capabilities. This is what Windows and other 3rd party SMB products do.
kurgan thanks for opening this techcommunity item, I'm sorry I didn't see it until now.
Ned Pyle | Principal Program Manager, MS | @nerdpyle on twitter
Same issues here with a Dell FluidFS compellent storage backed system. When you mentioned setting the max protocol to version 3.0.2 is that something the Dell support guys had to do? I only see the option to fully disable v3.
- itkpliMay 28, 2019Brass ContributorI think it's only possible to downgrade to 3.0.2 if your running on a Unity platform.
There is instructions provided for Unity in this kb: DTA 534173For Compellent; it seems like you have to disable v3.- tomattheMay 28, 2019Copper ContributorThanks, that makes better sense. Hopefully they don't leave the Compellent customers hanging.
I'm not able to get by the login piece to those KB articles.
In reading its still not clear to me if Dell is saying this is a Microsoft problem, or if Dell is actively working on a fix for their systems?- itkpliMay 28, 2019Brass Contributor
You should make a SR to Dell EMC about Compellent if you haven't done it yet.
Seems like Dell EMC are working to address it; at least on the Unity platform.
From the kb:
"Dell EMC is investigating an enhancement to address this issue. Dell EMC will update customers once more information on this enhancement becomes available to customers under current Dell EMC maintenance contracts."