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

adecroce's avatar
adecroce
Copper Contributor

Seems like they are still only pushing the workaround for the FluidFS.  I haven't seen any patches released yet. DarrenMiller 

tomatthe's avatar
tomatthe
Copper Contributor
Jul 03, 2019

adecroce 

 

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"

  • adecroce's avatar
    adecroce
    Copper Contributor
    Jul 03, 2019

    tomatthe 

     

    Thanks for the follow up!

    • DarrenMiller's avatar
      DarrenMiller
      Copper Contributor
      Jul 05, 2019

      adecroce I heard back from Dell today - they told me a FluidFS fix should be out in early August.

      • fangludi1's avatar
        fangludi1
        Copper Contributor
        Aug 13, 2019

        Anyone knows when Dell will release the new firmware update for FluidFS to fix this SMB issue ? 

    • JBoehlke's avatar
      JBoehlke
      Copper Contributor
      Sep 06, 2019

      @Ned Pyle

      My Storage admin was looking over the notes for the latest Unity release (OE 5.0.0.0.5.116)  and told me this:

      "Not fixed in the current release.  Still references the workaround."

      Any updates from MS on this - or still DELL\EMC issue??

      • NedPyle's avatar
        NedPyle
        Icon for Microsoft rankMicrosoft
        Sep 06, 2019

        JBoehlke Hi. There's nothing for us to do here at MS, Dell was not following the SMB2 Negotiate specification. They need to change their behavior here like they did in other products mentioned in the thread.

Resources