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
update,:
it seems it may be specific to Dell Compellent Fluidity, so probably some sort of issue with their smb implementation.
It works fine with my home Synology Nas, and MS fileservers
But it has worked fine on previous win 10 versions
- kurganJun 11, 2019Copper Contributor
It works for me now, not sure if it is a windows update or update on fluidity that has fixed it.
- tomattheJun 11, 2019Copper Contributor
kurgan Which version of Windows are you on now? Start -> Run - > Winver
Dell has not released updated firmware for the Fluid FS as of 6/10/2019 that I'm aware of from my current open ticket.
"I don’t have any additional information to share regarding the SMBv3 and Windows 10 update 1903 issue. I’ll continue to monitor this and keep you informed."
- kurganJun 13, 2019Copper Contributor1903 -18362.30