ReadyNas Pro 6 not found on new computer

---

schumaku wrote:

 

StephenB doesn't ol'ReadyNAS OS already had the ability to restrict the access to shared folders to a specific client LAN IP address, a LAN IP address range, or a subnet?

---

I'd have to check in the manual to get the exact permissions/ACL.

But I am thinking the place to look first is the private home share.

CustomVideoLLC - there is an accounts page in Frontview.  It'd be useful to go there, and see what user accounts were set up on your NAS.  Expand the security section in the right pane of Frontview, and then select the user & accounts option.

Worth to configure an address in the 10.1.10.x/24 subnet and connect the other LAN interface, where you should be able to reach 10.1.10.21 (permitting I remember the IP addresses from the screenshots provided earlier).so for the PC different from .21, e.g. use .20.

From the GUI, see if there is another user ID.  If there is, that's likely the one that was used to map the drives.  If it's the same user name as you used to log into your old PC, then the password likely is too.  But if it's not, then the tech probably used the "map using other credentials" capability of Windows.  If you don't know the password for that user, you can always change it as admin via the GUI.

Another thing that appears to be getting in your way is that Windows only allows you to use one set of credentials with one network resource.  So if you log in as admin via Windows (doing so via HTTPS and the GUI doesn't matter), then you're not going to be able to separately log in as the other user.  That's what the bottom half of the "Access Denied" dialog is telling you.

And when it comes to logging in via Windows, Windows doesn't always play nice with Linux.  From what i can tell, as soon as you try to log in, Windows sends your Windows user name and password with that request.  If that's not a valid NAS user/password combination, Windows should ask for new ones.  But it often does not and you instead get an "Access Denied" dialog.  NET USE with the appropriate NAS user name via the CLI is the only way I know around that.

And as StephenB has been telling you, your admin privileges are somewhat restricted because you are using the default admin password.    I've always assumed that's a (not especially effective) security feature.

Good Morning! Sorry for the delay in responding... had some Father's Day Activities yesterday.

There is NOTHING listed under Users...

I changed the password for admin and now when I double click on the NAS-0E-D3-CF icon in the Network window I get this message...

Doesn't even show me the share folders anymore!

FYI - This is listed under the "Security Mode" tab in frontview...

Here's what's listed under "Share Listing"... 

What to do next...

Thanks!

Also, while I was clicking around, I noticed this screen...

Ethernet 2, where the cable is attached, says to use values from a DHCP server. Should I change this to "use value below" and type in the numbers from below, which you told me to use for the ethernet connection on the computer?

IPv4

IP Address 192.168.168.100

Subnet mask 255.255.255.0

Gateway 192.168.168.168

Preferred DNS 8.8.8.8

Thanks!

---

CustomVideoLLC wrote:

Should I change this to "use value below" and type in the numbers from below, which you told me to use for the ethernet connection on the computer?

---

No.  Just leave it as it is.

---

CustomVideoLLC wrote:

What to do next...

---

The fact that there are no user accounts on the NAS means that the files are not in a private home folder.  So appears to be ruled out.

There are two approaches for the next step.  The first is to run CMD (just enter it in the windows search bar) and enter the two commands I gave you before.

net use * /d /y
net use z: \\192.168.168.168\c /u:admin NAS-ADMIN-PASSWORD

substituting the new NAS admin password for the NAS-ADMIN-PASSWORD placeholder.

If that works, it will mount the NAS data volume to drive letter C.

Another approach is to run the Windows Credentials Manager.  Type "Credential Manager" in the windows search to find it.  Then select "Windows Credentials", and select "Add a Windows Credential".  This is in blue text in small print.

If there is a credential for  \NAS-0E-D3-CF listed there, then delete it. 

After checking for that, create a new credential for \\NAS-0E-D3-CF, entering "admin" for user name, and your new admin password for the password.  Be careful on the typing, particularly the \\.

Then try clicking on that icon again in file explorer.

Here's the results of the cmd window. What was supposed to happen?

In the Windows Credentials, there was a listing for "NAS-0E-D3-CF", as well as one for "192.168.168.168". I removed them both. Typed in the new ones as you said, and double clicked on the icon and got this again...

Thanks!

Ok. So, I logged out and logged back in. Now when I double clicked the icon I got this folder and I am able to look in ALL the folders now. However, there is nothing in any of them. Just some other empty folders or a README.txt message.

I've since moved this message to another computer. As I was typing this message, my workstation computer crashed. It went to a reboot mode, came up with a black screen that said "Start PXE over IPv4", then changed to "Start PXE over IPv6" then went into a boot screen that said "HTTP(s) Boot". Then went to Dell Support Assist where it is now scanning the system. What happened?

It had to Download SupportAssist OS Recovery.

Hope this isn't because of anything we did?

---

CustomVideoLLC wrote:

Here's the results of the cmd window. What was supposed to happen?

 

---

The data volume should now show up in file explorer as the "Z" drive.  So look on Z for your files.

There was no Z drive before the crash.

Since it's crashed, I've disconnected the NAS. My workstation is now constantly trying to reboot. It has gone through those same screens a few times. Now it keeps saying "No bootable devices found."

Gotta contact Dell.

Got the computer back up and running. There is NO "Z" drive listed.

Can still see the "NAS-0E-D3-CF" icon in Network window. 

Can still see the (now 5) shared folders. Nothing in any of them except other empty folders. The admin folder has a README.txt file in it that says...

"Only the admin user can access the home share (and home-snap if snapshot is active) containing all the private user shares. This allows the admin user the ability to easily backup user shares."

What to do next?

Thanks!

---

CustomVideoLLC wrote:

 

What to do next?

 

---

The Z drive mounting wasn't persistant, so the two "net use" commands above would need to be re-entered in order to see that again.  BUT, the credential manager did work, as you are now able to browse all the folders.

Unfortunately there appears to be no data on the NAS. 

Can you double check the "C" folder in particular, making sure all the folders are empty (other than the the text file in the admin folder)?  The "C" folder is the entire data volume.

Also, since you still have the old workstation, I suggest connecting ethernet from LAN port 1 of the NAS to that workstation, and take another look at the G drive.

Stephen wrote:

The Z drive mounting wasn't persistant, so the two "net use" commands above would need to be re-entered in order to see that again.  BUT, the credential manager did work, as you are now able to browse all the folders.

I reentered the commands... still no Z drive.

Stephen wrote:

Unfortunately there appears to be no data on the NAS. 

These are screenshots from the G Drive listed on the old workstation...

As you can see... there is LOTS of data on the NAS.

Stephen wrote:

Can you double check the "C" folder in particular, making sure all the folders are empty (other than the the text file in the admin folder)?  The "C" folder is the entire data volume.

There is NOTHING in the "C" folder except other empty folders

Stephen wrote:

Also, since you still have the old workstation, I suggest connecting ethernet from LAN port 1 of the NAS to that workstation, and take another look at the G drive.

Here are some other sharing properties for the NAS2 (G:) on the old system...

And here is how it is connected...

I now have the NAS hooked up to both machines via ethernet cables. Let me know if you need to look at something else on the old machine.

Thanks!

Run cmd on the old workstation and then enter net use

Then post the output in a reply.  That should show the network path that was used to mount it.  Which is where your data is.

Hey Stephen,

No dice there...

Doesn't the fact that it is listed under "Devices and drives" and not " Network locations" mean anything? It says it is a Local Disk. And the connection is named iSCSI?

Thanks!

---

CustomVideoLLC wrote:

And the connection is named iSCSI?

 

---

The iSCSI bit matters for sure.  Honestly I haven't done much with iSCSI, and I don't have any systems running 4.2.x firmware.

It is a bit odd that the network path starts with \\Up-premiere, since that is not the name of the NAS.  It could be a manually entered hostname.  I am guessing that the iscsi target is g based on the Window property screen, but I am not 100% sure.

Not sure if this will show you anything, but are you seeing any iSCSI targets when you go to Volumes->Volume Settings and then select the iSCSI tab?

Hi Stephen,

Here is the Disk Management screen from the old workstation...

I couldn't find "Volume Settings", but I did find the iSCSI Initiator Properties. These are the windows....

Does any of this help?

As far as the \\UpPremiere, when this was all first put together, we had a server and a few workstations, plus two NAS boxes at the time. One was attached to each workstation though, same as now, with a yellow ethernet cable. I don't have the server anymore, not for more than six years. Like I said, the NAS just kept on working as an external drive, so I just kept using it that way. 

Thanks!

FYI, I was asking you to look on the NAS (in frontview - the NAS web ui), not in Windows.

There are two paths to proceed.  

1. stay with iSCSI and attempt to create an iSCSI Initiator on the new PC that points to the NAS.
2. switch to using normal shared folders.

So far it's been tough sledding.  (1) likely would continue to be challenging.  (2) is simpler, but would require copying all the data off the NAS, destroying the iSCSI LUN on the NAS to free up space and then copying tthe data back. 

So I am not sure which way is best.

Is UpPremiere defined in the Windows hosts file (c:\Windows\System32\drivers\etc\hosts)?  If it's not, then it may be the name given to the iSCSI pool.

StephenB's idea of using the old PC to offload the data to a backup and then re-configuring the NAS (and switching to OS6) may be your best plan of attack rather than continuing to struggle to configure the new PC to access it.  As you have found out, the method used to store the data makes it difficult to recover from, and we don't even know yet if there is encryption associated with the iSCSI volume.  What would you have done if the old PC had failed, rather than just been replaced?  Or if the NAS had died?  Plus, you clearly don't have a backup, so the drive you offload to can become that backup that you maintain.

I guess one of the main issues here is what the security risk is if somebody were to break in and steal the NAS.  How valuable is the data on it?  What's the risk of it being compromised?  Was this all set up to prevent that thief from accessing the data?

Good Morning!

I could not open frontview on the old system. This is the screen I got from RAIDar...

When I clicked on browse, I got this...

I tried to connect to the NAS via Firefox, which I already had on that system and I couldn't connect. I kept getting the "This site is asking you to sign it" window, but admin and netgear1 would not work. Just kept coming back to this same screen.

When I cancelled the window, I got an "Authorization Required: This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required."

In response to Sandshark... This is what I got when I opened the "hosts" file...

Also, I ALWAYS backup the client data on other external drives. I have all the data currently on the NAS on other drives. 

What I was attempting to do was to continue to use this old NAS as an 11TB external drive as I have been for lo' these many years.

But... I have now come to the conclusion that this effort has come to an end. Thanks for trying! Thought it would be an easy fix to move this thing from one Dell computer to another, but apparently ReadyNAS made it way too difficult for that to happen! 

Again, thanks for the herculean effort!

Mike

---

CustomVideoLLC wrote:

 

But... I have now come to the conclusion that this effort has come to an end. Thanks for trying! Thought it would be an easy fix to move this thing from one Dell computer to another, but apparently ReadyNAS made it way too difficult for that to happen! 

 

---

Your IT tech didn't do you any favors when he set up the system for you.  It sounds like he didn't give you any documentation on what he did - and his decision to use iSCSI was questionable. You are also using an old ReadyNAS, which doesn't help.

It is possible to continue to use it, if you are willing to put in the time.The process is to

1. copy off the data to a USB drive using the old workstation
2. do a factory reset on the Pro 6, and set it up again.
3. copy the data back to a share on the Pro 6.

Step 2 could include converting the system to run 6.x firmware, which would eliminate the need for FireFox.

Or just copy the data to a USB drive, and use that with the new workstation.  Then you could remove the disks, and sell the NAS diskless.

---

Sandshark wrote:

Is UpPremiere defined in the Windows hosts file (c:\Windows\System32\drivers\etc\hosts)?  If it's not, then it may be the name given to the iSCSI pool.

---

No, it's the name of the iSCSI initiator, so the iSCSI "client" in SMB or SAMBA or Windows File Share terms.

The name of the target is certainly in the same config ... NEO ... in the Target tab. 8-)

Back then, using iSCSI wasn't bad decision when it came to video online editing.

 complete different concept than SMB shred folders.

PS. NEO: Nomen est omen 8-)

---

schumaku wrote:

---

Back then, using iSCSI wasn't bad decision when it came to video online editing.

 

---

What was bad is that the tech didn't leave any documentation/records on how he set the system up.  We still don't know whether authentication is used or whether the LUN is encrypted.