I just bought a Netgear ReadyNAS 314 and four WD Red 3.5 drives to put in it. I'm having some basic, probably very easy to resolve issues, but the manual (both physical and online) is extremely unhelpful.I've installed and plugged in the device, and powered on. It's connected to my internet router. When I start up my browser and go to readycloud.netgear.com it says "No devices discovered" - I've tried waiting for a while and re-scanning, and I've tried pressing the 'backup' button for five seconds and then rescanning, without any success. The display on the device lists an IP address; if I point my browser to that address I get an authentication request from 'ReadyNAS admin' asking for a user-name and password (which I don't have). The display also says "Resync Data 6.59%" and counting up - the manual doesn't say anything about this. I also installed RAIDar but it doesn't find my device either.I'm running Windows 7 and Chrome 32. I'd appreciate any help; right now I've a couple of questions which the manual doesn't address:1) When the display says "Resync Data" and a percentage, does that mean the device is formatting my drives? Do I need to wait for it to reach 100% before the device can be discovered? The drives are fresh from the store, so I haven't formatted or used them previously.2) RAIDar recommends that I make sure that my computer and the NAS are on the same subnet - I know how to identify my subnet mask on my PC, but I don't know how to find out which subnet the device is on.In addition to this, do you have any other troubleshooting tips I could try?Thanks for any input.

The resync is what you would expect to be happening. It is setting up the Xraid volume.You should be able to access the device during this process.The username is adminThe password is passwordWhat is you PCs subnet - it is probably 255.255.255.0Is the routers dhcp server on?What ip address is displayed? anyway if you can get to the login dialogue box you should be able to access the admin pages. There is a network tab wehere you will be able to see and/or change the network settings.I'm pretty sure the manual covers at least the username and password element of your problem.

Excellent, thanks for the quick answer. You were right - the username and password could be found in the manual, but only in the section on what to do if your device was discovered, so I didn't realize that it could be used here as well. Now I can access the device in the web interface, but I still can't discover it in the Readycloud interface or in the RAIDar utility - is this a problem?My subnet mask is 255.255.255.0, and my router's dhcp server is enabled... Looking at the admin http-page, I see that the NAS subnet mask is 255.255.248.0 (configured using DHCP) - I tried changing that to Static configuration and 255.255.255.0 but it's still not discoverable by ReadyCloud / RAIDar. Thanks so far; any other tips?

Your dhcp server is on a different subnet.What is the IP address of the dhcp server device?What is the PC IP address?What is the NAS IP address?The PC, NAS and dhcp server should have IP addresses that are the same except the 4th number, ie. 192.168.2.x and 192.168.2.y and 192.168.2.z.Raidar should still see the NAS if your PC can access it, that is strange, but so is that subnet mask?

This is what I get from IPConfig:DHCP server: 192.168.2.1IPv4 Address: 192.168.2.1From the NAS-display I get the IP address: 213.113.255.47I still can't get the ReadyCloud service or RAIDar to discover my device. And now I can't even access the NAS via my browser anymore, or get a response when pinging it. Any tips?

That is ip config on your PC?The PC and the dhcp server have the same IP address?How is the PC connected to your lan? Is it plugged in to the router?What is the IP address of the router- this will be in the router admin pages as LAN IP address?What range of IP addresses is the dhcp server allocating?There is some problem with your lan setup if that is the info you get from ip config.

Installing RN314 - Device not detected

18 Replies

Replies have been turned off for this discussion

vandermerwe
Master
Jan 26, 2014
The resync is what you would expect to be happening. It is setting up the Xraid volume.
You should be able to access the device during this process.
The username is admin
The password is password

What is you PCs subnet - it is probably 255.255.255.0
Is the routers dhcp server on?
What ip address is displayed? anyway if you can get to the login dialogue box you should be able to access the admin pages. There is a network tab wehere you will be able to see and/or change the network settings.

I'm pretty sure the manual covers at least the username and password element of your problem.
HenrikR
Aspirant
Jan 26, 2014
Excellent, thanks for the quick answer. You were right - the username and password could be found in the manual, but only in the section on what to do if your device was discovered, so I didn't realize that it could be used here as well. Now I can access the device in the web interface, but I still can't discover it in the Readycloud interface or in the RAIDar utility - is this a problem?

My subnet mask is 255.255.255.0, and my router's dhcp server is enabled... Looking at the admin http-page, I see that the NAS subnet mask is 255.255.248.0 (configured using DHCP) - I tried changing that to Static configuration and 255.255.255.0 but it's still not discoverable by ReadyCloud / RAIDar. Thanks so far; any other tips?
vandermerwe
Master
Jan 26, 2014
Your dhcp server is on a different subnet.
What is the IP address of the dhcp server device?
What is the PC IP address?
What is the NAS IP address?
The PC, NAS and dhcp server should have IP addresses that are the same except the 4th number, ie. 192.168.2.x and 192.168.2.y and 192.168.2.z.

Raidar should still see the NAS if your PC can access it, that is strange, but so is that subnet mask?
HenrikR
Aspirant
Jan 26, 2014
This is what I get from IPConfig:

DHCP server: 192.168.2.1
IPv4 Address: 192.168.2.1

From the NAS-display I get the IP address: 213.113.255.47

I still can't get the ReadyCloud service or RAIDar to discover my device. And now I can't even access the NAS via my browser anymore, or get a response when pinging it. Any tips?
vandermerwe
Master
Jan 26, 2014
That is ip config on your PC?
The PC and the dhcp server have the same IP address?
How is the PC connected to your lan? Is it plugged in to the router?
What is the IP address of the router- this will be in the router admin pages as LAN IP address?
What range of IP addresses is the dhcp server allocating?

There is some problem with your lan setup if that is the info you get from ip config.
HenrikR
Aspirant
Jan 26, 2014
I think you were right about something being wrong with my setup; even though it was nominally working, I think I had my wireless router plugged in wrong. I've simplified my setup now and unplugged the wireless router, and now RAIDar actually finds my NAS (with a green indicator). However, I still can't find it in ReadyCloud, and when I click 'setup' in RAIDar it tries to open up https://213.113.255.47/admin/ in Chrome, which gives me "This webpage is not available," so I still can't get to the admin pages.

Right now my setup is that I have an Inteno VoIP Gateway , which is connected to the fiber connection in my wall through one ethernet cable, to my PC through another, and to my NAS through a third. After removing the wireless router, ipconfig on my PC now gives me the following information:

IPv4-address: 213.113.251.159
Subnet Mask: 255.255.248.0
DHCP server: 213.113.248.1

The NAS still displays that it has the IP: 213.113.255.47 (which is also what RAIDar says) but it now also says "Cannot connect discovery server". So maybe a small step forward, but not quite there yet?
vandermerwe
Master
Jan 26, 2014
Removing the gateway will not help.
Was the gateway connected properly? Is it possible you had the NAS connected to the WAN port instead of a lan port?
Is this the internet connection you have been using to access the forums?
There is a WAN port to connect to your fibre connection, then 4 lan ports, 1 should connect to your NAS, 1 to your PC.
Connect to the gateway at 192.168.1.1.( from your PC) This is the default IP address given in the manual I found, it may be different(192.168.2.1), check your manual ( for the VoIP gateway)

The default login details for your VoIP gateway are username admin, password admin.
Log in to the gateway and look at the dhcp server.
vandermerwe
Master
Jan 26, 2014
When you removed the gateway, how did you connect the NAS to the PC?
....and your internet connection?
HenrikR
Aspirant
Jan 26, 2014
Hmm... Some of that works for me, some of it doesn't. Right now I have a cable from my fiber connection to the WAN port of my Inteno gateway, then my PC on the first port after that, and my NAS on the second port after that. That's how I get the connection I'm using now - before that my PC was connected through my Belkin wireless router which is now removed.

I'm not able to connect to 192.168.1.1, and I'm not able to connect to 213.113.255.47 - both of those just give me a 'page not found' response, both in Chrome and Internet Explorer.
vandermerwe
Master
Jan 26, 2014
The limited info I have found on an inteno VoIP gateway suggests that it is also a router.
Is this it?
http://www.inteno.se/store/tabid/141/ca ... fault.aspx

So, when you started the NAS was connected to the inteno and your PC to the belkin.
Which device has the dhcp switched on, or have you got both devices with dhcp switched on.
If the inteno was your dhcp server then you should switch it off on the belkin AND use a static IP address on the belkin.

There must be an IP address on which you access the gateway and on the gateway there should be a dhcp server setting.m you may have switched this off as you were using the belkin.
Maybe you should put the belkin back. If you do, you should plug your PC and NAS into the lan ports of the belkin and the belkin should be connected to the gateway using a lan port.
What then is the IP address of the belkin. Can you access the belkin admin pages and look at the dhcp server settings.

The fundamental problem you seem to have is that the NAS and PC don't seem to be getting IP addresses correctly.