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
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 0003
SMB 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
NedPyle Hi Ned,
thanks for looking into this. The other Dell product, FluidFS, has the same issue. One of my colleagues spotted the new compression header using tcpdump when looking into this issue with the preview release of 1903 in April. We opened a case with Dell on the 30th April and we were told there wouldn't be any changes to FluidFS and we should open a case with Microsoft. Unfortunately we don't have a support agreement with Microsoft so just left feedback for the 1903 preview.
I haven't had any updates from Dell for a while so I'm not sure if they are looking at changing FluidFS, but now I have confirmation from you I can escalate it.
Thanks again.
- DarrenMillerJun 14, 2019Copper Contributor
Just a quick update on this - I have had confirmation from Dell that they are working on a fix for FluidFS.
- NedPyleJun 14, 2019Microsoft
DarrenMiller Awesome!
- tomattheJun 14, 2019Copper Contributor
DarrenMiller NedPyle thanks for moving this forward. We've also got a case opened with Microsoft now, but just requested it be closed per Ned. Also trying to work with our Dell reps to get this pushed along, if you reported the cased April 30th it seems like things should be moving a bit quicker then they are.
- adecroceJul 01, 2019Copper Contributor
Seems like they are still only pushing the workaround for the FluidFS. I haven't seen any patches released yet. DarrenMiller
- tomattheJul 03, 2019Copper Contributor
This is the last I got from Dell on the FluidFS side.
"ETA for a fix is not until the end of July. As such, I’m going to close out our case. However, I’ve created a reminder on 7/28 for me to check the status on this. I’ll send you a follow-up email then.
Have a great day!
Regards,
Chad"