Make sure they are connected on the same network. In network sharing settings, enable 128 Bit encryption and allow network discovery. There are 7 services related to network sharing in services.msc. Also, both systems must run on the same build of Windows 10.

I think you're missing a part of this. We're talking about a DELL EMC box not running Windows. It's running Linux but SMB has worked without issue on all prior Windows 10 versions. Things broke with 1903

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.

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"

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.

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.

You should make a SR to Dell EMC about Compellent if you haven't done it yet.

Seems like Dell EMC are working to address it; at least on the Unity platform.

From the kb:

"Dell EMC is investigating an enhancement to address this issue. Dell EMC will update customers once more information on this enhancement becomes available to customers under current Dell EMC maintenance contracts."

Case opened with them on the Compellent side. To hear it from the rep I spoke with they just learned about this last week. For anyone else who using the FluidFS compellent setup the only current solution is to uncheck the v3 SMB option on the FluidFS.

"I’m following up on our case regarding the Windows 10 1903 update and SMB share access. At this time, our development team is still testing possible solutions. They are also investigating potential client-side workarounds. However, we currently only have the workaround of disabling SMBv3 on the FS itself."

@kurgan I am the owner of SMB. I have not received any reports of this issue from Dell, nor any similar symptoms from other customers using non-Dell products. The symptoms, workaround, & lack of other vendor reports suggests an issue with Dell's specific implementation of SMB 3.1.1.

Regardless, I am not going to punt this. If you have opened a support case on this issue with Microsoft, please private message me the SR #. I am following up with our contacts at Dell to find out if they've spoken to us about this.

Whenever an OEM says it's an MS problem and asks you to uninstall critical security updates and stop using the safest network protocols, I highly recommend you immediately open a Support Case with MS and that vendor and force that vendor to prove it, before de-securing your systems.

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.

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.

thanks for looking into this. The other Dell product, FluidFS, has the same issue. One of my colleagues spotted the new compression header using tcpdump when looking into this issue with the preview release of 1903 in April. We opened a case with Dell on the 30th April and we were told there wouldn't be any changes to FluidFS and we should open a case with Microsoft. Unfortunately we don't have a support agreement with Microsoft so just left feedback for the 1903 preview.

I haven't had any updates from Dell for a while so I'm not sure if they are looking at changing FluidFS, but now I have confirmation from you I can escalate it.

@DarrenMiller@Ned Pyle thanks for moving this forward. We've also got a case opened with Microsoft now, but just requested it be closed per Ned. Also trying to work with our Dell reps to get this pushed along, if you reported the cased April 30th it seems like things should be moving a bit quicker then they are.

"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.