Mar 22 2019 02:07 AM
Mar 22 2019 02:07 AM
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 surely it was not intended to break basic UNC functionality, or am I missing something?
Mar 22 2019 04:52 AM - edited Mar 22 2019 10:22 AM
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
Apr 15 2019 07:22 PM
Apr 24 2019 03:17 PM
Just downloaded and installed the Windows 10 Enterprise 1903 release from MSDN to test and this issue is still present. On latest build 18362.53. Our company's files shares are mostly hosted from Dell EMC/Unity. I have been able to confirm that Windows Server file shares and Nutanix Files shares are unaffected. Hopefully they will get this fixed by the RTM next month.
Apr 30 2019 11:06 AM - edited Apr 30 2019 11:20 AM
May 05 2019 11:09 PM - edited May 05 2019 11:13 PM
@ThiagoCardosoThe response from Dell/EMC so far has been to tell us to contact Microsoft.
While it might be an issue with Windows 10 1903 it's still something Dell/EMC should be concerned about because it will hurt their customers. I'll update here if I get any more info.
May 09 2019 12:27 AM
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.
May 09 2019 08:55 AM
Good news, everyone!
Dell/EMC has a work around for this issue. By setting the SMB Max Protocol version to 3.0.2 (down from 3.1.1) I am able to access shares again. Please start a Dell/EMC support ticket and quote SR 14282798.
Kudos to engineer Harsha Vardan for providing the work around!
May 09 2019 11:22 PM
@dwatsonI got the same info yesterday as well from a local EMC representative who had looked at your SR and it's good that they have a workaround.
However there are quite a lot of improvements in 3.1.1 compared to 3.02.