SMB1 disabled, SMB2 enabled; Can no longer access network shares

Hey All,

After the recent Wanncry attacks I disabled SMB1 protocol as per the cautionary suggestions from Msft et al. Now I can no longer access my network shares via File Explorer. I am still able to access the network device using IP address via browser. However, the unifying and familiar Explorer remains stubbornly broken. When I turn SMB1 back on everything works ok. Any ideas how to fix File Explorer access while remaining somewhat protected. Mucho thanks in advance.

M.B.

If you're system is up to date, there's no need to be concerned about Wannacry - as such there's no problem using SMB1 (despite all the comments about SMB1)

I had the same problem - no shares visible on File Explorer - researched the issues related to disabling SMB1 - and quite frankly, it's only SMB1 on XP machines that will be (would have been before MS released a patch for XP) susceptible to a Wannacry attach. I suggest you reinstate SMB1 and enjoy accessing your network shares as before

R

I've heard the same from several sources and have reverted to smb1. Even so, I wonder why smb2/smb3 isn't enough to provide access to the networked resources. Thanks for the reply.

m.b.

Been through this and enabled SMB1 again.
Why it doesn't work? My findings were in this thread WannaCry - Page 2 - Windows 10 Forums
When you disable SMB1 it uninstalls stuff needed by Workstation service, as said the exploit was patched back in March.