- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
RN 316 RAIDar not connecting
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
RN 316 RAIDar not connecting
I use the NAS mainly for timemachine backups. I haven't connected to the admin interface in a while and tried to run RAIDar to get the IP#. I get the message:
RAIDar could not find any NETGEAR storage on your network. Check that your storage device is powered on and connected correctly. For more help, visit http://my.netgear.com.
I downloaded latest RAIDar 6.5 and re-installed. Same error.
I did find the IP# with a net scan and I'm able to connect to the ReadyNAS admin console, which is running the latest firmware (6.10.10). I can also SSH to the NAS.
Why can't RAIDar connect?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN 316 RAIDar not connecting
@theusual wrote:
I did find the IP# with a net scan and I'm able to connect to the ReadyNAS admin console, which is running the latest firmware (6.10.10). I can also SSH to the NAS.
Why can't RAIDar connect?
Likely internet security software on the PC is blocking the discovery broadcast packets.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN 316 RAIDar not connecting
Neither a RAIDar nor a RN316 issue.
Very likely, you are using PC or MAC defaulting to more recent SMB protocols, and currently not active.
Tell us what computer (make, model, OS, version) you are using please.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN 316 RAIDar not connecting
@schumaku wrote:
Very likely, you are using PC or MAC defaulting to more recent SMB protocols, and currently not active.
The complaint is that RAIDar can't find it on the network.
The RN316 supports current SMB, so I don't think that is the issue here.