User Profile
IronRolia
Copper Contributor
Joined Sep 09, 2019
User Widgets
Recent Discussions
Re: W10-1903 UNC path failing 0x80070043
tomatthe Thanks for the instruction. We have over thousand users sharing the the NAS, only few PCs upgraded to 1903, will revert back to 1809. Besides on 1809, we are able to take advantage of SMB 3.1.1, disabling SMB v3 is not going to work for us.9KViews0likes11CommentsRe: W10-1903 UNC path failing 0x80070043
tomatthe Thanks for the clarification, I didn't catch the fine print of compression feature in 1903's SMB 3.1.1. I really hope Microsoft and DELL can jointly work on this and come up with a fix soon. Before a fix become available, I hope Microsoft can also provide some workaround solution like replacing the SMB dlls or some registry changes etc. I personally have tried to replacing below DLLs from previous version of Windows 10 releases, but didn't work. Hope NedPyle can point out a better workaround solutions before we can get a permanent fix from DELL. System32\ntshrui.dll System32\smbwmiv2.dll System32\SMBHelperClass.dll SysWow64\SMBHelperClass.dll System32\drivers\smbdirect.sys9.1KViews0likes32CommentsRe: W10-1903 UNC path failing 0x80070043
NedPyle Thanks for the reply. My question is if DELL did not follow the SMB specification, how would the SMB 3.1.1 dialect / protocol worked on previous Windows 10 releases with EMC NAS? If I run GET-SMBConnection when connected to our EMC NAS, on previous Windows 10 releases, it clearly shows the connection are utilization SMB 3.1.1 protocol. Do you have prove of any other vendors that actually use SMB 3.1.1 on their NAS storage that work with Windows 10 1903? Are you suggesting that Microsoft also did not follow the SMB specs on their previous Win 10 releases, and now they decided to "fix" it in release 1903? I really hope Microsoft and DELL can work together to investigate the issue collaboratively and have this issue fixed.9.2KViews0likes34CommentsRe: W10-1903 UNC path failing 0x80070043
itkpli Not sure why most people are trying to blame EMC / FluidFS for the SMB implementation. I think Microsoft should be the one to fix the issue. SMB 3.1.1 is not new, our EMC NAS has been on SMB 3.1.1 for years, and on previous Windows 10 releases (1703, 1709, 1803, 1809), it is able using SMB 3.1.1 to connect to our EMC NAS servers. Why the same SMB 3.1.1 stopped working in 1903? Try to have a Windows 10 PC with build of (1703, 1709, 1803, 1809) connected with your EMC NAS. and run Get-SMBConnection, it should prove that the connection is utilizing SMB 3.1.1. There is no issue on EMC's SMB implementation.9.3KViews0likes36Comments
Recent Blog Articles
No content to show