[SOLVED] New computers drop NAS drive connection after reboot

[DonS]

Hey all!

Bit of an annoying issue today that has me stumped. I was replacing two work stations (old, upgraded Win10 workstations with brand new ones). I have a shared / mapped drive from another computer that is sharing quickbooks just fine. But they also have this ancient Lenovo PX2-300D NAS that worked fine on the previous computers but is having issues on the new computers.

Behavior is the same on both PCs. I can initially see it on the network, map it (it does not have any credentials to log in), and can access files fine.. until the computer reboots. Then, it shows the mapped drive, but not connected (no Red X) just.. unable to connect. When you attempt to connect to it, the annoying error of "0x80070035 The network path was not found" shows up.

If I disconnect the drive, reboot, I can then remap the drive again.. but it only stays until the next reboot. I made sure the SMB 1.0 file sharing support options were added (since this thing is ancient). But beyond that, not sure why it keeps puking out after every reboot.

Any suggestions would be welcome!

 

[Stever]

I have had simular issuse with machines changing IP addsess, the PFY had set them to "automatic ", IP adresses need to be static for stability

 

[Markverhyden]

How are the shares mapped? Using ip addresses is far more reliable than using network names in a non-domain environment.

 

[Stever]

How are the shares mapped? Using ip addresses is far more reliable than using network names in a non-domain environment.

Don't get me started on the issue of adding something dynamic to the Sendto folder that I have had with the PFY

 

[DonS]

I'm just grabbing it on the network by its name, then mapping the drive. Same way it was apparently done on the previous computers. I can certainly try mapping it by IP address... but something tells me that may not be a resolution i this case.

 

[Metanis]

Here's a handy little troubleshooting checklist...

Topic: What am i doing wrong? (Networking problems) @ AskWoody

I eventually created a batch file to try and solve Windows 10 network connection difficulties...

@echo off
echo This batch file enables smb 1.0, 2.0, and 3.0
echo and then deletes all possible saved or cached group policies!
echo Metanis 1/25/2016
@echo on
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
pause
sc.exe config mrxsmb10 start= auto
pause
sc.exe config mrxsmb20 start= auto
pause
reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters /v SMB1 /t REG_DWORD /d 1 /f
pause
reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters /v SMB2 /t REG_DWORD /d 1 /f
pause
powershell set-smbserverconfiguration -enablesmb1protocol $true
pause
powershell set-smbserverconfiguration -enablesmb2protocol $true
pause
reg query HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters /v SMB1
pause
reg query HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters /v SMB2
pause
del /S /F /Q "%ALLUSERSPROFILE%\Application Data\Microsoft\Group Policy\History\*.*"
pause
del /S /F /Q c:\windows\system32\grouppolicy\*.*
pause
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Group Policy" /f
pause
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy" /f
pause
reg delete "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Group Policy" /f
pause
reg delete "HKCU\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Group Policy\DataStore" /f
pause
reg delete "HKLM\Software\Policies\Microsoft" /f
pause
reg delete "HKCU\Software\Policies\Microsoft" /f
pause
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies" /f
pause
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths /v "\\*\SYSVOL" /d "RequireMutualAuthentication=0" /t REG_SZ /f
pause
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths /v "\\*\NETLOGON" /d "RequireMutualAuthentication=0" /t REG_SZ /f

 

[Markverhyden]

Here's a handy little troubleshooting checklist...

Topic: What am i doing wrong? (Networking problems) @ AskWoody

I eventually created a batch file to try and solve Windows 10 network connection difficulties...

@echo off
echo This batch file enables smb 1.0, 2.0, and 3.0
echo and then deletes all possible saved or cached group policies!
echo Metanis 1/25/2016
@echo on
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
pause
sc.exe config mrxsmb10 start= auto
pause
sc.exe config mrxsmb20 start= auto
pause
reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters /v SMB1 /t REG_DWORD /d 1 /f
pause
reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters /v SMB2 /t REG_DWORD /d 1 /f
pause
powershell set-smbserverconfiguration -enablesmb1protocol $true
pause
powershell set-smbserverconfiguration -enablesmb2protocol $true
pause
reg query HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters /v SMB1
pause
reg query HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters /v SMB2
pause
del /S /F /Q "%ALLUSERSPROFILE%\Application Data\Microsoft\Group Policy\History\*.*"
pause
del /S /F /Q c:\windows\system32\grouppolicy\*.*
pause
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Group Policy" /f
pause
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy" /f
pause
reg delete "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Group Policy" /f
pause
reg delete "HKCU\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Group Policy\DataStore" /f
pause
reg delete "HKLM\Software\Policies\Microsoft" /f
pause
reg delete "HKCU\Software\Policies\Microsoft" /f
pause
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies" /f
pause
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths /v "\\*\SYSVOL" /d "RequireMutualAuthentication=0" /t REG_SZ /f
pause
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths /v "\\*\NETLOGON" /d "RequireMutualAuthentication=0" /t REG_SZ /f

Thanks. Great share.

 

[Sky-Knight]

SMBv1 is bad, always bad, never will be good.

XP died a LONG time ago. Upgrade the device if it's so limited. The new machines are enforcing sanity, LET THEM!

 

[DonS]

Yes, the machines are enforcing sanity, alas, not on the client however.

 

[DonS]

Here was my resolution for this issue. The NAS share now retains after reboot

Added the following to Windows Registry under Registry subkey
HKEY_CURRENT_USER\Network\[drive letter]

Created a new DWORD (32-bit) value named ProviderFlags. ProviderFlags value set to 1