Readynas remote how does it work

In this output you will find Network Category, which needs to correspond to the category enabled through the firewall, as well as when Network Discovery is turned on. For machines with multiple interfaces, you will need to know the name of the interface which is connected to the network with the devices you wish to be discovered.

All is functioning now. Followed the advice here:. The answer above worked for me. The only change is where 'C' is listed in the command line it will need to reflect for actual volume name - that maybe 'C' or 'data', etc.

C is the name of your nas volume. Yes, you need to use an actual data volume name. It is ping-able and I can get to admin by typing it's IP. Taking steps from here and the Synology Link, it is now working. Launch it. Select tab for SMB Version. Choose SMB 1. Restart ReadyNAS. Run regedit. Command Prompt Admin Mode:. My Readynas now appears in explorer under networks. If you're using the preview releases of Windows 10, you might check to see if it works without dropping down to SMB1 now I'm currently on the "Fast Ring" for the Windows 10 previews, and after the last update Build , it started working as expected with no changes needed.

I would think this means that if you choose not to use the preview releases of Windows 10, it will work when the next "stable" build comes out. This could be related to this post. A windows update have fixed the SMB issues of several affected users. Thanks for sharing though. Hi I have two Netgear 4 disk RNs with firmware 6. I can get to them via ip and login. I ran the entire pathch recommended and intstalled the SMB app as well as ran the recommended changes to windows registry and command line etc.

It did not fix my problem. I now need to know how to undo the whol thing. Espescially need to know how to undo the command line portion: " sc. Destne ,. The link is:. We are actively working on resolving a similar issue with the Safari browser and recommend you use an alternate browser until this error has been resolved.

Subscribe for Updates. Join Now Log In Help. All forum topics Previous Topic Next Topic. Any Ideas on how to fix this? Message 1 of Labels: File Sharing. Me too. Accepted Solutions. Fire, theft, multiple disk failures, other hardware failure, floods, user negligence etc. Message 21 of All Replies. What firmware are you running? Are you using share security mode or user security mode? Are you using the microsoft login, or a local user login on the laptop? Message 2 of Other things you can try.

In Win10 I had to do the following: 1 There is a setting in windows Local Security Policy which is incorrectly set by default for viewing an older communication protocol NAS. Now double click and open "Local Security Policy". On in addition I had to run from an admin cmd window: sc. RNX - 6. Message 3 of Message 4 of Start with the RN, since share security mode isn't an issue there. If my net use commands work, then powellandy's changes aren't needed.

If they fail, then I'd try them. Then use the same steps. Message 5 of Sorry both. I feel like I'm getting closer. Message 7 of It's all blank. The instructions say I may need to log in as a user having access to the share. So how do I do that???!?!?!?!??!?! It just shows me a blank friggin window - no shares, no option to connect as a user I have defined on the server.

I have user level security set-up on the NAS. Message 8 of Charles, I saw the other thread you have created, I believe it is much better if you can keep it in one post only. I guess the admins doesn't want multiple threads on a single topic can you try opening port and forwarding it to the IP of the NAS? Message 9 of Nhellie - thanks so much for the reply. Sorry about the multiple threads. You're right they are better consolidated but my impression was once a thread was more than an day or so old and had at least one reply then it goes by the wayside That said I'll stick with this thread.

Could my NAS somehow be hacked thru ? Sorry I realize these are probably elementary questions. Thanks so much, - Charles. Message 10 of Ixa - Thanks for the FTP idea on this other thread - viewtopic.

Nhellie - It looks like it's now working!!!!!! It's a little odd tho Here's what I did Then I rebooted the NAS. After Reboot it still did not work.

Then I rebooted again. Once rebooted it's still working and I can see the shares. So even tho it didn't seem to work after the first reboot it did seem to work after the 2nd with FTP and 3rd reboots without FTP. Message 11 of Probably, opening the ports and enabling FTP triggered it to respond on the remote server. Glad to know it is working now.

Message 12 of So thanks to the help of others on this forum my immediate problem is solved - I have ReadyNAS Remote working from Windows 7 and 8 clients - thanks again. They can't actually get into the shares they don't have access to but i'd prefer they not even see that they exist unless they have access.

However, the problem is a side-effect. I can navigate to the hidden folders by typing in their name but I'd prefer to see them. If not I tried the KB articles instructions on both XP and Win 7 but just get "unknown network error" when trying to log in see my other thread referenced above for more detail.

Any thoughts on what I might be doing wrong? Message 13 of Anyone have any thoughts on my previous post? Message 14 of