I have most everything backed up, but doing the factory default will be a ton of work.
What would be the process for giving you access exactly? It doesn't really seem to be able to get an IP address, so not sure what my access options are.
Well to give support access you would have to put the NAS in tech support mode and there's a 5-digit ID (appears in Info - far right - column in RAIDar, and on NAS display) you can give them to help identify your system. Hopefully it will pickup an I.P. from your DHCP server when in that mode. If not, you might need an RMA.
For giving me access, it would be when the NAS is in that mode, but I would need your I.P. etc., port forwarded to port 23 on the NAS etc.
Support should be able to handle this (depending how busy they are the time taken before they can look at this may vary), but if I'm around I can take a look.
I think most likely you have an issue with your OS partition (it might be full), but the problem could be something else.
Well to give support access you would have to put the NAS in tech support mode and there's a 5-digit ID (appears in Info - far right - column in RAIDar, and on NAS display) you can give them to help identify your system. Hopefully it will pickup an I.P. from your DHCP server when in that mode. If not, you might need an RMA.
For giving me access, it would be when the NAS is in that mode, but I would need your I.P. etc., port forwarded to port 23 on the NAS etc.
The error message that you initially received means the unit cannot get an IP address by dhcp. There isn't anything intrinsically wrong with it. I have experienced this every time I have need to factory default or do an OS reinstall. The nas seems to start off using a subnet mask that is not 255.255.255.0 and therefore cannot get an IP address from most LAN dhcp servers. I think I remember that I needed to set my PC subnet mask at 255.0.0.0 then I was able to see the unit in raidar and connect to change the network settings. You may not need support.
DHCP uses broadcast packets, so the subnet mask shouldn't matter. The receiver is the router, and the only purpose of the subnet mask is to direct off-net traffic to the router. Also, DHCP is used to assign the subnet, so the protocol is defined so that it doesn't depend on a "starting subnet mask".
RAIDar also uses broadcast, so it should discover the NAS no matter what subnet you use (though there can be issues with wireless, because broadcast packets are sometimes dropped by the AP). Connecting to it via the web interface obviously does require a correct IP configuration in the NAS and the PC.
I'm not contradicting your experience, but perhaps the root cause isn't quite what you are thinking. You'd probably need a wireshark trace to really figure it out though, and it might not be worth the trouble.
I thought it might have something too do with subnets because the IP address that was displayed by the NAS after it gave the error about the discovery server was not in the range covered by 255.255.255.0. Raidar and readycloud both did not see the NAS. When I changed my PC network settings to a subnet of 255.0.0.0 then raidar could see the NAS, allowing me to access and change the network settings. I also tested the NAS with the correct subnet and it picks up an address by dhcp no problem, effectively the only difference is the subnet setting. Why do I need to set the subnet in dhcp if it's assigned by dhcp?
Yes that is the behaviour of my Ultra plus and nv+. The 316 comes up with the error message then sets an IP address that requires a subnet of 255.0.0.0. I can't remember exactly what it was, but definitely not 192.168.x.x When I get a chance I'll do another OS reinstall and see what happens.
I've investigated my dhcp problem a little. If dhcp is unavailable my 316 assigns itself 169.254.179.212 with a subnet of 255.255.0.0. Raidar does see it after about 1 minute. The dhcp server on my LAN is working and assigning addresses, but it appears not to my 316. I activated another dhcp server on my LAN and the 316 gets an IP address without difficulty. The first dhcp server is on an access point on the LAN, the second which works is the gateway. No filters blocking the readynas MAC address.
StephenB was right that the subnet difference does not prevent access.
I normally use a static IP for the 316 hence not ever tried to sort out dhcp access.
Agreed. I think my problem was some network error, it picked up the right IP when I moved to a different port on my switch. Probably time to reboot that thing.
Yes I only have one active, the one on the access point. There are only a few clients that need dhcp assigned addresses and they're all wireless, so this was not a problem until I got the 316. I assumed that a dhcp server is a dhcp server and would assign to any client. This one only seems to serve wireless clients. Now that I know this it's not really a problem, I may switch to the other dhcp server at some point.
