ReadyNAS 104 LCD Error: "Cannot connect discovery server"

Her the same problem after upgrading to 6.1.3.

DHCP does not work anymore, so I entered a static IP address. This makes the NAS accessible from the LAN.

Problem though is in the DNS settings. I can enter 2 DNS servers, but the are not saved in the config of the unit. Next time I open up the network settings page, the DNS servers are empty again.

I think this (and DHCP-problem) is a bug in 6.1.3

Who can comfirm this behaviour?

I am running 6.1.3 on my RN102, and DHCP is working fine, with no issues.

I also have this same problem

I have not found a solution for this minor issue yet. Perhaps it only shows up with a static IP set? (The NAS I'm using is going into a non-DHCP environment so I don't even have DHCP as an option.)

Had this problem since latest update (6.1.4), (sort of) solved it (for me) today. This is how I did it:
Do note; it ain't a pretty fix, but it works for the time being.

The problem, like most of you will know by know comes from the fact that the DNS server can't be set and the machine will only take it's default DNS (127.0.0.1, ::1).
It looks like the OS just forces its DNS settings.

What I did to fix it:

Machine: Netgear ReadyNAS 104(00)
ReadyNAS OS: 6.1.4
Preformed from: OSX 10.9
IP Settings: NAS has a static IP given via the web interface.

1. Turn on SSH via the webconsole

2 SSH to the NAS

iMac-van-Henk-Jan-2:~ JustHenk-Jan$ ssh root@xxx.xxx.xxx.xxx
root@xxx.xxx.xxx.xxx's password: 

Replace the xxx.xxx.xxx.xxx for the IP of your NAS.
it will prompt for a password, this is the same as the pass you use to logon to you web interface.

3. Let's have a look at your conf file, it should look something like this:

root@JustNAS_01:~# cat /etc/resolv.conf 
# Generated by Connection Manager
nameserver 127.0.0.1
nameserver ::1

If it has more ip's, this solution probably ain't gonna work for you.

4. Time to edit the /etc/resolv.conf file:
Unless you have installed Nano you'll probably have to work wit VIM, take a look at the instruction over here: https://wiki.debian.org/vim.

Open vim:

root@JustNAS_01:~# vi /etc/resolv.conf

Now enter your preferred DNS servers:

# Generated by Connection Manager
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 198.153.192.40
nameserver 198.153.194.40

nameserver 127.0.0.1
nameserver ::1
~
~
~
~
~
~
~
~
~
~
~
~
~
~
- /etc/resolv.conf 1/9 11%

5. Save and Close VIM (See instruction on the debian page how to controle VIM) and exit the SHH Shell. This should be enough to do the trick.
You can check by going to the web interface and clicking on "Check for updates", if it prompts the screen that you're update you will have connection to Netgear, and therefore a good connection to a DNS server. You will also note that the error message on the screen has gone away.

HOWEVER:
Like I said it's a dirty fix for 2 reasons:

First of all; by using ssh on your nas NETGEAR may refuse service when encountering problems.

The other problem is; as soon as you reboot the nas, the OS will override the settings you have made, and therefore you will have to preform these steps all over again.

Hope this will help some people out. But do keep in mind, this ain't a permanent fix. I sincerely hope Netgear will solve this problem asap.

Best of luck to all of you!

Disclaimer: The fact it worked for me isn't a guaranty it will work for you.

Hello all,

Sorry to revive a dead post. I was having this very same problem and with the help of hknobbe's suggestions, I was able to solve the problem without the risk of voiding the warranty.

You'll basically be doing what he said, specifying a DNS server, bud doing it through the web interface.

step 1)

log into the web interface using the ip address of your NAS

step 2)

navigate to the network tab

step 3)

select the gear next to the ethernet cards you are using
select settings from the little popup window

step 4)

select the dns tab
click the +

add 8.8.8.8 as a dns server


Voilà!!


I'd again like to thank hknobbe for helping me realize this solution.


PS, my NAS was out of warranty but I thought I'd use the live chat option to see what they could suggest. They were useless. It was a waste of time.

hknobbe wrote:

Had this problem since latest update (6.1.4), (sort of) solved it (for me) today. This is how I did it: Do note; it ain't a pretty fix, but it works for the time being. The problem, like most of you will know by know comes from the fact that the DNS server can't be set and the machine will only take it's default DNS (127.0.0.1, ::1). It looks like the OS just forces its DNS settings. What I did to fix it: Machine: Netgear ReadyNAS 104(00) ReadyNAS OS: 6.1.4 Preformed from: OSX 10.9 IP Settings: NAS has a static IP given via the web interface. 1. Turn on SSH via the webconsole 2 SSH to the NAS iMac-van-Henk-Jan-2:~ JustHenk-Jan$ ssh root@xxx.xxx.xxx.xxx root@xxx.xxx.xxx.xxx's password: Replace the xxx.xxx.xxx.xxx for the IP of your NAS. it will prompt for a password, this is the same as the pass you use to logon to you web interface. 3. Let's have a look at your conf file, it should look something like this: root@JustNAS_01:~# cat /etc/resolv.conf # Generated by Connection Manager nameserver 127.0.0.1 nameserver ::1 If it has more ip's, this solution probably ain't gonna work for you. 4. Time to edit the /etc/resolv.conf file: Unless you have installed Nano you'll probably have to work wit VIM, take a look at the instruction over here: https://wiki.debian.org/vim. Open vim: root@JustNAS_01:~# vi /etc/resolv.conf Now enter your preferred DNS servers: # Generated by Connection Manager nameserver 8.8.8.8 nameserver 8.8.4.4 nameserver 198.153.192.40 nameserver 198.153.194.40 nameserver 127.0.0.1 nameserver ::1 ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ - /etc/resolv.conf 1/9 11% 5. Save and Close VIM (See instruction on the debian page how to controle VIM) and exit the SHH Shell. This should be enough to do the trick. You can check by going to the web interface and clicking on "Check for updates", if it prompts the screen that you're update you will have connection to Netgear, and therefore a good connection to a DNS server. You will also note that the error message on the screen has gone away. HOWEVER: Like I said it's a dirty fix for 2 reasons: First of all; by using ssh on your nas NETGEAR may refuse service when encountering problems. The other problem is; as soon as you reboot the nas, the OS will override the settings you have made, and therefore you will have to preform these steps all over again. Hope this will help some people out. But do keep in mind, this ain't a permanent fix. I sincerely hope Netgear will solve this problem asap. Best of luck to all of you! Disclaimer: The fact it worked for me isn't a guaranty it will work for you.

Good day,

I recently purchased a Netgear ReadyNAS 104. I utilize a static configuration & my network setup as follows:

Netgear Cable Modem > ASUS RT-N56U Router <> TP-Link Gigabit Switch > Netgear ReadyNAS 104 (Firmware 6.2.2)

ASUS RT-N56U Router LAN IP: 192.168.1.254
Netgear ReadyNAS 104 IP: 192.168.1.199

ASUS Router > main PC (192.168.1.2)

ASUS Router <> TP-Link Switch

TP-Link Switch > server (192.168.1.5)
TP-Link Switch > Netgear (192.168.1.199)

As indicated above, I have a server (192.168.1.5/255.255.255.0/192.168.1.254) connected through the Switch and am able to connect to the ReadyNAS web interface on 192.168.1.199 from either main PC or server with no connectivity issues whatsoever.

For some odd reason, the Netgear display indicates "Cannot connect discovery server". As some have suggest adding DNS servers [8.8.8.8] should fix this problem, however even after a reboot of the Netgear, the same message still exists.

I have scaled the forums looking for answers, but there does not seem to be a definitive solution. If I may please rack the brains of community members and any tips/tricks/feedback to solve this would be greatly appreciated. Cheers :)

Seems like the gateway address is missing (192.168.1.254) in your ReadyNas. Not sure how to set this, but if you switch to dhcp it will be taken care off! (And you can still fix the Ip address when using dhcp...)

Sent from my SM-P900 using Tapatalk

Thanks for the prompt reply.

Firstly, as stated, my network is setup in a static configuration, DHCP is NOT an option. Secondly, to clarify, the Netgear interface (eth0) is setup as follows:

Configure IPv4: Static
IPv4 Address: 192.168.1.199
Subnet Mask: 255.255.255.0
Router: 192.168.1.254
Configure IPv6: Disable

Any other suggestions?

Are you getting a connectivity error when you ask the NAS to look for a firmware update?