NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
No Acces and System reset not working
Hey guys, I have annother extremely annoying problem.
I unplugged my ReadyNas Duo v2 from its network to take it home to access
my data locally. Now I cant access it.
Not with direct connection to my notebook, not via switch and not via router.
The IP of the NAS was set manually to 192.168.5.4 in 255.255.255.0. I cant even
connect if I use 192.168.5.x for my notebook (without DHCP).
I cant ping it and even my router doesnt detect it. And RAIDAR doesnt detect
it anyway (Raidar NEVER worked for me).
My idea was to reset the System bei holding the "SYS"-Button on the
back for 5 seconds while booting. But it shows no reaction, the HDD
diodes dont blink. Even if i hold the button for nearly 10 seconds.
Is there any solution to access or to reset the System? Or am I doing
something totally wrong?
Greetz,
Enfreyer.
I unplugged my ReadyNas Duo v2 from its network to take it home to access
my data locally. Now I cant access it.
Not with direct connection to my notebook, not via switch and not via router.
The IP of the NAS was set manually to 192.168.5.4 in 255.255.255.0. I cant even
connect if I use 192.168.5.x for my notebook (without DHCP).
I cant ping it and even my router doesnt detect it. And RAIDAR doesnt detect
it anyway (Raidar NEVER worked for me).
My idea was to reset the System bei holding the "SYS"-Button on the
back for 5 seconds while booting. But it shows no reaction, the HDD
diodes dont blink. Even if i hold the button for nearly 10 seconds.
Is there any solution to access or to reset the System? Or am I doing
something totally wrong?
Greetz,
Enfreyer.
14 Replies
Replies have been turned off for this discussion
- Try removing and reinserting the drives (with the NAS powered off!). They might have gotten jostled in transit.
- Same problem :(.
The diodes are constantly lighting 3 or 4 seconds after powering on. It doesnt care
if I push (and hold) the "SYS"-Button or not. - I am thinking you should enter an on-line support case at support.netgear.com
- Thanks, maybe I will do this if its necessary.
Update:
Yesterday I went back and connected the NAS again with its original Network.
-> now it works fine again.
I think the reason for the failed access was, that the NAS used 192.168.1.1 as DNS,
but 192.168.5.4 as own IP. Maybe the different adress ranges caused problems
while trying to access.
I now added 192.168.5.1 as second DNS and test it soon.
But I dont understand why I cant reset the Firmware.
Maybe because I installed a non-official Firmware in order to get access to
the FTP functionality? May this offend the Reset-Function? - Do you have a link to this non-official firmware?
The boot menu instructions for the v2 are different to the v1. See the FAQ or the hardware manual
This is a very unusual network config.Enfreyer wrote:
I think the reason for the failed access was, that the NAS used 192.168.1.1 as DNS,
but 192.168.5.4 as own IP. Maybe the different adress ranges caused problems
while trying to access.
I now added 192.168.5.1 as second DNS and test it soon.
Is your router 192.168.5.1? Do you have a device on your own network which uses 192.168.1.1?
If you are using 192.168.5.x private addresses, then 192.168.1.1 shouldn't be configured as a DNS server at all.StephenB wrote:
This is a very unusual network config.
Yeah, I had to change my routers IP-Adress to 192.168.5.1 due to port forwarding problems (to
share my NAS via ftp online). It didnt work with 192.168.1.1 as routers IP. If I remember
correctly it was because of the IP of my modem (which was 192.168.1.1 too).StephenB wrote:
If you are using 192.168.5.x private addresses, then 192.168.1.1 shouldn't be configured as a DNS server at all.
In the DNS config menu I can set in the first three lines "Domain Name Server *: ", and in the last
line I can set "DNS-Server (Domain Name Service): ". What are the differences? Is the last one the
adress for the internal DNS?
@mdgm: I try to find it again ;).
The Radiator Version is RAIDiator 5.3.5, but I'm very sure I installed something inofficial.
That would explain it. But you should be aware that your "modem" is actually functioning as a NAT router. 192.168.1.1 is a private address which cannot be routed over the public internet. Does your modem have more than one lan port? What model/brand is it?Enfreyer wrote: ...If I remember correctly it was because of the IP of my modem (which was 192.168.1.1 too). - Are you sure about that?
My Modems IP is 192.168.1.1 and my Routers IP is 192.168.5.1.
Im forwarding ports from the Router to the NAS IP (192.168.5.4).
(brand of the router is Thomson. I will look for the model as soon as I can enter the room ;) ).
Im doing a portscan now ^^.
Yes. if your modem's address is 192.168.1.1, then it is really a gateway (modem+router combined).Enfreyer wrote: Are you sure about that?
If it only has one LAN port then it could have a passthrough mode which would make port forwarding easier. If you have two routers back-to-back then you need to configure port forwarding in both (or alternatively put the "back end" router in the DMZ of the first).
I have this same constraint - my ISP (Verizon) requires that I use their modem in order to get TV services (channel guides, video on demand, etc), and also has an internal IP address of 192.168.1.1. My "real" router is behind that (a netgear R6300) Everything works ok, but I need to be careful when port forwarding.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
