NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ran Into Problems A Using My RNDuoV2
Dear Forum Members First, had to use a new registration and email to actually make this post, for some reason I could not use my old info to gain access to this forum. Anyway, my problem is t...
Hi StephenB
Just have a couple of things to report, more of a "reporting info I found out".
Thing 1) I believe the error messages I am getting, when trying to access my original Plex database via the icon, strongly suggest a security problem rather than a crash. And as mentioned before, the problem started after a windows 11 update. Plus, my other two RNDuoV2's still work perfectly. However, I can still access my original databases via the networked mapped drives in file/windows explorer.
Anyway, as for new data, I only ever add music data to that RNDuoV2, which in the scheme of things, i.e. disk space, cpu usage, etc., is next to nothing.
Thing 2) I found out, more by accident than design, that the RNDuoV2's name is more than just a name, i.e. it permeates the properties of every network drive/folder mapped backed to the original databases on that machine.
I also found out that trying to amend the mapped drives, to matched the recently added new Name, was next to impossible and came with unexpected side-effects.
So, eventually (today) I changed the Name, on my number one RNDuoV2, back to it's original which (I hope) will mitigate (or do away with) the side-effects I acquired with original name-change.
I'm guessing the above info will not be of any use to anyone because the RNDuoV2 was last manufactured around 2011/12, and got a last Plex software update in 2015. So there cannot be that many RNDuoV2 users out there, even though the machine is a very good solid workhorse (and still commands premium prices on ebay UK).
And there endeth this part of my RNDuoV2 adventures.
UK Bob
This sounds like it's related to an issue that's plagued accessing a Linux-based NAS from Windows for some time -- Windows stops being able to find the device by name. There are two solutions, both of which require the NAS IP address stay fixed. Those are: just using the IP address instead of the name and adding the name to the Windows Hosts file. As for insuring the NAS IP address stays fixed, the best method is to reserve the address in your router. BTW, if you do use the Hosts file, the name you give it there doesn't really have to match the name you gave it on the NAS. In fact, you can create multiple aliases for the same IP address.
This sounds like it's related to an issue that's plagued accessing a Linux-based NAS from Windows for some time -- Windows stops being able to find the device by name.
No static IP address required - just enable CIFS readily available.
You can enable SMB 1.0/CIFS on Windows 10 or 11 by turning it on through the Windows Features menu or by running an administrator command.
Using Windows Features (GUI)
- Press the Windows Key + R to open the Run dialog box.
- Type optionalfeatures and press Enter to open the Windows Features window.
- Scroll down the list and locate SMB 1.0/CIFS File Sharing Support.
- Check the box next to it (make sure all sub-options like the client and server components are selected).
- Click OK and wait for Windows to install the required files.
- Click Restart now to reboot your computer and apply the changes.
Just enabling CIFS does not always work. CIFS requires a "master browser", but none of the devices on my network assume that role.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
