Duo-v2 upgrade HELP

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.

@vandermerwe,
@StephenB,
Fine. It is Saturday, and I am calmed down. My LAN uses the 10.0.0.0 series also. I use a sub-net mask at each client of 255.255.255.0.
My current DNS servers are 66.18.32.2 and 66.18.32.3. Can NOT insert these values either. :?
My gateway (router) is 10.0.0.12 / 255.255.255.0. The DHCP server is disabled at the router.
My other clients are:
PC 10.0.0.8 / 255.255.255.0
PC 10.0.0.6 / 255.255.255.0 (off)
PC 10.0.0.4 / 255.255.255.0
Server 10.0.0.1 / 255.255.255.0
Readynas Duo-v1 10.0.0.21 / 255.255.255.0
Readynas Ultra 2 10.0.0.19 / 255.255.255.0
Readynas Ultra 2+ 10.0.0.17 / 255.255.255.0
Brother 5370DW printer 10.0.0.15 / 255.255.255.0
The home LAN also has 2 Netgear GS116NA switches
The home LAN uses the 'hub-and-spoke' topology. PC-10.0.0.4 (2BR) connects to the router/gateway's switch port 04 (1BR).
PC's 10.0.0.6 and 10.0.0.8 are located in the dining room (DR). They connect to to the router/gateway via switch #2510 port 16 to the router/gateway's switch port 01 (1BR).
The server 10.0.0.1 and the Readynas's 10.0.0.17, 19, and 21 (1BR) connect to the router/gateway via switch #250D port 19 to the router/gateway's switch port 02 (1BR).

IP address 10.0.0.2 is not used.
IP address 10.0.0.3 is not used. (retired, dead printer)
IP address 10.0.0.5 is not used. (retired, dead PC)
IP address 10.0.0.11 is not used. (retired, dead router/gateway)
IP address 10.0.0.13 is not used. (retired printer) **
IP address 10.0.0.22 - 10.0.0.254 are not used.
IP address 10.0.0.13 is not used.

This AM, I did a direct ethernet connection between my DR PC 10.0.0.8 after I admin'd the PC's ip address to 192.168.168.8 / 255.255.255.0 to the Duo-v2. Yes, the Duo-v2 remains at 192.168.168.168 / 255.255.255.0, and, remains locked to 'get IPv4 from DHCP. I find this disappointing. Actually, I feel this is a major bug in RAIDiator v5.3.8, but that is another thread perhaps.
Yes, I can use the drop down Dashboard menu to select 'use this IPv4 address. Yes, I can enter a new IP address of 10.0.0.13 / 255.255.255.0 ** and enter a gateway/router address of 10.0.012. And, then I can click APPLY. The Dashboard window sorta blinks and I do get the expected msg window about possible loss of connection. I select 'restart' for the DUO-v2 and close the Dashboard/browser window. I sit and wait for the DUO-v2 to completes its' restart. Then I relaunch RAIDar on the PC. The DUO-v2 pops up displaying an IP address of 192.168.168.168, NO CHANGE!

I can suppose that my DUO-v2 has a dead Ethernet section and that it is time to contact Netgear for an RMA. It is still under warranty (registered FEB 2012). I have never had this much trouble doing a static IP address assignment to a ReadyNAS. So, severly confused I remain. :x I remain willing to listen, learn, and correct any ReadyNAS bad behavior I may have picked up over the years. :)

Ok
I'm not sure why you think the Ethernet port is problematic.
Could you try activating your dhcp and seeing if the Nas gets an IP address.
On the off chance this is a browser issue, could you try the whole process using a different browser.
If this does not work, try an OS reinstall using the boot menu and try again with both static and dhcp assigned addresses.
If this doesn't work I think you'll need to log a support case.

Vandermerwe,
I do so understand that you are trying to help, but I am clueless to your focus for DHCP. I do not USE DHCP on my LAN. And, I fail to accept that the DUO-v2 refuses to allow me to statically assign its' ip address. It did 18months ago when I bought it. I read this as a major fault of the current RAIDiator f/w (v5.3.Eight). If I could, I would try to downgrade the RAIDiator f/w back to v5.3.3 (the last version I used to statically assign an ip address to this DUO-v2).

If you are adament on testing the DHCP server of my router and the ability of the router/nas to assign/change the Duo-v2's ip address, then I have to say, "Thank you. I am not interested. Good Day, mate!" I fail to see why you suggest that I do this, truly. Perhaps you like DHCP. I do not. No harm, no foul.

I am looking at the Netgear RN10200 and the Netgear RN31200 as replacements after I dust-bin or RMA this Duo-v2. :x

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.

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.