NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
sbonds
Oct 12, 2013Aspirant
ReadyNAS 104 LCD Error: "Cannot connect discovery server"
It seems to work fine, but this cosmetic problem covers up the name/IP on the LCD and keeps the LCD lit which will burn it out sooner than would be ideal. This is on a ReadyNAS 104 running firmware 6...
standarshy
Jan 04, 2015Tutor
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.
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 NASiMac-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.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!