28

Sign in to vote
Subject
Cannot access NAS Drives
Cannot access network attached storage
Error accessing NAS
\\Share\Folder is not accessible
Error code: 0X80070035 The network path was not found
Hi all,
I fixed a stubborn networking issue and hopefully someone else can benefit from all the frustration I
have experienced over the last few days.
Some background. This was a workgroup network not a domain client/server.  Also, Windows
HomeGroup wizards were not used - just accounts and passwords.  I have five NAS boxes for storage
and backup. These NAS boxes use CIFS or SMB file systems. IP address are assigned through DHCP.
It is a very simple yet secure workgroup net. Everything was OK then it hit the fan.
I installed a new router after the old one failed. I powered down the entire network, cabled up and
configured the new router. On my old Vista notebook PC all five NAS devices were OK. In Vista,
Windows Explorer, I could access all the folders and files on all the NAS boxes.
However on all the other systems, Windows 7 or Windows 8, I would get errors. In Windows Explorer
I could see "\\MyNAS\Share\" but cannot navigate to it. 
I would get an error:
"\\MyNAS\Share\ is not accessible. You might not have permission to use this network resource. The
specified network name is no longer available."
Or
"Error code: 0x80070035 The network path was not found"
Another symptom of the error: I could not access the NAS admin pages through Internet Explorer on
the Win 7 or 8 systems.
I spent days trying all the fixes proposed in ALL the online search results, including many and various
registry hacks, security policy changes, Windows Credential Manager changes, anti-virus and firewall
removal, clearing and reregistering DHCP and DNS caches, Router and NAS reconfiguration and
permissions, updating drivers and firmware, various command line tools such as ipconfig, netsh, hosts
file modifications, reinstalling the TCP-IP stack, etc., etc. and ad-nauseam.
The most popular suggestion by far was Network security: LAN Manager authentication level - change
the authentication level to Send LM & NTLM - use NTLMv2 session security if negotiated (or the
corresponding Registry Hack).
None of it worked.  After much trial and error, finally, the only thing that worked for my situation:
1) Network and Sharing Center - Change Advanced Sharing Settings
Turn everything to OFF on all profiles and options - Save changes and close
Then
2) Device Manager - Network Adapters - Uninstall Ethernet and Wireless adapters - Action, Scan for
Hardware Changes to reinstall these devices and close Device Manger.
Then
3) Network and Sharing Center - Change Advanced Sharing Settings - Turn everything to ON for all
profiles and options - Save changes and close.
NAS shares now work properly and I can access the NAS admin configuration pages.
Now you can restrict some access by setting some of the Advanced sharing settings.
So simple and easy after all...
Good Luck!

HAD TO UNINSTALL AND INSTALL CLIENT FOR MICROSOFT NETWORKS AND FILE AND
PRINT SHARING FOR MICROSOFT NETWORKS
 NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK
ADAPTER>CHOOSE PROPERTIES>UNINSTALL CLIENT FOR MICROSOFT NETWORKS
NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK
ADAPTER>CHOOSE PROPERTIES>UNINSTALL FILE AND PRINT SHARING FOR
MICROSOFT NETWORKS
NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK
ADAPTER>CHOOSE PROPERTIES>INTERNET PROTOCOL VERSION
4>INSTALL>CLIENT>INSTALL CLIENT FOR MICROSOFT NETWORKS
NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK
ADAPTER>CHOOSE PROPERTIES>INTERNET PROTOCOL VERSION
4>INSTALL>SERVICE>INSTALL FILE AND PRINT SHARING FOR MICROSOFT NETWORKS


2
Sign in to vote
shutdown all computers
you may have to do this one computer at a time
reset router
HAD TO UNINSTALL AND INSTALL CLIENT FOR MICROSOFT NETWORKS AND FILE AND
PRINT SHARING FOR MICROSOFT NETWORKS
 NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK
ADAPTER>CHOOSE PROPERTIES>UNINSTALL CLIENT FOR MICROSOFT NETWORKS
NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK
ADAPTER>CHOOSE PROPERTIES>UNINSTALL FILE AND PRINT SHARING FOR
MICROSOFT NETWORKS
NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK
ADAPTER>CHOOSE PROPERTIES>INTERNET PROTOCOL VERSION
4>INSTALL>CLIENT>INSTALL CLIENT FOR MICROSOFT NETWORKS
NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK
ADAPTER>CHOOSE PROPERTIES>INTERNET PROTOCOL VERSION
4>INSTALL>SERVICE>INSTALL FILE AND PRINT SHARING FOR MICROSOFT NETWORKS
SHUTDOWN

NET VIEW gives error 1231 !!

Discovered that this new Windows build has magically become CASE SENSITIVE to machine
names!!
IF you have missing shares or completely disappeared machines on your LAN, make sure their
machine names are not mixed-case. If they are mixed case, rename them to ALL CAPS and then
reboot.
Problem SOLVED, they will no longer be invisible on your network.
Just posting this for the benefit of anyone else who may have machines that are ping-able, and have
good  DNS name resolution, but it seems that NETBIOS resolution is 'somehow' broken, even though it
is properly enabled. What I discovered today was that somehow the latest Win10 build has become
slightly CASE-SENSITIVE - and this breaks the old NETBIOS standard going back to antiquity.
So rename your "invisible" shares or machine names to UPPER-CASE, and they will magically appear
on your WORKGROUP again.
http://forum.synology.com/enu/viewtopic.php?f=49&t=106924
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
reboot
------------------------------------------------------------------------------
I finally figured it out. It was in the Administrative tools/Local Security Policy/Security Options.

Changed Network security to Send LM & NTLM responses only

Set the minimum session security for NTLM SSP to disable 128 bit encryption.

Rebooted. Problem solved!

Function Discovery Resource Publication’ service

 Reset the TCP/IP stack
 Release the IP address
 Renew the IP address
 Flush and reset the DNS client resolver cache

 Type netsh winsock reset and press Enter.

 Type netsh int ip reset and press Enter.
 Type ipconfig /release and press Enter.
 Type ipconfig /renew and press Enter.
 Type ipconfig /flushdns and press Enter.
[sharedfolder]
path = /home/USERNAME/sharedfolder
available = yes
valid users = USERNAME
read only = no
browsable = yes
public = yes
writable = yes