Re: ReadyNas Pro 6 not found on new computer

CustomVideoLLC · ‎2024-06-14

Hi, I hope someone can help me. This old ReadyNas Pro 6 unit (RNDP6000) was hooked up to my old workstation via Ethernet cable for many years. I've since upgraded to a new workstation, running Windows 11 Pro. I can't find any documentation on how to connect the unit to my new computer. I have it connected via ethernet cable. I tried connecting via LAN 1 and LAN 2. I've downloaded the RAIDar utility and it sees the unit. Status:Healthy. Firmware: 4.2.30. But the unit doesn't show up in the Network. Does anyone know how to connect these to a new workstation? Thanks!

CustomVideoLLC · ‎2024-06-14

Also this is all I got from the RAIDar utility. I can't use any of the buttons except for the RESCAN which does nothing, the ABOUT, HELP, AND EXIT. The top three buttons give me this window...

Help!

Thanks!

StephenB · ‎2024-06-14

Try connecting it to your router instead of directly to your PC.

The other option is to set up a compatible static IP address on the Windows PC (just for the ethernet port you connected to the NAS). Set the IP to 192.168.168.100, with a subnet mask of 255.255.255.0 and set the gateway to 192.168.168.168.

CustomVideoLLC · ‎2024-06-14

Stephen thanks for your help and your reply. The extender that is next to my computer only has two ethernet connections and they are both being used, so direct connect to the router is not an option.

I did the static IP address option. I can now see the ReadyNAS on the network page...

When I double click the image under storage, I get this window...

When I double click the image under computer...

I get this window...

None of these folders are what was there before on the old machine. I should mention at this point that I had it hooked up to the other machine in the LAN 1 port and the IP Address was 10.1.10.21 from that port. Would that make a difference in the folders I see?

Secondly, when I double click the "C" folder or "home" folder above, I get

I used "netgear1" as the password. I also tried my user and password for this computer and got this...

I feel like we're getting close, however, as you can see... still need some help here!

Thanks!

StephenB · ‎2024-06-14

FWIW, the 192.168.168.168 IP address you are seeing happens when the NAS cannot get an IP address using DHCP from your router.

@CustomVideoLLC wrote:

Stephen thanks for your help and your reply. The extender that is next to my computer only has two ethernet connections and they are both being used, so direct connect to the router is not an option.

When you said the NAS was connected to your old workstation, I assumed that you meant it was directly connected. If you are connecting both the NAS and the PC through the extender, then that is very different - both are already connected to your router.

So the static address option isn't the right path. While it should get you into the NAS, it will end up with your PC not reaching the internet.

However, what happens when you browse to https://192.168.168.168/admin ?

That should get you into frontview.

CustomVideoLLC · ‎2024-06-14

Thanks Stephen.

When I browse to "https://192.168.168.168/admin", I still get this page...

The NAS WAS connected to my old workstation directly via ethernet cable, via LAN 1 out of the NAS and the IP address was 10.1.10.21 (It still shows that on the readout on the NAS when I put the ethernet cable into LAN 1).

Currently, the router extender has two computers hardwired, one is the office computer, the other is this workstation.

The NAS is also NOW connected to the new workstation directly via ethernet cable. I have it via LAN 2 out of the NAS and the IP address was what the RAIDar showed.

Should I try to connect via LAN 1 out of the NAS? If so, I would need to reset the manual static IP to different numbers, right?

Wish there was some tech help available at Netgear for this, instead of doing it through the community.

Thanks

StephenB · ‎2024-06-15

@CustomVideoLLC wrote:
When I browse to "https://192.168.168.168/admin", I still get this page...

Unfortunately your screenshot is too small for me to read the error details on the second line.

When was the last time you accessed Frontview???

Your NAS doesn't support TLS 1.2, and most browsers now require that. That started around 2 years ago. Do you recall seeing that issue, and doing something about it? If you don't, then try installing FireFox. Set security.tls.version.min to 1 (browse to about:config and search for the setting). Then browse to https://192.168.168.168/admin

You will still get a security warning, because the certificate in the NAS is self-signed. But you can click through that warning.

There are better solutions to the TLS 1.0 issues, but let's restore access to the NAS before we do anything else.

schumaku · ‎2024-06-15

@CustomVideoLLC nothing you can do - neither with your much to modern Web browser(s) like Edge than as-is your modern Windows 11.

If you like to continue using that legacy NAS, you have to enable the legacy CIFS/SMB 1.0 protocol (consisting of two major components like CIFS/NetBIOS or NetBEUI for name resolution and discovery, as well as for the simple SMB 1.0 Transport protocol. There is a simple control available in the Windows Features settings designated SMB 1.0/CIFS File Sharing Protocol and as well the SMB 1.0/CIFS Client and SMB 1.0/CIFS Server - and don't forget not to untick the SMB 1.0/CIFS Automatic Removal part.

The other part of the solution might be to use Firefox and enable TLS 1.0 https://support.mozilla.org/en-US/questions/1101896

No need for a direct connection from a PC et all, just keep it operational on your network (LAN or Wi-Fi).

If not - the life of your decades old NAS is over.

@StephenB the ubiquitous TLS message that is...

The connection for this site is not secure

192.168.168.168 uses an unsupported protocol.

ERR SSL VERSION_OR CIPHER MISMATCH

StephenB · ‎2024-06-15

@schumaku wrote:

@StephenB the ubiquitous TLS message that is...

The connection for this site is not secure

192.168.168.168 uses an unsupported protocol.

ERR SSL VERSION_OR CIPHER MISMATCH

I was thinking that was it, but the bottom line was too blurry to be certain.

@CustomVideoLLC - after we regain access, we can apply an add-on to your NAS to get rid of this particular issue. You could alternatively migrate your NAS to OS-6. But the firefox workaround will get past it for now.

As @schumaku says, you also need to make sure the CIFS/SMB 1 client is enabled in "turn windows features on or off".

But there is also the DHCP problem (the 192.168.168.168 address) we need to resolve.

One step at a time, getting into frontview is the first step. Leave your network setup alone until we manage to do that.

CustomVideoLLC · ‎2024-06-15

Thank you both! The Firefox solution worked. Here is the screen I can now access...

It has been many years since I was on Frontview. I never had the need.

I am a video editor. This NAS was where I stored all the Raw video files for editing on Adobe Premiere. I've had this setup for about 10 years now (or more). I finally had to upgrade my workstation so I could allow the upgrade to Adobe Premiere v24. The old system was stuck at v23.

I did the SMB1.0/CIFS thing after reading about that step elsewhere...

I guess I should have mentioned that I do still have the old workstation, so I could still hookup the NAS to it, if needed, to make any changes to the box/software, etc.

Please let me know the next steps....

And Thanks!

StephenB · ‎2024-06-15

@CustomVideoLLC wrote:

Please let me know the next steps....

First check to see that your shares are all shown on the shares page in Frontview.

Next I suggest trying again to access the shares from file explorer or the windows command line.

If your admin password is NOT the default netgear1 then these commands should mount the entire data volume to drive letter Z

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

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

If everything looks ok, then we can move on to the DHCP issue.

schumaku · ‎2024-06-15

@CustomVideoLLC great, don't forget to take away the SMB 1.0/CIFS Automatic Removal to avoid the unexpected.

CustomVideoLLC · ‎2024-06-15

Ok. I don't think this NAS ever had any shares. It was setup as the G-Drive on my old system. (Someone other than me obviously set it up!) When I moved locations about 6 years ago, the NAS was still working when directly plugged into the old system via ethernet port 1. I accessed it as I would any other connected external drive.

Here is the setting for ethernet 1...

and the setting for ethernet 2...

This is what I got when I accessed the NAS via file browser...

As far as I know the "admin and netgear1" are the only user password combo.

So the commands did nothing in the command prompt window.

Thanks

StephenB · ‎2024-06-15

@CustomVideoLLC wrote:

Ok. I don't think this NAS ever had any shares.

If you could access it over ethernet, then it had shares. These are either public or private home shares.

You need to find your files...

@CustomVideoLLC wrote:

This is what I got when I accessed the NAS via file browser...

You accessed it the wrong way then (using your browser and NOT file explorer).

Try again with file explorer. Enter \\192.168.168.168 and see if you can get a list of shared folders (e.g. shares!) to access. The \\ is important. If you use // by mistake you'll end up with your third screen shot.

@CustomVideoLLC wrote:

As far as I know the "admin and netgear1" are the only user password combo.

You could try changing the admin password via frontview to something else, and then try the two commands I posted above.

@CustomVideoLLC wrote:

Here is the setting for ethernet 1...

This is a static address that you must have set up yourself.

Do you recall doing it?

Do you know what IP address range your current router is using?

CustomVideoLLC · ‎2024-06-15

The IPv4 address is 192.168.1.40.

I did NOT set this up the first time. We had a tech who did it for us back in the day.

When I open with file explorer OR double click the icon below...

I get this screen with these shared folders...

Backup and media have NOTHING in them. C and Home need a user/password. Trying admin/netgear1 does not work. Tells me "access is denied". Trying my user/password for this computer tells me...

Again, on my old system, this NAS and my old computer were originally setup in a WORKGROUP, but as I said, once I moved locations, the NAS was working just by hooking it up to the computer via a yellow ethernet cable.

Also, this is the first time I am EVER seeing these "shared" folders. Like I said before, this NAS was setup as the "G" drive on the old system. I just double clicked on it and it opened to a window with regular file folders, nothing like these shared folders.

Thanks!

StephenB · ‎2024-06-16

@CustomVideoLLC wrote:

Also, this is the first time I am EVER seeing these "shared" folders. Like I said before, this NAS was setup as the "G" drive on the old system. I just double clicked on it and it opened to a window with regular file folders, nothing like these shared folders.

The tech you used the first time must have mapped one of the shares to a drive letter. Not sure which one, so you need to figure out where the data is. I am thinking he might have used one of the "private" shares in Home. But that is just a hunch at this point.

@CustomVideoLLC wrote:

I get this screen with these shared folders...

Backup and media have NOTHING in them. C and Home need a user/password. Trying admin/netgear1 does not work. Tells me "access is denied". Trying my user/password for this computer tells me...

Do you know the user/password for your old computer? Or was it set to automatically log you in? Let us know the user name.

BTW, netgear1 is the default admin password. It can't be used to access C or Home, which is why I suggesting changing the admin password to something else in Frontview.

@CustomVideoLLC wrote:

The IPv4 address is 192.168.1.40.

I did NOT set this up the first time. We had a tech who did it for us back in the day.

Not sure which IP address you mean. Are you talking about the computer's address?

The tech likely set up the static 10.x.x.x. address on the NAS, and set up a compatible 10.x.x.x IP address on the ethernet port you were using on the old workstation.

schumaku · ‎2024-06-16

Whatever was mapped to your old computer as a G drive letter - it certainly was a shared folder on your NAS. This was and still is the key for any NAS, Windows or Apple OS file shares as it's part of the design.

@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?

StephenB · ‎2024-06-16

@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.

schumaku · ‎2024-06-16

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.

Sandshark · ‎2024-06-16

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.

CustomVideoLLC · ‎2024-06-17

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!

CustomVideoLLC · ‎2024-06-17

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!

StephenB · ‎2024-06-17

@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.

StephenB · ‎2024-06-17

@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.

CustomVideoLLC · ‎2024-06-17

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!