NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN314 OS 6.8.1 - Win10 Pro 64-bit Fall Creator 1709 - Can't access Shares
Hi A few days ago I have created a new instance of Win 10, and this has just upgraded to Win10 1709 Fall Creator. Before upgrading to 1709 the instance was connected to the shares, and the shares w...
I (usually) connect the drives as you describe (using different credentials), as I have always had different usernames on the PC and the NAS.
(This was what I meant with this: "Hence when usually establishing connection to the NAS, I am using the NAS-defined username and password, and this has worked fine.")
Can you access it by typing the NAS address or name and share name (//xxx.xxx.xxx.xxx/Share or //NasName/Share) into a Windows Explorer address bar? If not, what is the error message?
No. When I do, I am - as expected - requested to enter credentials.
And when I enter the NAS-stored Username and Password, I receive an error 0x80004005.
The text is probably something like this (translated to english):
Network error
There can't be established access to \\NasName\ShareName.
Control if the name is spelled correct. There can possibly be problems with the network. Click on diagnose to try to identify and solve network problems.
I HAVE run diagnose a few times - and also tried resetting all network settings.
No luck.
Are you possibly already connected to the NAS with different credentials form the same computer (or, at least Windows thinks you are)? Windows does not allow you to connect to the same device using different sets of credentials. You can partly work around that by using the name for one connection and the IP address for a second one, because Windows does not know they are the same device.
Try opening up a command prompt and typing net use /delete, then try again.
BTW, I am very interested in getting to the bottom of this. I have two systems that have asked me to allow them to update to 1709, and I have put it off. But I can't do that forever.
NEW INFORMATION:
I have now tried to also disable IPv6 (as suggested elsewhere).
And I have tried using command line to map the shares as a drive AND THIS WORKS (partly).
net use t: \\NasName\ShareName /user:NasUsername NasPassword /persistent:yes
Doing this, I get the share mapped as t: (in the CMD-environment).
I am able to cd to t:, and use dir to see the files.
and using net use shows the mapped drive.
HOWEVER: It does not have effect on windows explorer (or my other GUI-file managers), where the t: drive is not appearing, and can't be adressed. STRANGE :-(
I have now tried to use Credentials manager, to delete (all) the windows-stored credentials to the NAS.
I have then rebooted.
There are now NO STORED credentials in windows for the NAS.
On the NAS, the SMB Plus app is still set for SMB Version 3.0 (which I assume is right).
This is what I now observe:
When using Windows File Explorer, I click on the NAS-entry in the Network Group (in order to see what it contains (so Windows does still detect the existence of the NAS). I now get the error 0x80070035. The text something like this (translated): The network path was not found.
This is a different error than before. And I am now not requested to enter credentials.
I have now also tried to (again) remove the NAS-app SMB Plus, and let the NAS OS handle it by it self.
No change.
I can still use CMD/net use to map the drive and get CMD/dir access. But the drive is still inaccessible from the GUI file managers. (And I expect from other windows uses as such).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
