S
ShaunIOW
This is a strange fault as it happened all of a sudden, I shut down the PC one night when everything was fine, then the following day after bootup I couldn't access the NAS drives although they do show in Windows File Explorer, I just get the error 0x80070035 The network path was not found.
I can access the Buffalo Linkstation NAS though the navigator desktop app PC, and can log onto the dashboard for the FreeNAS (running on a HP Proliant Microserver 1610T Gen8), Plex which is installed on the FreeNAS also works fine, I just cannot access them in Windows File Explorer. Everything is wired with Cat5e cable (and unmanaged gigabit switches) and have static IP's. The PC and NAS drives are also all in the same Workgroup.
The Windows 10 Pro version on the desktop PC is 1903 OS build 18362.239. I've also run Windows update today till it found no more.
I've tried all the following things so far:
Enabled SMB 1.0/CIFS File Sharing Support
Made sure Network discovery and sharing is turned on
Disabled AntiVirus and Firewall
Uninstalled AntiVirus and Firewall
Enabled NetBIOS over TCP/IP
Windows Credentials is empty
Made sure Send LM & NTLM-use NTLMv2 session security if negotiated.is enabled
Using the Windows Powershell (admin) prompt I entered:
ipconfig /release
ipconfig /flushdns
ipconfig /renew
Then tried:
ipconfig /flushdns
nbtstat –r
netsh int ip resetnetsh winsock reset
But after using netsh int ip reset I got the following:
PS C:\> netsh int ip reset
Resetting Compartment Forwarding, OK!
Resetting Compartment, OK!
Resetting Control Protocol, OK!
Resetting Echo Sequence Request, OK!
Resetting Global, OK!
Resetting Interface, OK!
Resetting Anycast Address, OK!
Resetting Multicast Address, OK!
Resetting Unicast Address, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting Potential, OK!
Resetting Prefix Policy, OK!
Resetting Proxy Neighbor, OK!
Resetting Route, OK!
Resetting Site Prefix, OK!
Resetting Subinterface, OK!
Resetting Wakeup Pattern, OK!
Resetting Resolve Neighbor, OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , failed.
Access is denied.
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Restart the computer to complete this action.
So after an Internet search I tried using Regedit to change:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Nsi/{eb004a00-9b1a-11d4-9123-0050047759bc}/26
To give everyone permission, then re-ran netsh int ip reset and had no errors, so re-ran netsh winsock reset
I've also tried uninstalliing and reinstalling the network adaptor, and uninstaling/reinstalling all the network adaptors including hidden ones.
None of this worked, so I tried refreshing the PC using the remove everything option (all my files are on a different drive anyway, Drive C: is just Windows and programs), still no joy, so tried everything above again, after that failed to work I tried with a fresh install of Windows, and tried everything above yet again, still no joy and I'm at a loss what to try next.
Strangely on my laptop running Windows 10 (also version 1903 and updated today) I can see and access all the NAS drives no problem over both wired or wireless.
Any ideas?
Cheers
Continue reading...
I can access the Buffalo Linkstation NAS though the navigator desktop app PC, and can log onto the dashboard for the FreeNAS (running on a HP Proliant Microserver 1610T Gen8), Plex which is installed on the FreeNAS also works fine, I just cannot access them in Windows File Explorer. Everything is wired with Cat5e cable (and unmanaged gigabit switches) and have static IP's. The PC and NAS drives are also all in the same Workgroup.
The Windows 10 Pro version on the desktop PC is 1903 OS build 18362.239. I've also run Windows update today till it found no more.
I've tried all the following things so far:
Enabled SMB 1.0/CIFS File Sharing Support
Made sure Network discovery and sharing is turned on
Disabled AntiVirus and Firewall
Uninstalled AntiVirus and Firewall
Enabled NetBIOS over TCP/IP
Windows Credentials is empty
Made sure Send LM & NTLM-use NTLMv2 session security if negotiated.is enabled
Using the Windows Powershell (admin) prompt I entered:
ipconfig /release
ipconfig /flushdns
ipconfig /renew
Then tried:
ipconfig /flushdns
nbtstat –r
netsh int ip resetnetsh winsock reset
But after using netsh int ip reset I got the following:
PS C:\> netsh int ip reset
Resetting Compartment Forwarding, OK!
Resetting Compartment, OK!
Resetting Control Protocol, OK!
Resetting Echo Sequence Request, OK!
Resetting Global, OK!
Resetting Interface, OK!
Resetting Anycast Address, OK!
Resetting Multicast Address, OK!
Resetting Unicast Address, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting Potential, OK!
Resetting Prefix Policy, OK!
Resetting Proxy Neighbor, OK!
Resetting Route, OK!
Resetting Site Prefix, OK!
Resetting Subinterface, OK!
Resetting Wakeup Pattern, OK!
Resetting Resolve Neighbor, OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , failed.
Access is denied.
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Restart the computer to complete this action.
So after an Internet search I tried using Regedit to change:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Nsi/{eb004a00-9b1a-11d4-9123-0050047759bc}/26
To give everyone permission, then re-ran netsh int ip reset and had no errors, so re-ran netsh winsock reset
I've also tried uninstalliing and reinstalling the network adaptor, and uninstaling/reinstalling all the network adaptors including hidden ones.
None of this worked, so I tried refreshing the PC using the remove everything option (all my files are on a different drive anyway, Drive C: is just Windows and programs), still no joy, so tried everything above again, after that failed to work I tried with a fresh install of Windows, and tried everything above yet again, still no joy and I'm at a loss what to try next.
Strangely on my laptop running Windows 10 (also version 1903 and updated today) I can see and access all the NAS drives no problem over both wired or wireless.
Any ideas?
Cheers
Continue reading...