OK, I have unpacked my old Duo-v2 (rnd2000-200NAS) again to set it up to go live with my Brother on his LAN. I have upgraded its' f/w to v5.3.8, host name, and modified/added some shares. I chose to use a pair of WD10EFRX drives. Sadly one of the drives arrived DOA (SMART errors on initial 'Disk Checks'). Fine. An RMA is in process as I write this beg for help. I chose XRAID-2 and formatted the single 1TB drive for use. Yes, the DUO came up as 'non-redundant! The old DUO-v2 lives again with its' new WD RED 1TB drive. I will learn about Expansion when the replacement arrives. This note is about today's trouble.Today, I am trying to change the NAS's IP address. Somehow, this NAS seems locked to 192.168.168.168. I can not seem to change in ip addy to what I wish it to be.I have read, and re-read both the current hdw UM and the current sw UM. I've followed the warnings, cautions, and am tentatively dealing with the new Dashboard (which I have to agree is much better than my first experience at v5.3.3).What am I missing?????? I have tried to change the default 'DHCP assigned ip addy' to an assigned ip addy 5 times now. I have tried to change the default ip addy using Dashboard without change now. Is there another Dashboard bug I am unaware of?? I have done this action to my other 3 ReadNAS already, so I'm sorta familiar with the process.I use my main PC (ip addy changed) connected to a Netgear GS116NA switch (port 08) to the Duo-v2 (port 13). The Netgear switch is only 10 days old. All cabling is CAT6. At this point, I am grumping clueless. The docs tell me how to do this. I follow them, and, nothing happens. This DUO-v2 remains locked a 192.168.168.168 and will not change. Something is amiss. Help!Yes, I can still be convinced that the base DUO-v2 may need to be replaced under warranty. I am getting cranky, but, I'll be patient.

It's not entirely clear to me what you are trying to do, so my reply covers 2 possible scenarios:Your Duo is not getting a dhcp assigned address (see below), even if it was you cannot change the dhcp assigned address from the dashboard, you would need to do this using your router by reserving an address for the duo. The IP address you give (192.168.168.168) is what the readynas uses if it cannot get a dhcp assigned address. Is the readynas on the same subnet as the dhcp server? Is there a router with dhcp function? Is the dhcp turned on? Does the router have any filtering such as MAC address filtering on?If you are already trying to set a static address then:I assume you might want to set a static IP address, rather than have a dhcp assigned reserved IP address.Tell us exactly how you are changing to a static IP address.You are selecting "Use the following address" and then entering an IP address that is compatible with your lan, the correct subnet mask and gateway as well as dns addresses.You then click apply.Could you tell us exactly what you are entering in these fields, and also what your PC IP address, router lan IP address and the lan subnet mask are.

@Vandermerwe,First, I agree that this NAS is NOT getting an IP addy from a DHCP operating on my LAN. Simple answer is that I do not use a DHCP at all anywhere on my LAN. Never have, and, I do not intend to start now. The DHCP server of the router is disabled. I have never used a DHCP server. On my LAN I statically assign ip addy's in the private class A series of 10.0.0.x series, but, I use a subnet mask of 255.255.255.0. I have been maintaining my private home LAN this way for the past 25 years.My PC ip address is 10.0.0.x; as in my router's ip addy. All works very well. The Duo displays an ip addy of 192.168.168.168. This is its' default addy. I know this, so, I admin my PC's ip addy to 192.168.168.x to speak with the NAS via my LAN. And, I can speak with the NAS, login, and get to the f/w's Dashboard. All as expected so far. Back in FEB 2012 when I bought this Duo-v2 new, I was able to use its' RAIDiator v5.3.3 to change all the network settings using a ghastly Dashboard. I also upgraded its' f/w to v5.3.5. After two weeks of trial and error, I decided to put the Duo back in the box and retire it. I now wish to give it to my Brother.Yes, when I view the DUO's Dashboard under System/Network I do see that it is set to "Get IPv4 address from DHCP." I change this to "...use this IPv4 address" and then I click Apply. Then, I click the black X to the right of the current ip addy. The box goes blank; so I click the box and enter the IPv4 addy i wish to use, 192.168.0.x. I also change the sub-net mask to 255.255.255.0, and, the gateway address to 192.168.1.x (which is the ip addy of my brother's router (and gateway) and click Apply again. No, I am not entering any addresses for my Brothers DNS servers simply because I do not know what they are yet.I do understand that you say I can not change this Netgear assigned static address without mucking about in my router to 'play DHCP.' I find this counter to my ReadNAS experience since I started using a Duo-v1 in 2008. Since then I have added an Untra 2 and an Ultra 2+. On all three of these current ReadyNAS I have manually assigned network specs using RAIDar Frontview/setup.The answers to your 3d paragraph are all NO! I do not use/allow a DHCP server on my home LAN. I statically assign all ip addresses, subnet masks, gateway addresses, and DNS server addresses.Lastly, why do you ask me for my chosen ip addresses in your closing paragraph? I consider this private information and not germain to my question. Please explain why you wish to know all this data.

Why are you using 192.168.0.x for your Nas when the router is 192.168.1.x?The Nas may not be accepting this , can you not try 192.168.1.x for the Nas?Is your PC IP address 192.168.1.x or 192.168.0.x?I don't care what anyone's LAN IP addresses are, most people use the same range of addresses so this is not really private information. It is useful to know this information when trying to solve a problem like this.

NASNoob wrote:...Lastly, why do you ask me for my chosen ip addresses in your closing paragraph? I consider this private information and not germain to my question. Please explain why you wish to know all this data.NASNoob, I would have asked for it if he had not. If you ask for help, you will get questions, and some of them may seem irrelevant to you. But (a) sometimes they are relevant (not always) and (b) we only have the information in your posts to go by.-your 10.0.0.x addresses (as you ought to know) are not publicly routable, Those addresses are reserved for private use, and your devices cannot be reached over the internet using them. My pro is 10.0.0.10, my duo is 10.0.0.11, my nv+ is 10.0.0.12, my RN102 is 10.0.0.13. That information does not let you reach any of my gear, so it is totally safe for me to tell you those addresses.-A lot of people who post here with static address issues have absolutely no idea how IPv4 addresses, gateways, and subnet masks are constructed. So confirming that the IP addressing is sensible is actually an important step. Many of them also use a mix of DHCP and static, and then lose connectivity when they replace their router, and don't why.-The normal subnet mask for 192.168 addresses is 255.255.255.0. With that mask, all local addresses must be identical in the first 3 fields - and that includes the gateway address. So you need to be consistent about 192.168.0.x or 192.168.1.x. It is simplest to just enable dhcp, and have your brother set the address if he wants to. Personally I prefer address reservation in the router combined with dhcp. It makes things much easier esp. with my mobile devices that connect to various networks.

Agree with StephenB, also if you don't yet know the ISP DNS addresses you can just enter the router IP address in one of the DNS address fields.Perhaps take the Nas to your brother's LAN and complete the network setup there if this is feasible.

Duo-v2 upgrade HELP | NETGEAR Communities

16 Replies

Replies have been turned off for this discussion

NASNoob11

Aspirant

Sep 07, 2013

vandermerwe wrote:
The purpose of testing the dhcp assignment is to make sure the NAS can get an IP address other than 192.168.168.168.
You have made it very clear that you don't want to use dhcp in your earlier posts.
I also use static ip addresses only.
Good luck, try the beta, you seem to have given up so you don't have anything to lose.

vandermerwe wrote:
The purpose of testing the dhcp assignment is to make sure the NAS can get an IP address other than 192.168.168.168. You have made it very clear that you don't want to use dhcp in your earlier posts. I also use static ip addresses only. Good luck, try the beta, you seem to have given up so you don't have anything to lose.

Vandermerwe,
I had a previous note to you that somehow got killed when I somehow got logged off the forum. I got a phone call from an old friend before I clicked 'Submit." I apologize.
In any case, I do understand your feelings, even though I still stubbornly choose not to test DHCP. I am happy to know that you also do static assignment of ip addy's.
I accept that I am very stubborn on trying various network related stuff. I think I've learned enough to do this task; still learning about sub-net masks, however.
I do believe that the DUO-v2 and/or its' f/w has a serious bug that still needs to be killed. Fine. Ultimately I may choose another Readynas hdw platform to build my Brother's NAS upon.
I had trouble with this DUO-v2 back in FEB12 when I bought it. That's why it lived in its' box since now. I figured just maybe I'd get lucky. Nope.
Yes, I will try the new beta f/w v5.3.9-T5. This can't hurt anything. Yes, I'm also looking a hdw platform replacements and have raised threads on our forum. I am trying to avoid choosing a Synology choice at this time. At this point, I'd like to just end this thread; but, I will share my RAIDiator v5.3.9-T5 results here post trial/error.

Believe me, I truly appreciate your help and patience. I will solve this issue one way or another.

vandermerwe
Master
Sep 07, 2013
Please tell us you're going to try the possible solution in the link that StephenB has found for you.

NASNoob11

Aspirant

Sep 07, 2013

StephenB wrote:
NASNoob - just searched the forum, and found there is someone else who reported your issue with the v2: viewtopic.php?f=20&t=71645&p=397902&hilit=static+address+v2#p397902

I don't see a resolution posted, but you might want to submit a request at support.netgear.com, and let us know what they say.

EDIT: There might be a resolution, but I don't think you will like it... viewtopic.php?f=65&t=61031&p=354031&hilit=static+addresses+v2#p353901
It seems there is a bug if you try to set a static IP without first assigning the details using DHCP. The solution is to allow the unit to get an IP and gateway using DHCP first. You can then change all the static IP settings back to whatever you need.

StephenB,
I read both of your shares. Yes! That is the issue. I just replied to Vandermerwe about this thread. I will share results post upgade to RAIDiator v5.3.9-T5 on the DUO-v2. At least this function still does work! LOL! If that is not helpful to this current glitch, I will start to look for a new hdw platform for my Brother's NAS. I am looking at the RN102, and, the RN312, ATM.
Thank you for your counsel and patience. I do realize that I have network stubbornness. I don't have a fix for that. Perhaps I will mellow with age; but I am 65 now, and I don't see much change in the future.

NASNoob11
Aspirant
Sep 07, 2013
vandermerwe wrote:
Please tell us you're going to try the possible solution in the link that StephenB has found for you.

Vandermerwe,
Sorry. I did not see a possible solution in either of the 2 links StephenB shared. But, it does seem that others have the same issue.
I still get to do a Factory Reset boot.
I still get to do a OS Reload boot.
I still get to upgrade the f/w to its' lastest beta.
I proceed forward aware that a bug/glitch still exists in the DUO-v2 area.
Appreciate the share.
vandermerwe
Master
Sep 07, 2013
The possible solution is there in the second link.
It is to get an address assigned by dhcp, then switch to fixed IP.
It seemed to work according to the thread.
NASNoob11
Aspirant
Sep 08, 2013
vandermerwe wrote:
Please tell us you're going to try the possible solution in the link that StephenB has found for you.

Vandermerwe and StephenB,
OK. OK. I did it. I did it. I did it! Post more research in my router's UM, I did enable DHCP. I did set a range of 10.0.0.2 - 10.0.0.30.
I did also populate the 'reserved address' table in the router with all of my current LAN clients whether they are ON or OFF. When done, I rebooted the router. Once complete, I opened RAIDar and then powered on the DUO-v2. The DUO-v2 popped into RAIDar presenting its' NEW IP addy of 10.0.0.2! Success. :D
The DUO-v2 logic does work. :slap:
OK, that test is complete. I have now decided to just leave 'sleeping dogs lay!' I did NOT even try to change/reset the NAS's new IP addy to something else! I'm done with this business for now. As this logic works it will make this NAS much easier for my Brother to install it on his home LAN. I do not think that he micro-manages his LAN as I do.

So, no RMA for the DUO-v2. I will wait for the replacement hard drive and expand the volume. Then, I'll package the NAS in its' box and UPS it off to my Brother. Project complete. BTW, I did upgrade the NAS to RAIDiator v5.3.9-T5 (beta).

I do so appreciate all the help both of you provided. I have new arrows in my NAS quiver!! If you have questions, please ask.

Forum Discussion

Duo-v2 upgrade HELP

16 Replies

Related Content

readynas duo v2 disk failed ..

Unable to upgrade ReadyNas Duo v2

ACTUALIZAR FIRMWARE READYNAS DUO V2

Netgear Ready Nas duo v2

ReadyNAS Duo v2

NETGEAR Academy

ProSupport for Business