ReadyNAS Remote iPad app v1.3.4

CIFS flat out isn't working. I set all my shares to disabled by default for all protocols, but the user I am accessing ReadyNAS Remote with is both enabled and is able to access all shares with write permission (via Windows), also via all protocols that are enabled. Won't connect at all with CIFS, will connect with FTP, but won't display any files / folders with AFP off. Works via Windows ReadyNAS Remote, just not iPhone. Am an iPhone noob, this is my first Apple device, so it may be me doing something wrong. But a friend of mine has a 3GS and managed to get his to work with his Duo with much less hassle than i'm getting. Having said that, he's not set up any restrictions on the shares, and doesn't advertise anything over http/s.

EDIT: Also, changing the protocol type from CIFS to FTP and then selecting "Done", will still fail with the right credentials. After changing to FTP (from CIFS) it was nessecary to use the "Cancel" option instead of "Done", then the device would connect as if you had pressed "Done".

gibxxi wrote:
CIFS flat out isn't working.

I haven't tried CIFS so can't confirm it's not working. FTP works again with 1.3.5.

Okay, I was finally able to connect using v1.3.5, but man it took some tinkering. I'm only connecting via FTP, not sure about CIFS, but I don't need it.

1. Ensure FTP is enabled on your shares. It's very easy to overlook. Disable Guest and setup a user/password for FTP. I just replicated my existing CIFS/AFP user info.
2. Make sure your user info is setup properly in the ReadyNAS Remote Add-On. there's no way to recover the user password (that I'm aware of). You may have to create a new ReadyNAS Remote user.
3. Once you can log into the ReadyNAS from the iPhone app, press ReadyNAS Remote (bottom right), then press EDIT at the top left corner.
4. Press the BLUE CIRCLE/ARROW.
5. Select FTP
6. Enter your FTP user info (same from step 1).
7. Turn Guest OFF.
8. Press DONE, and then press DONE once more.
9. Press the ReadyNAS displayed in the ReadyNAS Remote window.
10. You should see and be able to access any FTP shares you configured.

I hope this helps. It's very easy to overlook a simple step. I've been copying all kinds of files directly to the iPhone using FTP.

EDIT: And yes, most iOS-supported music files will play on the iPhone 4S :D

I am using v1.3.5 on IPad but unable to see any shares on my IPad. The shares are FTP enabled. I am able to login to my nas from iPad, but I don't see any shares in the remote app. Any tips?

Mike_bike wrote:
I am using v1.3.5 on IPad but unable to see any shares on my IPad. The shares are FTP enabled. I am able to login to my nas from iPad, but I don't see any shares in the remote app. Any tips?

Is the AFP service enabled on your NAS? I didn't need to set permissions for the shares via AFP to get them to be seen, but I did have to enable the AFP service in order for the shares to show up, even in FTP mode on the iPhone.

Looks like v1.3.6 was posted today with a few changes.

After the 1.3.4 issues i'm not moving off 1.3.5 until i have proof that 1.3.6 will not break Readnas Remote IOS client again.

Now using iPad version 1.3.6 with the new RAIDiator 4.1.9 and still no success: the consistent error is, "Response Invalid"

I confirmed that I'm running the latest Remote add-in. I stopped and restarted the Remote service. I rebooted the ReadyNAS NV+. My ReadyNAS shows up and the app shows "Connected as . . ." with the correct ID, but attempts to connect by WiFi on the same LAN or by 4G consistently fail. I'm set up for CIFS Guest access, which is how I connect using Macs and PCs on my LAN.

To state the obvious, disappointing.

Not sure if this will be of any help but here goes. I just recently configured ReadyNAS remote for a ReadyNAS NV+, and after days of not getting any client working, I now have the mac os and ios client working. To get my iOS client working, like the previous post, I had to disable anonymous FTP for my ftp share on the readynas (i.e. set it to User authentication) and turn off Guest on the iOS app, then it appeared. I kept getting "Invalid command" or something when I left it on CIFS.

1.3.6 was unable to recognize my account credentials...