ReadyNAS not available after moving to ATT Giga

[vfpeter]

I have been using ReadyNAS RNDP200U for many years with no issues. I recently moved to ATT Giga. Now suddenly I am unable to go to the main page using my browser. I get the error "Can't reach this page".

I can see the device on my ATT router home page.

p.s. I am using Eero for WIFI and disabled ATT router WiFi.

Thanks,

Pete.

[StephenB]

Can you access the shares from Windows (or OSX)?

[vfpeter]

Not any more. I could before the move.

[StephenB]

Is the NAS set up to use a static IP address?

[vfpeter]

Stephen,

It was static before the move. After the move to new router, it got dynamically allocated.

However, I went and configured the IP to be static again and made sure that the IP was the same. 

Because I cannot even get to the admin page, I am not able to do any diagnostic/troubleshooting. 

Thanks,

Pete.

[StephenB]

There's three configurations

-static (configured on the NAS with no DHCP involved)

-dynamic (address assigned by the router using DHCP)

-reserved (address reserved in the router, so the router always assigns the same IP address to the NAS with DHCP.

The most common cause of your problem is a static address that is not compatible with your new router's subnet.  For instance, if you assign a 192.168.0.x address when the router is configured for 192.168.1.x.

Do you think that is your situation?  If so, there are a couple of fairly easy fixes.

[vfpeter]

That is in the range of the IPs subnet range. I was using that as it was what I had before. 

So I went back to DHCP and let the IP assigned dynamically. Once I got the new IP, I made it static. I am still having the same problem. 

[StephenB]

Perhaps you have an IP address conflict?  (that is another device is using the IP address)?  Can you ping the address?

Perhaps go back to DHCP and then reserve the IP address in the router.

[vfpeter]

I got instant response when trying to ping that IP.

I also do not have any other device on that IP. 

p.s. I had already made that IP static for ReadyNAS.

[StephenB]

---

@vfpeter wrote:

p.s. I had already made that IP static for ReadyNAS.

---

Do you mean that you reserved it in the router?  Or configured it in the ReadyNAS admin ui?

[vfpeter]

I reserved it in ATT Router config. 

How do I access ReadyNAS Admin UI? I am not able to get through the default url of 192.168.1.142/admin from my PC.

p.s. My ReadyNAS is currently directly connected to ATT Router. 

[StephenB]

Normally it would be https://192.168.1.142/admin 

Do you see any shares if you enter \\192.168.1.142 in the address bar of windows file explorer?

Though it might be a long shot - have you tried reserving a lower address (perhaps in the .64-95 range)?  I used to have an ISP-provided actiontec router which included a coax bridge for my set top boxes.  It was hardwired to reserve the upper addresses of the subnet for coax-connected devices - but the configuration didn't show that anywhere.  

[vfpeter]

You are right about the admin url. I tried the ip in windows explorer and got the error "Windows cannot access \\192.168.1.142

I then reserved a lower ip 192.168.1.80. When I tried this, https://192.168.1.80/admin it still did not work. 

[StephenB]

But when you use DHCP with no reservation you can access everything?

Is the subnet mask the usual 255.255.255.0?

[vfpeter]

Correct, before I ran into this issue after my move.

DHCPv4 Netmask : 255.255.255.0

DHCP Server : On

DHCPv4 Start Address : 192.168.1.64

DHCPv4 End Address : 192.168.1.253

This is what I see on ATT Router for ReadyNAS:

MAC Address : 84:1b:5e:26:cf:6a

IPv4 Address / Name : 192.168.1.143 / unknown841b5e26cf6a

Last Activity : Sat Aug 5 09:37:21 2017

Status : on

Allocation  : static

Connection Type : Ethernet LAN-4

IPv6 Address : 2600:1700:1960:c4c0:861b:5eff:fe26:cf6a

Type  : slaac

Valid Lifetime : 1209600s

Preferred Lifetime  : 1209600s

p.s. Not that it would be the cause of this issue, I am now using Eero mesh and disabled wifi on ATT router. However, ReadyNAS is directly wired into ATT Router. 

[vfpeter]

The error I see when launching in browser (https://192.168.1.143/admin/) is this : 

The device or resource (192.168.1.143) is not set up to accept connections on port "https".

My laptop is on Eero wif with ip of 192.168.7.29. Will this be causing the issue?

[vfpeter]

I think I figured out what was wrong....

All my devices was on different newtwork (wifi of Eero mesh), whereas my ReadyNAS is directly connected to the main ATT Router via ethernet putting it on different network.

Once I connect my ReadyNAS to Eero device via ethernet, I can see it in RAIDar. However, I cannot get the admin screen to come up in my browser (http://192.168.7.39/admin/)

 In RAIDar, I see "Click setup" in top right side of the window. When I click on setup, I get message ReadyNAS is currently not configured with a volume. Will I lose my data if I go through with this?

[StephenB]

It sounds like you are double-routing (with the eero mesh is configured as a router).  You might consider setting it  up as an AP.

With the current setup, it's easier if everything connect to the eero.  

Try pinging 192.168.7.39 from that PC.  You can also try https://192.168.7.39/admin  If you are seeing browser security warnings, click through them.

[vfpeter]

I can ping it from my laptop. 

However, trying https://192.168.7.39/admin/ in browser, gives me the message " The remove device or resource wont accept the connection. It is not setup to accept connections on https.  

Is there anything I need to do on ReayNAS?

[StephenB]

---

@vfpeter wrote:

I can ping it from my laptop. 

However, trying https://192.168.7.39/admin/ in browser, gives me the message " The remove device or resource wont accept the connection. It is not setup to accept connections on https.  

Is there anything I need to do on ReayNAS?

---

If you can't log into the NAS web ui, there isn't much you can do on the ReadyNAS.

Maybe try powering it down, and then starting it up again?

[vfpeter]

I powered it up couple of times. I can see it in RAIDar. So why is it I cannot get to the admin GUI in browser?

[StephenB]

---

@vfpeter wrote:

I powered it up couple of times. I can see it in RAIDar. So why is it I cannot get to the admin GUI in browser?

---

That is the question.

RAIDar can find some devices that have IP configurations that don't match your network router - that's because is uses a multicast discovery protocol that generally does reach all devices.

Does the NAS respond to ping?

[vfpeter]

yes, it responds to ping. 

[vfpeter]

In RAIDar, now I see "Corrupt root" message. 

[StephenB]

---

@vfpeter wrote:

In RAIDar, now I see "Corrupt root" message. 

---

That is not a good sign.

Do you have a backup of the data?  If not, you should contact paid support (my.netgear.com).