Forum Discussion

kurgan's avatar
kurgan
Copper Contributor
Mar 22, 2019

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 ...
  • NedPyle's avatar
    NedPyle
    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 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

Dmorton's avatar
Dmorton
Copper Contributor
May 20, 2019
Any updates on this? Thanks
  • tomatthe's avatar
    tomatthe
    Copper Contributor
    May 28, 2019

    Dmorton 

     

    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.

    • itkpli's avatar
      itkpli
      Brass Contributor
      May 28, 2019

      tomatthe 

       

      I 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 534173
       
      For Compellent; it seems like you have to disable v3.
      • tomatthe's avatar
        tomatthe
        Copper Contributor
        May 28, 2019
        Thanks, 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?

Resources