SOLVED
Home

W10-1903 UNC path failing 0x80070043

%3CLINGO-SUB%20id%3D%22lingo-sub-382540%22%20slang%3D%22en-US%22%3EW10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382540%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20no%20longer%20access%20network%20shares%20through%20unc%20paths%20%5C%5Cserver%5Cshare%20I%20get%20the%200x80070043%20%22Network%20name%20cannot%20be%20found%22%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20suspect%20that%20this%20is%20related%20to%20the%20removal%20of%20Homegroups%3F%20but%20surely%20it%20was%20not%20intended%20to%20break%20basic%20UNC%20functionality%2C%20or%20am%20I%20missing%20something%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-452067%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-452067%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305974%22%20target%3D%22_blank%22%3E%40kurgan%3C%2FA%3E%26nbsp%3BAny%20luck%20figuring%20this%20out%3F%20Having%20the%20same%20problem%20over%20here%20with%20our%20Dell%20EMC%20UNITY%20SAN%20and%20it's%20killing%20me.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-382616%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382616%22%20slang%3D%22en-US%22%3E%3CP%3Eupdate%2C%3A%3C%2FP%3E%3CP%3Eit%20seems%20it%20may%20be%20specific%20to%20Dell%20Compellent%20Fluidity%2C%20so%20probably%20some%20sort%20of%20issue%20with%20their%20smb%20implementation.%3CBR%20%2F%3EIt%20works%20fine%20with%20my%20home%20Synology%20Nas%2C%20and%20MS%20fileservers%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20it%20has%20worked%20fine%20on%20previous%20win%2010%20versions%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-458077%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-458077%22%20slang%3D%22en-US%22%3EMake%20sure%20they%20are%20connected%20on%20the%20same%20network.%20In%20network%20sharing%20settings%2C%20enable%20128%20Bit%20encryption%20and%20allow%20network%20discovery.%20There%20are%207%20services%20related%20to%20network%20sharing%20in%20services.msc.%20Also%2C%20both%20systems%20must%20run%20on%20the%20same%20build%20of%20Windows%2010.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-461725%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-461725%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F321689%22%20target%3D%22_blank%22%3E%40Rohit_Sakhrani%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20you're%20missing%20a%20part%20of%20this.%20We're%20talking%20about%20a%20DELL%20EMC%20box%20not%20running%20Windows.%20It's%20running%20Linux%20but%20SMB%20has%20worked%20without%20issue%20on%20all%20prior%20Windows%2010%20versions.%20Things%20broke%20with%201903%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482342%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482342%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20downloaded%20and%20installed%20the%20Windows%2010%20Enterprise%201903%20release%20from%20MSDN%20to%20test%20and%20this%20issue%20is%20still%20present.%20On%20latest%20build%2018362.53.%20Our%20company's%20files%20shares%20are%20mostly%20hosted%20from%20Dell%20EMC%2FUnity.%20I%20have%20been%20able%20to%20confirm%20that%20Windows%20Server%20file%20shares%20and%20Nutanix%20Files%20shares%20are%20unaffected.%20Hopefully%20they%20will%20get%20this%20fixed%20by%20the%20RTM%20next%20month.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482743%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482743%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F326724%22%20target%3D%22_blank%22%3E%40k_perri%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20wanted%20to%20add%20that%20we%20also%20have%20problems%20using%20SMB%20with%201903%20and%20our%202%20Unity%20400%20(latest%20code).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20a%20big%20issue%20for%20us%20but%20I%20find%20it%20strange%20that%20I%20haven't%20found%20anything%20on%20the%20Internet%20about%20this%20except%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-485445%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-485445%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F327427%22%20target%3D%22_blank%22%3E%40itkpli%3C%2FA%3E%26nbsp%3BSame%20problem%20also%20here%20with%20Build%2019h1%20and%20Dell%20compellent%20FluidFS.%20no%20poblem%20with%20windows%20servers.%20does%20anyone%20else%20can%20test%20on%20a%20linux%20machine%20with%20standard%20samba%20%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-499300%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-499300%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F328156%22%20target%3D%22_blank%22%3E%40Sybux%3C%2FA%3EWe've%20now%20filed%20a%20support%20case%20with%20Dell%2FEMC%20about%20this.%3C%2FP%3E%3CP%3EWe'll%20see%20what%20they%20say%20about%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-505356%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-505356%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F327427%22%20target%3D%22_blank%22%3E%40itkpli%3C%2FA%3EI%20just%20subscribed%20to%20this%20post.%20I%20just%20wiped%20and%20reloaded%20my%201903%20machine%20thinking%20I%20had%20screwed%20it%20up.%20Good%20to%20know%20I'm%20not%20alone.%20I%20also%20cannot%20access%20EMC%20Unity%20shares.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20created%20this%20problem%20report%20in%20the%20feedback%20hub%20if%20you%20wish%20to%20upvote%20it%3A%20%26nbsp%3B%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FAA4y2ra%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FAA4y2ra%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EDan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-525819%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-525819%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F327427%22%20target%3D%22_blank%22%3E%40itkpli%3C%2FA%3Ewhat%20did%20Dell%20say%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20anyone%20fix%20this%20issue%20yet%3F%20we%20are%20on%20the%20same%20boat%20with%20Dell%20Unity%2C%20we%20will%20also%20open%20a%20case%20with%20Dell.%20Just%20want%20to%20know%20if%20anyone%20has%20any%20insights.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-533322%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-533322%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F333013%22%20target%3D%22_blank%22%3E%40ThiagoCardoso%3C%2FA%3EThe%20response%20from%20Dell%2FEMC%20so%20far%20has%20been%20to%20tell%20us%20to%20contact%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhile%20it%20might%20be%20an%20issue%20with%20Windows%2010%201903%20it's%20still%20something%20Dell%2FEMC%20should%20be%20concerned%20about%20because%20it%20will%20hurt%20their%20customers.%20I'll%20update%20here%20if%20I%20get%20any%20more%20info.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-534690%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-534690%22%20slang%3D%22en-US%22%3EIf%20you'll%20shoot%20me%20the%20case%20number%2C%20I'll%20include%20it%20in%20a%20ticket%20that%20I%20create%20with%20them.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-540669%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-540669%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22user-login%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F327427%22%20target%3D%22_blank%22%3E%40itkpli%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F290454%22%20target%3D%22_blank%22%3E%40dwatson%3C%2FA%3E%26nbsp%3BIf%20you%20can%20do%20the%20same%20for%20me%2C%20I'll%20raise%20a%20case%20with%20EMC%20as%20well%20and%20include%20it%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-551337%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-551337%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20having%20the%20same%20issues.%20We%20are%20trying%20to%20access%20shares%20on%20Dell%20EMC%20FluidFS%20connected%20to%20compellent%20storage.%20I%20have%20raised%20a%20support%20call%20with%20Dell%20EMC%20and%20the%20response%20was%3C%2FP%3E%3CP%3E%22The%20purpose%20of%20the%20preview%20releases%20(which%20are%20expected%20to%20have%20bugs)%20and%20the%20Microsoft%20Insider%20Program%20is%20to%20identify%20any%20potential%20bugs%20and%20report%20back%20to%20Microsoft%20so%20they%20can%20address%20them%20accordingly%20(sometimes%20they%20advise%20registry%20edits%20etc%20as%20temporary%20workarounds%20until%20the%20full%20release).%3C%2FP%3E%3CP%3EHave%20you%20tried%20addressing%20it%20with%20Microsoft%20yet%20so%20they%20can%20investigate%20further%20for%20you%22%3C%2FP%3E%3CP%3EHopefully%20Microsoft%20will%20look%20into%20the%20problem.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-552376%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552376%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F338908%22%20target%3D%22_blank%22%3E%40mrjonboy%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWow.%20Nice%20of%20Dell%20to%20explain%20the%20program%20to%20us!%26nbsp%3B%20Lucky%20for%20me%2C%20I%20have%20a%20WebEx%20this%20morning%20with%20one%20of%20their%20Engineers%20that%20seems%20to%20have%20an%20idea%20to%20at%20least%20try.%26nbsp%3B%20Fingers%20crossed%3B%20I'll%20report%20back.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-553433%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-553433%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20news%2C%20everyone!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDell%2FEMC%20has%20a%20work%20around%20for%20this%20issue.%20By%20setting%20the%20SMB%20Max%20Protocol%20version%20to%203.0.2%20(down%20from%203.1.1)%20I%20am%20able%20to%20access%20shares%20again.%20Please%20start%20a%20Dell%2FEMC%20support%20ticket%20and%20quote%20SR%2014282798.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKudos%20to%20engineer%20Harsha%20Vardan%20for%20providing%20the%20work%20around!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-556656%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-556656%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F290454%22%20target%3D%22_blank%22%3E%40dwatson%3C%2FA%3EI%20got%20the%20same%20info%20yesterday%20as%20well%20from%20a%20local%20EMC%20representative%20who%20had%20looked%20at%20your%20SR%20and%20it's%20good%20that%20they%20have%20a%20workaround.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20there%20are%20quite%20a%20lot%20of%20improvements%20in%203.1.1%20compared%20to%203.02.%3C%2FP%3E%3CP%3EMore%20info%3A%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fjosebda%2F2015%2F05%2F05%2Fwhats-new-in-smb-3-1-1-in-the-windows-server-2016-technical-preview-2%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWhat%E2%80%99s%20new%20in%20SMB%203.1.1%20in%20the%20Windows%20Server%202016%20Technical%20Preview%202%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-558766%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-558766%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F327427%22%20target%3D%22_blank%22%3E%40itkpli%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAgreed%20on%20all%20counts.%20At%20least%20we're%20not%20dead%20in%20the%20water%2C%20though%2C%20while%20we%20wait%20for%20a%20fix.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-562623%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-562623%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F290454%22%20target%3D%22_blank%22%3E%40dwatson%3C%2FA%3E%26nbsp%3BPresumably%20this%20fix%20is%20for%20Unity%3F%3C%2FP%3E%3CP%3EWe%20still%20have%20the%20same%20problem%20with%20FluidFS%20and%20Dell%20have%20told%20us%20it%20is%20Microsoft's%20problem.%3C%2FP%3E%3CP%3EHas%20anybody%20found%20a%20fix%20for%20FluidFS%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-563322%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-563322%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F290454%22%20target%3D%22_blank%22%3E%40dwatson%3C%2FA%3EMany%20thanks%20for%20this.%20This%20has%20fixed%20my%20issue%20for%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-563391%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-563391%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20answering%20my%20own%20question%20-%20it%20looks%20like%20completely%20disabling%20SMBv3%20on%20FluidFS%20is%20a%20workaround.%26nbsp%3B%20Not%20great%2C%20but%20at%20least%20it%20gets%20things%20working%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-617709%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-617709%22%20slang%3D%22en-US%22%3EAny%20updates%20on%20this%3F%20Thanks%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-651216%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-651216%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F339355%22%20target%3D%22_blank%22%3E%40Dmorton%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDell%20EMC%20just%20released%20an%20official%20KB%20about%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22DTA%20534173%3A%20Dell%20EMC%20Unity%3A%20Windows%20users%20may%20be%20unable%20to%20access%20Common%20Internet%20File%20System%20(CIFS)%20shares%20when%20Server%20Message%20Block%20(SMB)%203.1.1%20is%20running%20which%20may%20result%20in%20potential%20data%20unavailability%22%20href%3D%22https%3A%2F%2Femcservice.force.com%2FCustomersPartners%2FkA43a00000003w4CAA%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDTA%20534173%3A%20Dell%20EMC%20Unity%3A%20Windows%20users%20may%20be%20unable%20to%20access%20Common%20Internet%20File%20System%20(CIFS)%20shares%20when%20Server%20Message%20Block%20(SMB)%203.1.1%20is%20running%20which%20may%20result%20in%20potential%20data%20unavailability%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20still%20recommend%20to%20downgrade%20to%203.0.2%20or%20to%20go%20back%20to%201809%20on%20the%20clients%20but%20it%20says%20that%20they%20are%20investigating%20an%20enchancement%20to%20adress%20this%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-652201%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-652201%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F339355%22%20target%3D%22_blank%22%3E%40Dmorton%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20issues%20here%20with%20a%20Dell%20FluidFS%20compellent%20storage%20backed%20system.%26nbsp%3B%20When%20you%20mentioned%20setting%20the%20max%20protocol%20to%20version%203.0.2%20is%20that%20something%20the%20Dell%20support%20guys%20had%20to%20do%3F%26nbsp%3B%20I%20only%20see%20the%20option%20to%20fully%20disable%20v3.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-652267%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-652267%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CFONT%3EI%20think%20it's%20only%20possible%20to%20downgrade%20to%203.0.2%20if%20your%20running%20on%20a%20Unity%20platform.%3CBR%20%2F%3EThere%20is%20instructions%20provided%20for%20Unity%20in%20this%20kb%3A%26nbsp%3B%3CA%20title%3D%22DTA%20534173%22%20href%3D%22https%3A%2F%2Femcservice.force.com%2FCustomersPartners%2FkA43a00000003w4CAA%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDTA%20534173%3C%2FA%3E%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EFor%20Compellent%3B%20it%20seems%20like%20you%20have%20to%20disable%20v3.%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-652287%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-652287%22%20slang%3D%22en-US%22%3EThanks%2C%20that%20makes%20better%20sense.%20Hopefully%20they%20don't%20leave%20the%20Compellent%20customers%20hanging.%3CBR%20%2F%3E%3CBR%20%2F%3EI'm%20not%20able%20to%20get%20by%20the%20login%20piece%20to%20those%20KB%20articles.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20reading%20its%20still%20not%20clear%20to%20me%20if%20Dell%20is%20saying%20this%20is%20a%20Microsoft%20problem%2C%20or%20if%20Dell%20is%20actively%20working%20on%20a%20fix%20for%20their%20systems%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-652325%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-652325%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20should%20make%20a%20SR%20to%20Dell%20EMC%20about%20Compellent%20if%20you%20haven't%20done%20it%20yet.%3C%2FP%3E%3CP%3ESeems%20like%20Dell%20EMC%20are%20working%20to%20address%20it%3B%20at%20least%20on%20the%20Unity%20platform.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20the%20kb%3A%3C%2FP%3E%3CP%3E%3CEM%3E%22Dell%20EMC%20is%20investigating%20an%20enhancement%20to%20address%20this%20issue.%20Dell%20EMC%20will%20update%20customers%20once%20more%20information%20on%20this%20enhancement%20becomes%20available%20to%20customers%20under%20current%20Dell%20EMC%20maintenance%20contracts.%22%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-652657%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-652657%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F327427%22%20target%3D%22_blank%22%3E%40itkpli%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECase%20opened%20with%20them%20on%20the%20Compellent%20side.%26nbsp%3B%20To%20hear%20it%20from%20the%20rep%20I%20spoke%20with%20they%20just%20learned%20about%20this%20last%20week.%26nbsp%3B%20For%20anyone%20else%20who%20using%20the%20FluidFS%20compellent%20setup%20the%20only%20current%20solution%20is%20to%20uncheck%20the%20v3%20SMB%20option%20on%20the%20FluidFS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20anyone%20wanted%20the%20case%20toe%20reference%2C%3C%2FP%3E%3CP%3ESR%20991311217%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-655396%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-655396%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20engineering%20team%20at%20EMC%20are%20working%20on%20providing%20a%20resolution%20or%20hotfix%20in%20the%20next%20patch.%3C%2FP%3E%3CP%3EI've%20also%20got%20permission%20from%20EMC%20to%20post%20their%20official%20document%20about%20Unity%20and%20Windows%201903%20here.%3C%2FP%3E%3CP%3EThe%20.pdf%20includes%20instructions%20for%20the%20workaround%20to%20downgrade%20to%203.0.2%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20see%20the%20attached%20document.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-664736%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-664736%22%20slang%3D%22en-US%22%3EFrom%20Dell%20on%20the%20Compellent%20end%20of%20things%20as%20of%206%2F2%2F2019%3CBR%20%2F%3E%3CBR%20%2F%3E%22I%E2%80%99m%20following%20up%20on%20our%20case%20regarding%20the%20Windows%2010%201903%20update%20and%20SMB%20share%20access.%20At%20this%20time%2C%20our%20development%20team%20is%20still%20testing%20possible%20solutions.%20They%20are%20also%20investigating%20potential%20client-side%20workarounds.%20However%2C%20we%20currently%20only%20have%20the%20workaround%20of%20disabling%20SMBv3%20on%20the%20FS%20itself.%22%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666109%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666109%22%20slang%3D%22en-US%22%3E%3CP%3Ebetter%20get%20used%20to%20typing%20%2F%2F192.168.0.xx%20on%20new%20shortcut%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305974%22%20target%3D%22_blank%22%3E%40kurgan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683773%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683773%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20works%20for%20me%20now%2C%20not%20sure%20if%20it%20is%20a%20windows%20update%20or%20update%20on%20fluidity%20that%20has%20fixed%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-684803%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-684803%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305974%22%20target%3D%22_blank%22%3E%40kurgan%3C%2FA%3E%26nbsp%3B%20Which%20version%20of%20Windows%20are%20you%20on%20now%3F%26nbsp%3B%20Start%20-%26gt%3B%20Run%20-%20%26gt%3B%20Winver%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDell%20has%20not%20released%20updated%20firmware%20for%20the%20Fluid%20FS%20as%20of%206%2F10%2F2019%20that%20I'm%20aware%20of%20from%20my%20current%20open%20ticket.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22I%20don%E2%80%99t%20have%20any%20additional%20information%20to%20share%20regarding%20the%20SMBv3%20and%20Windows%2010%20update%201903%20issue.%20I%E2%80%99ll%20continue%20to%20monitor%20this%20and%20keep%20you%20informed.%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-689425%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-689425%22%20slang%3D%22en-US%22%3E1903%20-18362.30%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-689461%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-689461%22%20slang%3D%22en-US%22%3Eactually%20just%20updated%20to%2018362.175%20a%20minute%20ago%2C%20still%20works%20fine%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-689530%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-689530%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20just%20tried%20the%20latest%20update%20(18362.175)%20and%20it%20still%20does%20not%20work%20with%20FluidFS%20for%20me%20with%20SMBv3%20turned%20on.%3C%2FP%3E%3CP%3EThe%20message%20I%20got%20from%20my%20case%20with%20Dell%20was%20they%20weren't%20planning%20on%20making%20any%20changes%20to%20FluidFS%20and%20were%20leaving%20Microsoft%20to%20fix%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-689614%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-689614%22%20slang%3D%22en-US%22%3E%3CP%3EOkay%20followed%20up%20on%20it%2C%20our%20IT%20department%20has%20disabled%20smb3%20for%20now%20to%20fix%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-690865%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-690865%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305974%22%20target%3D%22_blank%22%3E%40kurgan%3C%2FA%3E%26nbsp%3BI%20am%20the%20owner%20of%20SMB.%20I%20have%20not%20received%20any%20reports%20of%20this%20issue%20from%20Dell%2C%20nor%20any%20similar%20symptoms%20from%20other%20customers%20using%20non-Dell%20products.%20The%20symptoms%2C%20workaround%2C%20%26amp%3B%20lack%20of%20other%20vendor%20reports%20suggests%20an%20issue%20with%20Dell's%20specific%20implementation%20of%20SMB%203.1.1.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegardless%2C%20I%20am%20not%20going%20to%20punt%20this.%20If%20you%20have%20opened%20a%20support%20case%20on%20this%20issue%20with%20Microsoft%2C%20please%20private%20message%20me%20the%20SR%20%23.%20I%20am%20following%20up%20with%20our%20contacts%20at%20Dell%20to%20find%20out%20if%20they've%20spoken%20to%20us%20about%20this.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhenever%20an%20OEM%20says%20it's%20an%20MS%20problem%20and%20asks%20you%20to%20uninstall%20critical%20security%20updates%20and%20stop%20using%20the%20safest%20network%20protocols%2C%20I%20%3CEM%3Ehighly%20recommend%26nbsp%3B%3C%2FEM%3Eyou%20immediately%20open%20a%20Support%20Case%20with%20MS%20and%20that%20vendor%20and%20force%20that%20vendor%20to%20prove%20it%2C%20before%20de-securing%20your%20systems.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-690867%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-690867%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305974%22%20target%3D%22_blank%22%3E%40kurgan%3C%2FA%3E%26nbsp%3BI%20am%20the%20owner%20of%20SMB.%20I%20have%20not%20received%20any%20reports%20of%20this%20issue%20from%20Dell%2C%20nor%20any%20similar%20symptoms%20from%20other%20customers%20using%20non-Dell%20products.%20The%20symptoms%2C%20workaround%2C%20%26amp%3B%20lack%20of%20other%20vendor%20reports%20suggests%20an%20issue%20with%20Dell's%20specific%20implementation%20of%20SMB%203.1.1.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegardless%2C%20I%20am%20not%20going%20to%20punt%20this.%20If%20you%20have%20opened%20a%20support%20case%20on%20this%20issue%20with%20Microsoft%2C%20please%20private%20message%20me%20the%20SR%20%23.%20I%20am%20following%20up%20with%20our%20contacts%20at%20Dell%20to%20find%20out%20if%20they've%20spoken%20to%20us%20about%20this.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhenever%20an%20OEM%20says%20it's%20an%20MS%20problem%20and%20asks%20you%20to%20uninstall%20critical%20security%20updates%20and%20stop%20using%20the%20safest%20network%20protocols%2C%20I%20%3CEM%3Ehighly%20recommend%26nbsp%3B%3C%2FEM%3Eyou%20immediately%20open%20a%20Support%20Case%20with%20MS%20and%20that%20vendor%20and%20force%20that%20vendor%20to%20prove%20it%2C%20before%20de-securing%20your%20systems.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENed%20Pyle%20%7C%20Principal%20Program%20Manager%2C%20MS%20%7C%20%40nerdpyle%20on%20twitter%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-691314%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-691314%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone.%20We%20got%20access%20to%20the%20Dell%20KB%20and%20see%20the%20issue%20in%20Dell%2FEMCs%20'Unity'%20CIFS%20implementation.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20the%20DELL%20EMC%20KB%20attached%20to%20thread%20(below)%2C%20the%20Unity%20SMB%20Server%20implementation%20is%20failing%20on%20the%20%22SMB2_NETNAME_CONTEXT%22%20and%20%22SMB2_COMPRESSION_CAPABILITIES%22%20we%20added%20in%201903.%20These%20were%20changes%20designed%20to%20add%20some%20new%20capabilities%20to%20SMB%3B%20we%20make%20some%20variant%20of%20these%20at%20most%20OS%20releases.%20If%20an%20SMB%2FCIFS%20server%20doesn't%20recognize%20capabilities%2C%20it%20should%20%3CSTRONG%3Eignore%20them%3C%2FSTRONG%3E%2C%20not%20fail.%20Otherwise%20Dell%20would%20have%20to%20update%20their%20SMB%20implementation%20every%20time%20we%20released%20a%20new%20SMB%20capability%20that%20didn't%20also%20include%20a%20protocol%20dialect%20revision%20(like%20%22SMB%203.1.2%22)%2C%20forever%20and%20ever.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EError%20Messages%20in%20the%20Unity%20c4_safe_ktrace.log%3A%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3Esade%3ASMB%3A%203%3A%5Bnas_serverx%5D%20Unrecognized%20SMB2%20negotiate%20context%20type%200003%3CBR%20%2F%3Esade%3ASMB%3A%203%3A%5Bnas_serverx%5D%20Unrecognized%20SMB2%20negotiate%20context%20type%200003%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESMB%20client%20sends%20the%20compression%20context%20before%20the%20netname%20context%2C%20so%20the%20server%20encounters%20the%20compression%20context%20first.%20The%20Unity%20server%20would%20probably%20encounter%20the%20same%20problem%20with%20the%20netname%20context.%20Instead%20of%20failing%20when%20their%20SMB%20Server%20version%20doesn't%20support%20more%20advanced%20capabilities%2C%20it%20should%20be%20ignoring%20those%20capabilities.%20This%20is%20what%20Windows%20and%20other%203rd%20party%20SMB%20products%20do.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305974%22%20target%3D%22_blank%22%3E%40kurgan%3C%2FA%3E%26nbsp%3Bthanks%20for%20opening%20this%20techcommunity%20item%2C%20I'm%20sorry%20I%20didn't%20see%20it%20until%20now.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENed%20Pyle%20%7C%20Principal%20Program%20Manager%2C%20MS%20%7C%20%40nerdpyle%20on%20twitter%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-691935%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-691935%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F52778%22%20target%3D%22_blank%22%3E%40Ned%20Pyle%3C%2FA%3E%26nbsp%3BHi%20Ned%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%20for%20looking%20into%20this.%26nbsp%3B%20The%20other%20Dell%20product%2C%20FluidFS%2C%20has%20the%20same%20issue.%26nbsp%3B%20One%20of%20my%20colleagues%20spotted%20the%20new%20compression%20header%20using%20tcpdump%20when%20looking%20into%20this%20issue%20with%20the%20preview%20release%20of%201903%20in%20April.%26nbsp%3B%20We%20opened%20a%20case%20with%20Dell%20on%20the%2030th%20April%20and%20we%20were%20told%20there%20wouldn't%20be%20any%20changes%20to%20FluidFS%20and%20we%20should%20open%20a%20case%20with%20Microsoft.%26nbsp%3B%20Unfortunately%20we%20don't%20have%20a%20support%20agreement%20with%20Microsoft%20so%20just%20left%20feedback%20for%20the%201903%20preview.%3C%2FP%3E%3CP%3EI%20haven't%20had%20any%20updates%20from%20Dell%20for%20a%20while%20so%20I'm%20not%20sure%20if%20they%20are%20looking%20at%20changing%20FluidFS%2C%20but%20now%20I%20have%20confirmation%20from%20you%20I%20can%20escalate%20it.%3C%2FP%3E%3CP%3EThanks%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-692113%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-692113%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20a%20quick%20update%20on%20this%20-%20I%20have%20had%20confirmation%20from%20Dell%20that%20they%20are%20working%20on%20a%20fix%20for%20FluidFS.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-692533%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-692533%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F341189%22%20target%3D%22_blank%22%3E%40DarrenMiller%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F52778%22%20target%3D%22_blank%22%3E%40Ned%20Pyle%3C%2FA%3E%26nbsp%3Bthanks%20for%20moving%20this%20forward.%26nbsp%3B%20We've%20also%20got%20a%20case%20opened%20with%20Microsoft%20now%2C%20but%20just%20requested%20it%20be%20closed%20per%20Ned.%26nbsp%3B%20Also%20trying%20to%20work%20with%20our%20Dell%20reps%20to%20get%20this%20pushed%20along%2C%20if%20you%20reported%20the%20cased%20April%2030th%20it%20seems%20like%20things%20should%20be%20moving%20a%20bit%20quicker%20then%20they%20are.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-693177%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-693177%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3B%20if%20Dell%20pushes%20back%20please%20feel%20free%20to%20drop%20my%20name%2C%20I'll%20be%20happy%20to%20chat%20with%20them%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-693181%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-693181%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F341189%22%20target%3D%22_blank%22%3E%40DarrenMiller%3C%2FA%3E%26nbsp%3BAwesome!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-710486%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-710486%22%20slang%3D%22en-US%22%3EHi%20everyone%2C%3CBR%20%2F%3E%3CBR%20%2F%3Edo%20you%20have%20any%20update%20%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-717142%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-717142%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eon%20my%20side%20we%20have%20a%20UnityVSA%20and%20they%20confirm%20its%20fixed%20on%20the%20latest%20release%20(not%20public)%26nbsp%3B%3C%2FP%3E%3CP%3E4.5.1.0.6.136%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eso%20now%20it%20maybe%20available%20for%20other%20Filer%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-731438%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-731438%22%20slang%3D%22en-US%22%3E%3CP%3ESeems%20like%20they%20are%20still%20only%20pushing%20the%20workaround%20for%20the%20FluidFS.%26nbsp%3B%20I%20haven't%20seen%20any%20patches%20released%20yet.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F341189%22%20target%3D%22_blank%22%3E%40DarrenMiller%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-736398%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-736398%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F362429%22%20target%3D%22_blank%22%3E%40adecroce%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20the%20last%20I%20got%20from%20Dell%20on%20the%20FluidFS%20side.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22ETA%20for%20a%20fix%20is%20not%20until%20the%20end%20of%20July.%20As%20such%2C%20I%E2%80%99m%20going%20to%20close%20out%20our%20case.%20However%2C%20I%E2%80%99ve%20created%20a%20reminder%20on%207%2F28%20for%20me%20to%20check%20the%20status%20on%20this.%20I%E2%80%99ll%20send%20you%20a%20follow-up%20email%20then.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20a%20great%20day!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EChad%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-736411%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-736411%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20follow%20up!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-739198%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-739198%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F362429%22%20target%3D%22_blank%22%3E%40adecroce%3C%2FA%3E%26nbsp%3BI%20heard%20back%20from%20Dell%20today%20-%20they%20told%20me%20a%20FluidFS%20fix%20should%20be%20out%20in%20early%20August.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-802265%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-802265%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20knows%20when%20Dell%20will%20release%20the%20new%20firmware%20update%20for%20FluidFS%20to%20fix%20this%20SMB%20issue%20%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-802555%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-802555%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F347950%22%20target%3D%22_blank%22%3E%40fangludi1%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20from%20Dell%20on%20Aug%209th.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22ETA%20is%20still%20%E2%80%9CAugust%E2%80%9D.%20No%20date%20available%20yet.%20I%E2%80%99ll%20check%20again%20next%20Friday.%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-811036%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-811036%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate%20as%20of%208%2F19%2F2019.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20current%20ETA%20for%20MR640%20(and%20the%20SBM%20fix)%20has%20been%20changed%20from%20August%20to%20open.%20However%2C%20I%20anticipate%20it%20being%20release%20in%20the%20next%20few%20weeks.%20I%E2%80%99ll%20continue%20to%20check%20the%20status%20on%20this%20and%20send%20you%20an%20update%20every%20week%20or%20so.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-811088%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-811088%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20update%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-830929%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-830929%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3BHas%20there%20been%20an%20update%20on%20MR640%20from%20DELL%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-831376%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-831376%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F400971%22%20target%3D%22_blank%22%3E%40stevecookMOL%3C%2FA%3E%26nbsp%3B%20%26nbsp%3B1903%20is%20started%20to%20end%20up%20on%20machines%20here%2C%20and%20this%20is%20quickly%20becoming%20a%20rather%20large%20problem%20for%20us.%26nbsp%3B%20I%20really%20don't%20want%20to%20disable%20v3%20completely%2C%20but%20running%20out%20of%20options.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E8%2F26%2F2019%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20morning%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20change%20yet%20in%20the%20current%20status%20for%20release.%20It%20is%20still%20in%20testing%20and%20does%20not%20have%20a%20firm%20ETA.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EChad%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-841018%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-841018%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F52778%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%40Ned%20Pyle%3C%2FA%3E%3C%2FP%3E%3CP%3EMy%20Storage%20admin%20was%20looking%20over%20the%20notes%20for%20the%20latest%20Unity%20release%20(%3CSPAN%3EOE%205.0.0.0.5.116)%26nbsp%3B%3C%2FSPAN%3Eand%20told%20me%20this%3A%3C%2FP%3E%3CP%3E%3CSPAN%3E%22Not%20fixed%20in%20the%20current%20release.%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EStill%20references%20the%20workaround.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAny%20updates%20from%20MS%20on%20this%20-%20or%20still%20DELL%5CEMC%20issue%3F%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-841241%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-841241%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F404735%22%20target%3D%22_blank%22%3E%40JBoehlke%3C%2FA%3E%26nbsp%3BHi.%20There's%20nothing%20for%20us%20to%20do%20here%20at%20MS%2C%20Dell%20was%20not%20following%20the%20SMB2%20Negotiate%20specification.%20They%20need%20to%20change%20their%20behavior%20here%20like%20they%20did%20in%20other%20products%20mentioned%20in%20the%20thread.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-841254%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-841254%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F52778%22%20target%3D%22_blank%22%3E%40Ned%20Pyle%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYep%2C%20understood.%20thx%20for%20the%20reply%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-841271%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-841271%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F404735%22%20target%3D%22_blank%22%3E%40JBoehlke%3C%2FA%3EWe%20are%20currently%20in%20the%20process%20of%20migrating%20150%20TB%20of%20data%20from%20our%20FluidFS%20to%20a%20newly%20built%20Server%202019%20VM%20because%20of%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-844076%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-844076%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F327427%22%20target%3D%22_blank%22%3E%40itkpli%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20sure%20why%20most%20people%20are%20trying%20to%20blame%20EMC%20%2F%26nbsp%3B%3CSPAN%3EFluidFS%26nbsp%3Bfor%20the%20SMB%20implementation.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20think%20Microsoft%20should%20be%20the%20one%20to%20fix%20the%20issue.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESMB%203.1.1%20is%20not%20new%2C%20our%20EMC%20NAS%20has%20been%20on%20SMB%203.1.1%20for%20years%2C%20and%20on%20previous%20Windows%2010%20releases%20(1703%2C%201709%2C%201803%2C%201809)%2C%20it%20is%20able%20using%20SMB%203.1.1%20to%20connect%20to%20our%20EMC%20NAS%20servers.%20Why%20the%20same%20SMB%203.1.1%20stopped%20working%20in%201903%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ETry%20to%20have%20a%20%3C%2FSPAN%3EWindows%2010%20PC%20with%20build%20of%26nbsp%3B%3CSPAN%3E(1703%2C%201709%2C%201803%2C%201809)%20connected%20with%20your%20EMC%20NAS.%20and%20run%20Get-SMBConnection%2C%20it%20should%20prove%20that%20the%20connection%20is%20utilizing%20SMB%203.1.1.%20There%20is%20no%20issue%20on%20EMC's%20SMB%20implementation.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-844840%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-844840%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F405923%22%20target%3D%22_blank%22%3E%40IronRolia%3C%2FA%3E%26nbsp%3BBecause%20Dell%20was%20not%20following%20the%20SMB%20specification.%20An%20SMB%20server%20is%20not%20supposed%20to%20fail%20when%20sent%20unsupported%20capabilities%20during%20NEGOTIATE%20phase%2C%20regardless%20of%20the%20maximum%20dialect%20support.%201903%20added%20a%20Compression%20flag%20to%20SMB%20capabilities%20(which%20was%20also%20publicly%20documented%20so%20that%20vendors%20could%20support%20it%20if%20they%20wished)%20and%20if%20not%20supporting%20compression%2C%20the%20Dell%20device%20is%20supposed%20to%20respond%20that%20it%20doesn't%20support%20that%20flag%2C%20not%20error%20and%20tear%20down%20session.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20why%20Dell%20already%20fixed%20their%20other%20product%20with%20this%20symptom.%20Other%20manufacturers%20were%20unaffected%20by%20the%20addition%20of%20SMB%20Compression%20support%20in%201903%20because%20they%20followed%20the%20spec.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENote%3A%20I%20own%20SMB%20and%20its%20specification.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-846607%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-846607%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F52778%22%20target%3D%22_blank%22%3E%40Ned%20Pyle%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20reply.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%20is%20if%20DELL%20did%20not%20follow%20the%20SMB%20specification%2C%20how%20would%20the%20SMB%203.1.1%20dialect%20%2F%20protocol%20worked%20on%20previous%20Windows%2010%20releases%20with%20EMC%20NAS%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20run%20GET-SMBConnection%20when%20connected%20to%20our%20EMC%20NAS%2C%20on%20previous%20Windows%2010%20releases%2C%20it%20clearly%20shows%20the%20connection%20are%20utilization%20SMB%203.1.1%20protocol.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20prove%20of%20any%20other%20vendors%20that%20actually%20use%20SMB%203.1.1%20on%20their%20NAS%20storage%20that%20work%20with%20Windows%2010%201903%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20you%20suggesting%20that%20Microsoft%20also%20did%20not%20follow%20the%20SMB%20specs%20on%20their%20previous%20Win%2010%20releases%2C%20and%20now%20they%20decided%20to%20%22fix%22%20it%20in%20release%201903%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20481px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F130945i5C321D7F37711BE6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22WIndows-SMB-EMC-NAS.PNG%22%20title%3D%22WIndows-SMB-EMC-NAS.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI%20really%20hope%20Microsoft%20and%20DELL%20can%20work%20together%20to%20investigate%20the%20issue%20collaboratively%20and%20have%20this%20issue%20fixed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-846898%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-846898%22%20slang%3D%22en-US%22%3E%3CP%3EFWIW%20the%20latest%20from%20Dell.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E9%2F9%2F2019%3C%2FP%3E%3CP%3ENo%20official%20ETA%20yet%20for%20MR640%20but%20I%20think%20that%20a%20release%20sometime%20this%20month%20is%20a%20strong%20possibility.%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EChad%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F405923%22%20target%3D%22_blank%22%3E%40IronRolia%3C%2FA%3E%26nbsp%3BNeds'%20explanation%20says%20that%20the%203.1.1%20spec%20if%20properly%20supported%20can%20have%20features%20that%20a%20vendor%20may%20not%20support%2C%20but%20that%20vendor%20device%20is%20still%20supposed%20to%20work.%26nbsp%3B%20MS%20added%20the%20compression%20piece%20in%201903%20and%20if%20the%20vendor%20was%20using%20the%20spec%20properly%20they%20would%20still%20work%2C%20and%20just%20not%20actually%20have%20the%20compression%20part.%26nbsp%3B%20The%20Dell%20system%20is%20failing%20because%20it%20does%20not%20properly%20handle%20the%20added%20features%20as%20the%203.1.1%20spec%20says%20it%20should.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENetapp%20does%20not%20have%20this%20issue%2C%20nor%20does%20a%20small%20Qnap%20device%20I%20run.%26nbsp%3B%20I%20think%20Dell%20has%20already%20fixed%20this%20on%20their%20Unity%20line%20(perhaps%20not%20from%20reading%20above%2C%20I%20don't%20have%20one%20of%20those%20systems)%2C%20but%20those%20of%20us%20stuck%20using%20the%20FluidFS%20system%20which%20they%20have%20already%20stopped%20selling%20don't%20yet%20have%20a%20fix.%26nbsp%3B%20Our%20system%20is%20covered%20under%20warranty%20until%20March%202022%20so%20i'm%20certainly%20expecting%20a%20fix.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-847261%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-847261%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20clarification%2C%20I%20didn't%20catch%20the%20fine%20print%20of%20compression%20feature%20in%201903's%20SMB%203.1.1.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20really%20hope%20Microsoft%20and%20DELL%20can%20jointly%20work%20on%20this%20and%20come%20up%20with%20a%20fix%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBefore%20a%20fix%20become%20available%2C%20I%20hope%20Microsoft%20can%20also%20provide%20some%20workaround%20solution%20like%20replacing%20the%20SMB%20dlls%20or%20some%20registry%20changes%20etc.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20personally%20have%20tried%20to%20replacing%20below%20DLLs%20from%20previous%20version%20of%20Windows%2010%20releases%2C%20but%20didn't%20work.%20Hope%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F52778%22%20target%3D%22_blank%22%3E%40Ned%20Pyle%3C%2FA%3E%26nbsp%3B%20can%20point%20out%20a%20better%20workaround%20solutions%20before%20we%20can%20get%20a%20permanent%20fix%20from%20DELL.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESystem32%5Cntshrui.dll%3C%2FP%3E%3CP%3ESystem32%5Csmbwmiv2.dll%3C%2FP%3E%3CP%3ESystem32%5CSMBHelperClass.dll%3C%2FP%3E%3CP%3ESysWow64%5CSMBHelperClass.dll%3C%2FP%3E%3CP%3ESystem32%5Cdrivers%5Csmbdirect.sys%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-847263%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-847263%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F405923%22%20target%3D%22_blank%22%3E%40IronRolia%3C%2FA%3E%26nbsp%3BI've%20been%20telling%20users%20to%20rollback%20versions%20for%20now%2C%20as%20the%20Dell%20fix%20is%20to%20completely%20disable%20smb%203%20on%20the%20NAS%20end.%26nbsp%3B%20Not%20sure%20on%20what%20level%20you%20are%20dealing%20with%20the%20problem%2C%20but%20we've%20also%20blocked%20the%201903%20rollout%20for%20now.%26nbsp%3B%20I%20don't%20love%20the%20solution%20by%20any%20means%2C%20but%20just%20dealing%20with%20what%20we've%20got%20to%20work%20with.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-847265%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-847265%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F405923%22%20target%3D%22_blank%22%3E%40IronRolia%3C%2FA%3E%26nbsp%3BYep%2C%20we%20rang%20them%20up%20right%20away%20%3A).%20They%20already%20fixed%20another%20line%20of%20products%2C%20I'm%20sure%20they%20are%20diligently%20working%20on%20this.%20The%20only%20workarounds%20right%20now%20are%20to%20disable%20SMB%203.1.1%20within%20the%20NAS%26nbsp%3B%20so%20that%20the%20client%20doesn't%20try%20to%20negotiate%20compression%20capabilities%20-%20this%20sacrifices%20a%20lot%20of%20other%20things%2C%20obviously.%20I%20think%20some%20other%20folks%20in%20this%20thread%20have%20talked%20about%20how%20to%20do%20this%2C%20I%20have%20no%20idea%20%3A%5C%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-847279%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-847279%22%20slang%3D%22en-US%22%3EIt%20isn't%20disruptive.%20It%20only%20effects%20new%20connections%2C%20existing%20connections%20stay%20on%20SMB3%20until%20they%20close.%3CBR%20%2F%3EWe%20have%20done%20it%20on%20our%20FluidFS%20servers%20and%20they%20now%20work%20with%201903.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-847276%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-847276%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F52778%22%20target%3D%22_blank%22%3E%40Ned%20Pyle%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F405923%22%20target%3D%22_blank%22%3E%40IronRolia%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVia%20the%20NAS%20GUI%3A%3C%2FP%3E%3CP%3EFile%20System%20-%20%26gt%3B%20Client%20Accessibility%20-%20%26gt%3B%20Protocols%20-%20%26gt%3B%20Edit%20Settings%20on%20the%20SMB%20Protocol%3C%2FP%3E%3CP%3EUncheck%20SMBv3%3C%2FP%3E%3CP%3Eper%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F341189%22%20target%3D%22_blank%22%3E%40DarrenMiller%3C%2FA%3E%26nbsp%3Bbelow%20this%20is%20not%20a%20disruptive%20change%2C%20and%20only%20impacts%20new%20connections.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F130992i607389E02363B221%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-847607%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-847607%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20instruction.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20over%20thousand%20users%20sharing%20the%20the%20NAS%2C%20only%20few%20PCs%20upgraded%20to%201903%2C%20will%20revert%20back%20to%201809.%20Besides%20on%201809%2C%20we%20are%20able%20to%20take%20advantage%20of%20SMB%203.1.1%2C%20disabling%20SMB%20v3%20is%20not%20going%20to%20work%20for%20us.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-869848%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-869848%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F405923%22%20target%3D%22_blank%22%3E%40IronRolia%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGOOD%20NEWS...%20I'm%20just%20on%20phone%20with%20my%20local%20Dell%20Engineer%2C%20the%20RM640%20Patch%20is%20out%20since%20friday%2019.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDon't%20hesitate%20to%20ask%20them%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20fun%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870101%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870101%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F328156%22%20target%3D%22_blank%22%3E%40Sybux%3C%2FA%3Ebeat%20me%20to%20it%2C%20hope%20to%20get%20this%20installed%20this%20week.%26nbsp%3B%20If%20anyone%20has%20has%20loaded%20it%20already%20and%20had%20any%20comments%20it%20would%20be%20appreciated.%26nbsp%3B%20Presumably%20it%20fixes%20the%201903%20issue%2C%20but%20I%20haven't%20been%20able%20to%20get%20a%20copy%20of%20the%20release%20notes%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870167%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870167%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3Bdo%20you%20have%20a%20link%20to%20the%20release%20notes%20for%20the%20patch%3F%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870226%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870226%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F406665%22%20target%3D%22_blank%22%3E%40deetee%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22ftp%3A%2F%2Fcustomer%3AY3V2s-uH%40ftp.compellent.com%2FSOFTWARE%2FFluidFS%2F680-115-002_FluidFS_v6_Release_Notes.pdf%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eftp%3A%2F%2Fcustomer%3AY3V2s-uH%40ftp.compellent.com%2FSOFTWARE%2FFluidFS%2F680-115-002_FluidFS_v6_Release_Notes.pdf%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPretty%20minimal%20changes%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFixed%20Issues%20in%20FluidFS%20Version%206.0.400016%3CBR%20%2F%3EThe%20following%20issues%20were%20fixed%20in%20FluidFS%206.0.400016%3A%3CBR%20%2F%3EArea%20Description%3CBR%20%2F%3ENAS%20Volumes%2C%20Shares%2C%3CBR%20%2F%3Eand%20Exports%3CBR%20%2F%3EAfter%20installing%20Windows%2010%20update%201903%2C%20SMB%20shares%20are%20not%20accessible%20using%20the%20UNC%20path.%3CBR%20%2F%3ESystem%20Functionality%20The%20system%20incorrectly%20reports%20that%20duplicate%20IP%20addresses%20are%20in%20use%20for%20nodes%20on%20the%20cluster.%3CBR%20%2F%3EThe%20system%20incorrectly%20reports%20battery%20failures%20during%20the%20battery%20calibration%20process%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-871581%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-871581%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3B%20I%20installed%20the%20new%20version%20on%20our%20DR%20FluidFS%20this%20morning.%26nbsp%3B%20It%20all%20went%20smoothly%20and%20it%20now%20works%20with%20SMB3%20and%20Windows%2010%201903!%3C%2FP%3E%3CP%3EI'm%20going%20to%20give%20it%20a%20few%20more%20days%20testing%20before%20installing%20it%20on%20the%20production%20servers%20but%20it%20looks%20ok%20so%20far.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-874293%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-874293%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F341189%22%20target%3D%22_blank%22%3E%40DarrenMiller%3C%2FA%3E%26nbsp%3BStill%20trying%20to%20get%20Dell%20to%20review%20the%20diags%20I%20sent%20them%20and%20get%20me%20the%20actual%20firmware.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFWIW%20a%20friend%20of%20mine%20who%20also%20runs%20this%20system%20sent%20me%20the%20info%20below.%26nbsp%3B%20Hopefully%20unlikely%20anyone%20else%20will%20run%20into%20this%2C%20but%20sounds%20like%20a%20bad%20situation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3C%2FP%3E%3CP%3EThe%20problem%20that%20occurred%20on%20our%20end%20occurred%20during%20the%20initial%20diagnostics%20process.%26nbsp%3B%20We%20were%20working%20with%20the%20individual%20assigned%20to%20help%20get%20us%20prepped%20for%20the%20update%2C%20and%20so%20we%20pulled%20the%20ISO%2C%20and%20were%20running%20the%20initial%20tests.%26nbsp%3B%20Part%20of%20that%20process%20%E2%80%93%20they%20had%20asked%20us%20to%20update%20the%20support%20password.%26nbsp%3B%20When%20we%20did%2C%20the%20process%20tossed%20an%20error.%26nbsp%3B%20They%20didn%E2%80%99t%20think%20anything%20about%20it.%26nbsp%3B%20However%2C%20that%20process%20created%20a%20seed%20that%20didn%E2%80%99t%20exist%2C%20and%20the%20system%20literally%20hung%20during%20the%20diagnostic%20process%20trying%20to%20sync%20that%20file%20between%20the%20two%20nodes.%26nbsp%3B%20It%20was%20difficult%20to%20diagnosis%20and%20we%20had%20to%20have%20someone%20from%20the%20team%20that%20actually%20wrote%20the%20queuing%20system%20for%20the%20product%20determine%20the%20problem%20and%20write%20a%20small%20utility%20to%20stop%20the%20cascade%20of%20badness.%26nbsp%3B%20We%20were%20actually%20at%20a%20point%20of%20essentially%20re-imaging%20both%20nodes%20because%20no%20one%20could%20figure%20out%20all%20Thursday%20and%20Friday%20what%20the%20hell%20was%20going%20on.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnce%20that%20was%20fixed%2C%20the%20firmware%20update%20took%2025-30%20minutes%20%E2%80%93%20tops.%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-877147%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-877147%22%20slang%3D%22en-US%22%3E%3CP%3EHaving%20the%20same%20issue%20with%20Unity%20300.%3C%2FP%3E%3CP%3EThis%20Dell%20EMC%20Article%20worked%20for%20me.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Femcservice.force.com%2FCustomersPartners%2FkA43a00000003w4CAA%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Femcservice.force.com%2FCustomersPartners%2FkA43a00000003w4CAA%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-877210%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-877210%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F341189%22%20target%3D%22_blank%22%3E%40DarrenMiller%3C%2FA%3E%26nbsp%3Bfinally%20got%20this%20installed%20our%20on%20DR%20side%20yesterday.%26nbsp%3B%20Did%20Dell%20request%20you%20rolling%20restart%20both%20controllers%20on%20the%20FS%20prior%20to%20updating%2C%20and%20then%20again%20request%20you%20restart%20both%20controllers%20after%20updating%20firmware%3F%26nbsp%3B%20They%20asked%20that%20I%20do%20that%2C%20then%20send%20them%20the%20gen%20diags%20after%20doing%20all%20of%20that.%26nbsp%3B%20The%202nd%20set%20of%20rolling%20restarts%20did%20create%20some%20problems.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20are%20also%20asking%20for%20access%20to%20the%20storage%20arrays%2C%20which%20makes%20me%20a%20bit%20hesitant%20to%20think%20this%20firmware%20is%20production%20ready.%26nbsp%3B%20That%20being%20said%20I%20haven't%20seen%20any%20issues%20with%20it%20so%20far%2C%20and%201903%20does%20work%20properly.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-877565%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-877565%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3BThey%20requested%20rolling%20reboots%20before%20the%20upgrade%20and%20logs%2C%20but%20not%20rolling%20reboots%20after.%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20will%20try%20rolling%20reboots%20now%20the%20upgrade%20is%20done%20to%20check%20it%20doesn't%20cause%20us%20any%20issues.%26nbsp%3B%20We%20normally%20have%20to%20do%20rolling%20reboots%20once%20a%20month%20anyway%20as%20the%20controllers%20regularly%20run%20out%20of%20cache%20(long%20standing%20issue%2C%20not%20related%20to%20this).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20a%20bit%20surprised%20by%20the%20extra%20steps%20-%20I've%20never%20had%20to%20do%20that%20before%20so%20it%20does%20seem%20they%20are%20being%20extra%20cautious%20with%20this%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-905148%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-905148%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F341189%22%20target%3D%22_blank%22%3E%40DarrenMiller%3C%2FA%3E%26nbsp%3B%20They%20eventually%20said%20the%20luns%20were%20dropped%20during%20the%20restarts%20because%20there%20was%20a%20raid%20rebalance%20going%20at%20that%20time.%26nbsp%3B%20I'm%20not%20sure%20why%20that%20would%20cause%20it%20to%20drop%20connections%2C%20but%20that's%20what%20I%20was%20told.%26nbsp%3B%20I%20had%20replaced%20a%20drive%20in%20one%20of%20the%20sc2080's%20under%20the%20NAS%20head%20a%20few%20days%20before%20doing%20the%20restarts.%26nbsp%3B%20From%20the%20end%20user%20side%20I%20don't%20believe%20there%20is%20any%20way%20to%20actually%20see%20that%20the%20system%20is%20still%20balancing%20data%20after%20replacing%20a%20disk.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20amount%20of%20disk%20these%20arrays%20have%20dropped%20is%20at%20about%2015%25%20in%202.5%20years%20of%20use%20which%20is%20about%2010%25%20worse%20then%20any%20other%20array%20I%20run%20fwiw.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1046189%22%20slang%3D%22en-US%22%3ERe%3A%20W10-1903%20UNC%20path%20failing%200x80070043%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1046189%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350077%22%20target%3D%22_blank%22%3E%40tomatthe%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20wanted%20to%20add%20that%20this%20issue%20is%20now%20%3CFONT%3Eaddressed%20in%20Unity%20Operating%20Environment%205.0.1.0.5.011%20and%20greater.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EWe%20upgraded%20our%20Unity's%20a%20few%20weeks%20ago%20and%20everything%20works%20in%20regards%20to%20Windows%2010%201903%20(and%201909)%20with%20SMB%203.1.1%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
kurgan
Occasional Contributor

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?

81 Replies

update,:

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

Highlighted

@kurgan Any luck figuring this out? Having the same problem over here with our Dell EMC UNITY SAN and it's killing me. 

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.

@Rohit_Sakhrani 

 

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.

@k_perri 

Just wanted to add that we also have problems using SMB with 1903 and our 2 Unity 400 (latest code).

 

This is a big issue for us but I find it strange that I haven't found anything on the Internet about this except here.

@itkpli Same problem also here with Build 19h1 and Dell compellent FluidFS. no poblem with windows servers. does anyone else can test on a linux machine with standard samba ? 

@SybuxWe've now filed a support case with Dell/EMC about this.

We'll see what they say about it.

 

@itkpliI just subscribed to this post. I just wiped and reloaded my 1903 machine thinking I had screwed it up. Good to know I'm not alone. I also cannot access EMC Unity shares.

 

I've created this problem report in the feedback hub if you wish to upvote it:  https://aka.ms/AA4y2ra

 

Thanks,

Dan

@itkpliwhat did Dell say?

 

Did anyone fix this issue yet? we are on the same boat with Dell Unity, we will also open a case with Dell. Just want to know if anyone has any insights. 

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

If you'll shoot me the case number, I'll include it in a ticket that I create with them.

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. 

@mrjonboy 

 

Wow. Nice of Dell to explain the program to us!  Lucky for me, I have a WebEx this morning with one of their Engineers that seems to have an idea to at least try.  Fingers crossed; I'll report back.

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!

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

More info: What’s new in SMB 3.1.1 in the Windows Server 2016 Technical Preview 2

@itkpli 

 

Agreed on all counts. At least we're not dead in the water, though, while we wait for a fix.

@dwatson Presumably this fix is for Unity?

We still have the same problem with FluidFS and Dell have told us it is Microsoft's problem.

Has anybody found a fix for FluidFS?

@dwatsonMany thanks for this. This has fixed my issue for now.

Just answering my own question - it looks like completely disabling SMBv3 on FluidFS is a workaround.  Not great, but at least it gets things working again.

Any updates on this? Thanks

@Dmorton 

Dell EMC just released an official KB about this:

 

DTA 534173: Dell EMC Unity: Windows users may be unable to access Common Internet File System (CIFS)...

 

They still recommend to downgrade to 3.0.2 or to go back to 1809 on the clients but it says that they are investigating an enchancement to adress this issue.

 

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

@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.
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?

@tomatthe 

 

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

@itkpli 

 

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.

 

If anyone wanted the case toe reference,

SR 991311217

The engineering team at EMC are working on providing a resolution or hotfix in the next patch.

I've also got permission from EMC to post their official document about Unity and Windows 1903 here.

The .pdf includes instructions for the workaround to downgrade to 3.0.2

 

Please see the attached document.

From Dell on the Compellent end of things as of 6/2/2019

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

better get used to typing //192.168.0.xx on new shortcut

 

@kurgan 

It works for me now, not sure if it is a windows update or update on fluidity that has fixed it.

@kurgan  Which version of Windows are you on now?  Start -> Run - > Winver

 

Dell has not released updated firmware for the Fluid FS as of 6/10/2019 that I'm aware of from my current open ticket.

 

"I don’t have any additional information to share regarding the SMBv3 and Windows 10 update 1903 issue. I’ll continue to monitor this and keep you informed."

1903 -18362.30
actually just updated to 18362.175 a minute ago, still works fine

I've just tried the latest update (18362.175) and it still does not work with FluidFS for me with SMBv3 turned on.

The message I got from my case with Dell was they weren't planning on making any changes to FluidFS and were leaving Microsoft to fix it.

Okay followed up on it, our IT department has disabled smb3 for now to fix it.

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

 

Ned Pyle | Principal Program Manager, MS | @nerdpyle on twitter

Solution

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

@Ned Pyle Hi Ned,

 

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.

Thanks again.

Just a quick update on this - I have had confirmation from Dell that they are working on a fix for FluidFS.

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

@tomatthe  if Dell pushes back please feel free to drop my name, I'll be happy to chat with them

Hi everyone,

do you have any update ?

Hi

 

on my side we have a UnityVSA and they confirm its fixed on the latest release (not public) 

4.5.1.0.6.136

 

so now it maybe available for other Filer

 

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

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

@tomatthe 

 

Thanks for the follow up!

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies