Changes between Initial Version and Version 1 of Fix Windows SMB Networking Issues

Timestamp:

11/15/23 09:22:45 (6 months ago)

Author:

Paul Kulda

Comment:

--

Fix Windows SMB Networking Issues

@@ +1 @@
+= Fix Windows SMB Networking Issues =
+
+{{{
+The following or similar registry settings from other threads have not worked:
+
+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider]
+"RestoreConnection"=dword:00000000
+"RestoreTimeout"=dword:00000004
+"DeferConnection"=dword:00000000
+
+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters]
+"SessTimeout"=dword:0000000a
+"ExtendedSessTimeout"=dword:00000000
+"ReconnectTimeout"=dword:00000004
+
+
+
+}}}
+
+{{{
+changed to
+
+LanmanWorkstation,webclient,RDPNPWindows Registry Editor Version 5.00
+
+ [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider]
+ "RestoreConnection"=dword:00000000
+
+ [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder]
+ "ProviderOrder"="RDPNP,LanmanWorkstation,webclient,P9NP"
+
+ [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order]
+ "ProviderOrder"="RDPNP,LanmanWorkstation,webclient,P9NP"
+
+ [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder]
+ "LanmanWorkstation"=dword:000007d0
+ "P9NP"=dword:000001f4
+ "RDPNP"=dword:000003e8
+ "webclient"=dword:00000bb8
+
+}}}
+
+{{{
+Under the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider, 
+
+the RestoreConnection DWORD value 0
+
+
+used to block Explorer from auto-connecting to network shares. 
+
+also
+
+You can create a registry key to disable the automatic reconnection after login. Please take care when editing the registry, as unintended changes may cause system instability.
+
+    As an administrator, hold the Windows Key, while pressing “R” to bring up the Run dialog box.
+    Type “Regedit“, then press “Enter“.
+    The Registry Editor window appears. Navigate to the following location in the Registry.
+        HKEY_LOCAL_MACHINE
+        SYSTEM
+        CurrentControlSet
+        Control
+        NetworkProvider
+    Give “RestoreConnection” one of the values of “0” to disabled the mapped network drive message.
+    If this value doesn’t exist, right-click, then choose “New” > “DWORD Value“ and name it “RestoreConnection”. Make sure you have "0" set as value.
+    Restart your system.
+
+
+}}}
+
+{{{
+SMBv1 Only
+
+I have found another thread with similar issues.   I'm going to give this a go as it looks very promising.
+
+https://community.spiceworks.com/topic/2277832-windows-10-2004-can-t-access-network-shares-and-old-2003-server?page=1
+
+Just in case anyone is still dealing with this there does appear to be a functioning work around.  It'll at least get us by until we can finally and fully deprecate our SMB1 shares.
+
+The trick is to add the registry key "ProviderFlags" as a REG_DWORD with a value of 1 (0x00000001) to HKEY_CURRENT_USER\Network\*SMBv1 Drive Letter*
+
+Then reboot or log on/off.  It fixes the perpetual "reconnecting" status of the SMBv1 drive at logon and everything has been functioning normally and quickly for users we've added that registry key.  Only needs to be added to the drive letters under Network that correspond to SMBv1 shares.
+
+Credit goes to user LeeB1430 in this thread.
+
+EDIT/UPDATE:  This is helping ALOT with my connections.  I initially created one user with the connection and this fix, all OK.  Another user with just the connection and they're virtually unusable.  Quick change to the registry and restart then OK.
+
+}}}
+
+