NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas NV+ ultimate setup frustration
I am installing a readynas NV+ RND4000 for a friend who purchased it over a year ago. Unfortunately his wife was ill and only got around to it now so I no longer have tech support and need all the help I can get. The new original RND4000-100 was defective and Netgear replaced it twice with an older refurbished RND4000, please see sig for setup details.
3rd times the charm and I was able to set it up with a direct connection to a Mac Mini with a fresh install of Lion 10.7.2. The network is pure Apple and the unit will serve as a shared disk for media that will be accessed by various Apple devices and iMacs. Because of this I disabled all protocols except for AFP and enabled Bonjour and Appletalk on the NV+.
Due to logistics the NV+ is attached directly to the Mac Mini which is itself connected to the Apple Extreme router via wireless. I would have preferred to install the NV+ directly on the router, but as previously mentioned, this is not possible. The router DNS range ends at 10.0.1.200.
Problems:
I connected the unit and Raidar easily found it. I setup the unit and everything seemed fine until i changed the IP to a manual value of 10.0.1.220 and subnet mask of 255.255.255.0. I changed the ethernet port IP on the Mac Mini to a manual IP of 10.0.1.225. The Mac Mini's wireless IP was set to DHCP with manual IP because I am accessing it remotely to support my friend. Raidar still finds the NV+ every time but I can't access Frontview anymore for love or for money. I cleared my Safari cache, tried Firefox, installed Raidar 4.3.1-T3 which also easily finds the unit, all to no avail.
Any ideas?
Questions:
I did not setup any exclusions on the router because I was outside the DHCP range. Should I have?
I want the unit to be accessible to everyone which is why I tried to put it on the same subnet. Is this correct? Is there another cleaner approach?
Thank you for any help you can provide.
3rd times the charm and I was able to set it up with a direct connection to a Mac Mini with a fresh install of Lion 10.7.2. The network is pure Apple and the unit will serve as a shared disk for media that will be accessed by various Apple devices and iMacs. Because of this I disabled all protocols except for AFP and enabled Bonjour and Appletalk on the NV+.
Due to logistics the NV+ is attached directly to the Mac Mini which is itself connected to the Apple Extreme router via wireless. I would have preferred to install the NV+ directly on the router, but as previously mentioned, this is not possible. The router DNS range ends at 10.0.1.200.
Problems:
I connected the unit and Raidar easily found it. I setup the unit and everything seemed fine until i changed the IP to a manual value of 10.0.1.220 and subnet mask of 255.255.255.0. I changed the ethernet port IP on the Mac Mini to a manual IP of 10.0.1.225. The Mac Mini's wireless IP was set to DHCP with manual IP because I am accessing it remotely to support my friend. Raidar still finds the NV+ every time but I can't access Frontview anymore for love or for money. I cleared my Safari cache, tried Firefox, installed Raidar 4.3.1-T3 which also easily finds the unit, all to no avail.
Any ideas?
Questions:
I did not setup any exclusions on the router because I was outside the DHCP range. Should I have?
I want the unit to be accessible to everyone which is why I tried to put it on the same subnet. Is this correct? Is there another cleaner approach?
Thank you for any help you can provide.
3 Replies
Replies have been turned off for this discussion
- You normally can't daisy chain network devices like that, that why it doesn't work.
You have 2 network interfaces on the mac on the same subnet, but only one is actually going out to the router, the other is plugged in to the nas.
Since the connection going out the router (the default gateway), it tries to out that connection, but that connection does not know about the nas.
Before you manually set the ips on the nas/mac, it was probably auto-configuring the ips to a different subnet (probably 169.254.x.x).
The correct solution is to connect the nas to the router, not the mac.
If there are no ports on the router, or too long to run another cable, then buy another cheap gbit switch, and daisy chain the switch off the router, then the mac and nas into the switch.
[edit]I guess your mac is only connected to wifi, so there is no cable connection to the router. Essentially, the router must be the center of the network, you can not daisy chain devices off the mac and expect those devices to also be usable by the rest of the network. I would suggest you move the nas next to the router and plug in there.[/edit]
If you disconnect the wifi, you should be able to get access back to frontview.
You can then change the nas and network connection to a different subnet (ie 10.2.x.x), then the mac can connect to frontview and wifi, but only the mac can access the nas (because the other network does not know about it). - I understand the switch and I actually set it up in anticipation of a cable being routed but that hat is off the table because the cable run would require tearing into walls that were just renovated.
If I fix my issue, and can get back in to to Frotview, can I bind the networks together using Vlan? If I do this do I get the same net result? Will everybody be able to access the NAS?
Thank you for the quick reply. - no vlan wont accomplish that
move the nas to the same location as the router, that is going to be the simpliest and easist solution.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
