Forum Discussion
Solved
W10-1903 UNC path failing 0x80070043
I can no longer access network shares through unc paths \\server\share I get the 0x80070043 "Network name cannot be found" error. I suspect that this is related to the removal of Homegroups? but ...
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
If you'll shoot me the case number, I'll include it in a ticket that I create with them.
@itkpli dwatson If you can do the same for me, I'll raise a case with EMC as well and include it
We are having the same issues. We are trying to access shares on Dell EMC FluidFS connected to compellent storage. I have raised a support call with Dell EMC and the response was
"The purpose of the preview releases (which are expected to have bugs) and the Microsoft Insider Program is to identify any potential bugs and report back to Microsoft so they can address them accordingly (sometimes they advise registry edits etc as temporary workarounds until the full release).
Have you tried addressing it with Microsoft yet so they can investigate further for you"
Hopefully Microsoft will look into the problem.
