Friday, 17 September 2010

How to Direct Connect to your ReadyNAS

When encountering a problem with a ReadyNAS device, it is often useful during the process of diagnosing that problem to eliminate the network to which the ReadyNAS is connected to determine if the issue is truly with the ReadyNAS, or due to the network to which it is connected.

Any ReadyNAS device can be connected directly to a client via a standard ethernet cable - there is no requirement for a cross-over cable as the ReadyNAS ethernet ports are autosensing. Therefore, to make the direct connection work, it is simply a matter of ensuring the client is configured with an appropriate IP address and subnet mask.

For ReadyNAS devices with Static IP addresses

In the case where the ReadyNAS device has already been configured with a static IP address, a direct connection can be established by setting the client to have an IP address on the same subnet, and a subnet mask of For example:

If the ReadyNAS device has a static address of, configure the client to have an address - where xxx can be any integer between 1 and 250 (except, in this case, for 100 which is the IP address of the ReadyNAS) Google "changing IPv4 settings" for your client if you are unfamiliar with doing this.

Once done, directly connect the client to the ReadyNAS device with a standard cable and it should be immediately available to the client

For ReadyNAS devices with Dynamically Assigned IP addresses

If the ReadyNAS device is setup to obtain its IP address from a DHCP server, then additional steps are required to direct connect to it.
  1. Power off the ReadyNAS device
  2. Configure the client with any IP address on the subnet, (where xxx is any number between 1 and 250, except 168) - eg - and subnetmask Google "changing IPv4 settings" for your client. if you are unfamiliar with doing this.
  3. Connect the client to the ReadyNAS device with an ethernet cable
  4. Power on the ReadyNAS device
In the absence of a DHCP server, once booted the ReadyNAS device will default to the IP address at which point the connection should be established. While it should not be necessary to reboot the ReadyNAS to ensure it resets its IP address to the default once directly connected to a client, this is suggested as a precaution.

Accessing the ReadyNAS Device

Once the connection is configured and made, Frontview should be immediately available at https://<nas_ip_address>/admin - in the above examples at either or

If for any reason Frontview cannot be accessed, it is recommended to install & run RAIDar to verify that the ReadyNAS device has properly booted and is available, and also that the IP address is as expected.

If, after verifying the NAS has booted and the IP addresses being used are correct, it is still not possible to direct connect, first try a new ethernet cable. While it is rare for cables to simply 'break' there may be issues due to a slightly damaged connector or a broken wire within the cable.

If the connection still fails, then it would be advisable to contact Netgear Technical Support


  1. Hi,

    This is very informative and I wish that I had it when first configuring my NVX. I might just add that a router will act as a DHCP(Will assign a device on a network an IP) and if you are unlucky like me and purchased one of the many faulty Netgear DGN2000's your NAS will have to be configured through your computer. In this case your computer will not act as a DHCP and when running Raidar and clicking setup, you will get an error message saying the NAS and your computer are on different subnets.

    This means that you will have to change your computer from 'Obtain ip Automatically' to a defined ip in the form 192.168.168.X. X being any reasonable number in the range, 10 is safe. If you are not familiar with who this is done, google changing IPv4 settings.

    Hope this info helps anyone else having issues :)

  2. You're absolutely right - but see step 2 of the section "For ReadyNAS devices with Dynamically Assigned IP addresses" where it does state to configure the client with a static IP address, suggesting you use

    Maybe I can clarify that point more

    (Edit - have updated the post to try to make the text clearer)

  3. Configure the client with any IP address on the subnet, (where xxx is any number between 1 and 250, except 168) – eg – and subnetmask

    This cannot be done. Either the example should be or the subnet mask needs to be

  4. Please explain why it cannot be done and why the post is in error and I will gladly correct it.

  5. When I set my router's subnet mask to
    and then try to set my readynas to

    The router says "The IP is not within its DNS range".

    If I change the IP for my ready nas to then it is accepted.
    If I change the subnet mask to then is accepted.

  6. Why are you trying to set the IP address on the router?

    The whole purpose of this post is to describe how to directly connect the client to the NAS without a router ie via a single Ethernet cable, and so you have no need to make router settings changes, just a change to the IP settings of the client computer.

  7. Can I use a direct connect as a means of improving the reading speed between the client and the NAS? And, I have an RNPro -- can I use the other ethernet port to connect to the router so other clients can access it too? I've had tremendous trouble with stuttering HD Video, even with a Gigabit switch and port teaming with link aggregation...

  8. Alan - a direct connection should give you the best performance, though in my experience with the equipment I have used I have always been able to achieve the same speed over the network. The reality is my client machines are the bottleneck to network performance.

    Yes, you can use the 2nd port of the Pro as a direct connect while using the other to connect to your network. Just be advised that you should fix a static IP address on the direct-connect port and connect from the client via IP address rather than name to ensure the use of that connection is enforced. (Depending on the client, there are then various ways to assign a name to that chosen IP address)

    As for stuttering video - there could be many reasons. Try a direct connect first to rule out problems between client and/or NAS. If video then streams fine, this points to a networking issue. It's also worth disabling link aggregation in subsequent network tests as there can be incompatibilities between the NAS and network equipment that harm performance rather than improve it. There are numerous posts about this on the official forum

  9. Any reason to not use a direct connection for Rndu-6(4)000 all the time? I have no network access requirements for the storage.

  10. None at all if you really only need to access it from the one client - see previous comment - though it leaves me wondering why you chose to invest in a *Network* Attached Storage device