NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
kbachler6
Dec 04, 2019Aspirant
RN 314 Issues after updating to OS 6.10.2
After updating to 6.10.2, I can no longer see any network shares other than the Home folder. Prior to updating, I had a share named Home; that is now part of the Home folder, and appears there when ...
- Dec 05, 2019
On Home-1 it might be best to create a new share, copy the contents of Home-1 into it, delete Home-1, and then rename the new share (to something other than Home).
On the main issue, try running the Windows Command prompt and enter
net use * /delete
net use t: \\nas-ip-address\data /user:admin nas-admin-password
using the real NAS ip address and admin password of course. Be careful on the typing - particularly spaces and the slash direction.
The first command closes any network sessions open on the PC. The second maps the full data volume to drive letter T. You should see all the shares, Data, and Home on that drive letter if it works.
StephenB
Mar 03, 2020Guru - Experienced User
kbachler6 wrote:
I recently had a failure of my Surface Pro, and had to replace it. The new Surface Pro had exactly the same issue. Using the mapped drive via the command-prompt names allows me to access the files; however, the NAS 314 is still not accessible using the NAS-name.
Can you reach the web admin ui by browsing to https://NAS-name/admin ?
If not, the next steps are to
- reserve an IP address for the NAS in your router
- enter the NAS-name and associated IP address in your windows hosts file
The hosts file is located in %WINDIR%\system32\drivers\etc\. You'll need to open Notepad as admin, and then navigate to that folder to edit it. Enter the IP address first, then the NAS-name (separate them with a tab).
After you reboot the PC you should be able to access the NAS by name. It still might not show up in the file explorer left pane though.
If you can access the web admin ui by name, then try opening the Windows Credentials Manager on the surface and create a Windows credential for the NAS that uses a username on the NAS and it's associated password.
kbachler6
Mar 03, 2020Aspirant
Thank you. The NAS had been reserved, but I had not added it to the hosts file. Doing so addressed the issue.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!