NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RNRX4000 - ReadyNAS 2100 Is this capable of installing/running Plex?
looking into adding Plex to my home network, and wondering if trying to install Plex on my ReadyNAS 2100 is a wastenof time or doable? X-Rais2 Firmware Raidiator 4.2.28 1gb memory 4 disks w/ 8 TB...
wingnuttArk wrote:
looking into adding Plex to my home network, and wondering if trying to install Plex on my ReadyNAS 2100 is a wastenof time or doable?
X-Rais2
Firmware Raidiator 4.2.28
1gb memory
4 disks w/ 8 TB
The current version of plex won't work on your NAS, the plex folks only build software for ReadyNAS running OS-6 firmware.
I'm using the NAS for a home network. There are 3 computers and a bunch of peripherals on the network. 2 Win 10 units (workstation and a Surface 5 tablet) and a laptop running latest Debian Linux distro.
Network in a Starlink node, and all 3 computers and the NAS are connected via Cat 6 cables. If I initiate a connection on any of the computers, I can access the data on the NAS by logging in as admin. I can also access the data with default client using a media server (Jellyfin) which is installed on the Linux machine. If I try to connect with test users that I added, then I end up in password jail ... a User/Password box pops up, I enter the information, the box disappears, then pops back up in a loop.
NASReady 2100 with firmware 6.10.7
wingnuttArk wrote:
. If I initiate a connection on any of the computers, I can access the data on the NAS by logging in as admin. I can also access the data with default client using a media server (Jellyfin) which is installed on the Linux machine. If I try to connect with test users that I added, then I end up in password jail ... a User/Password box pops up, I enter the information, the box disappears, then pops back up in a loop.
- if you are using SMB, then is anonymous access enabled for the share(s)?
- When you are "looping", are you entering the credentials for a user account you have set up on the NAS
- If the NAS is using the same host name or IP address that it did before, then did you remove any old credentials stored on the Win10 machines (using the Windows Credential Manager)?
the anonymous user works fine since the Jellyfin server delivers requested content to the requesting client.
I have myself set up as a user account, and have several test accounts set up as users. When I try to access the main share as myself, or a test user, I get the loop. If I use the admin account, I get full access.
The loop occurs when I use either Windows box or the Linux box. I will have to check saved credentials on the Win10 machines, but I can report that I did a complete wipe of the Linux server and a complete new load of tge Linux Debian OS. No change.
There is no error message, just a repeat popup of the login box. I enter ID, box popup goes away, 2 seconds later pops back up. If I hit cancel, then the loop exits to password recovery process.
wingnuttArk wrote:
the anonymous user works fine since the Jellyfin server delivers requested content to the requesting client.
That just means that the server can access the data, since the Jellyfin clients would have their own authentication method (and get their content from the server).
wingnuttArk wrote:
When I try to access the main share as myself, or a test user, I get the loop. If I use the admin account, I get full access.
Note that anonymous access only applies when the NAS doesn't recognize the username. If the NAS does recognize the username, but the password is incorrect, then access will be denied even if anonymous access is checked.
Also, some usernames won't work. The username can't match a sharename or hostname. It also likely won't work if it matches an existing built-in account.
If you test with Windows, then one restriction to keep in mind is that Windows only allows one set of credentials to be used at a time with a given hostname or IP address. That can get in the way, as you don't necessarily see all open sessions from Windows. You can open command and then run net use * /delete /y to clear any open sessions. Note you can follow that with net use t: \\nas-ip-address\sharename /user:username userpassword (making the relevant substitutions). That will map the sharename to drive letter t.
Are you using SMB with the linux systems? Or are you using a different protocol?
awesome, Stephen. Had not occurred to me that my access as admin would be persistent. I used Powershell to enter the net commands, and - after several attempts to get the user/password entered in the correct format, I has working access to the share. Many thanks for solving that.
And yes, the default protocol on the linux machine is SMB
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
