Backup Connection Error

I have a folder named Users on the PC but is not shared.

It would need to be shared if the path you entered is to work. Otherwise, you can share the documents folder at the end of the path and use that as the backup source.

Ewok - I am sharing the entire c: drive with account/password protection - do I need to also share specific target folders?

Also, you noted early on about selecing the CIFS protocol - I have never had such an option. Possibly related, I have since re-enabled the NFS protocol that I disabled on initial setup as I have no Linux boxes - the error messages on the backups has not changed even with newly created jobs (still default to CIFS). Backup jobs using NFS from an attached NTFS USB drive to the NAS C: drive or another USB (NTFS or EXT3) works fine.

Is there a potential firewall situation here as I have no trouble accessing the NAS from the PC but the NAS can't initiate access to any PC's (Both PCs are Windows Vista with McAfee firewall). I can log into the C: drive from the other PC without problem.

Thoughts? Should I log an official support call or my direct phone #?

Thx,
Old Man

Old Man wrote:
Ewok - I am sharing the entire c: drive with account/password protection - do I need to also share specific target folders?

If the c drive is the only thing being shared by the source PC, then the path would have to look like this:

//chuckadmin-pc/c$/users/chuckadmin/documents

If you're only planning to access one folder on the PC over the network, then it's better to just share that folder rather than the entire c drive.

Old Man wrote:

Also, you noted early on about selecing the CIFS protocol - I have never had such an option. Possibly related, I have since re-enabled the NFS protocol that I disabled on initial setup as I have no Linux boxes - the error messages on the backups has not changed even with newly created jobs (still default to CIFS). Backup jobs using NFS from an attached NTFS USB drive to the NAS C: drive or another USB (NTFS or EXT3) works fine.

Windows/Timestamp and Windows/Archive Bit are different methods of using CIFS for the backup protocol.

Old Man wrote:
Thoughts? Should I log an official support call or my direct phone #?

Feel free to contact support for additional help. They may have some other ideas on things you can try to resolve the issue.

Thanks Ewok,

I've been experimenting and finally got something to work. After rebooting all PC's and the Readynas, I could backup connect to the PC IP address and share using the primary credentials. However, I could never backup connect to either PC network name or use an alternate account that had administrator priviledges. Also, all jobs log that they are running the CIFS protocol.

The key to resolution was understanding the required security. I googled the problem and found step by step backup job setup instructions on ehow.com. The final resolution key was setting up share access to the PC which is a topic that the ReadyNas user guide NEVER mentions in the backup instructions.

Thanks for the help as you were taking me to the solution - my configuration just wasn't as prepared as you might have assumed.

Old Man, PMP, CISSP, GSEC, GCIH

I'm getting the same connection error with Win 7 HP 64 bit, shared folders Music, Documents, Pictures. I've tried the IP and computer name as host and the folders as paths, as in PapaBears example above. Login is activated. I have also tried Users/Username/Folder as path, with either IP or pc-name as host. Ideas?

(it's a fresh RND2110 with latest firmware / raidar)

Hey, Newbie, if you see this, please post the exact line on ehow as I have a similar issue and would like to try out
what you did.

Thanks

Thanks for all your comments. They helped this Lurker figure out my similar issue. I right clicked on my extra drive (F:) and it was set to share by default, which confused me, because I could not get it to connect to backup. Then I saw the "New Share" option and gave it a new name (Storage) and set permissions to full control. Now I just type my computer name in at "Host" and at "Path" I type in "Storage" and I am connected sucessfully! BTW, after setting the new name of "Storage" it was replaced on the open window with F$, but available to view in a drop down.

I am trying to set this up to back up to my 1TB internal HD so I can then backup to my cloud service which does not offer NAS interaction.

Update: For the new folks (like me)... I have to remember that even though the "Test Connection" event in backup returns a succesful response, you must include an ID: ("Administrator" typically) and Password:(Whatever your computer login) for the backup to complete sucessfully.

Same problem. Everything was working fine, until I changed my main PC to Win 7 Ultimate x32.
- My User Share does not appear in >Network view;
- No other shares (/pub, /Music, etc) appear either;
- ReadyNAS appears as a "Media device"; selecting it starts Windows Media Player;
- ReadyNAS also appears as "Storage"; selecting it starts FrontView admin in web browser.

Meanwhile, all the NAS shares appear as they should on my Macbook Pro running OS X 10.6.7 and on my laptops running Win XP Pro and Win Vista HP....

The FrontView backup "Test Connection" option reports "Error connecting to //MYPC/mysharedfolder". All of the folders to be backed up are shared and can be accessed across the network. I have checked/double-checked my "Backup" user settings and password.

The backups have been failing, and the logs report the "Reason for failure:" as being "Unable to access remote path //MYPC/mysharedfolder".

HOWEVER... I have today discovered that I can access the shares by mapping drives - but this is a work-around and shouldn't be necessary (or should it?).

AND... Now that I have set up a mapped drive, the FrontView backups appear to have started to work (when manually started, at least)!

BUT... The FrontView backup "Test Connection" option STILL reports "Error connecting to //MYPC/mysharedfolder", both before and after a successful (manually-instigated) backup!

Why would this be?

I paste below the last two log entries for my "test" backup. The most recent was manually started, which is presumably why there is no "Backup started" timestamp?:
--------------------------------------------------------------------------------

Job: 008
Protocol: cifs
Source: //192.168.0.48/testbak
Destination: [julian]//testbak

Backup finished. Sat May 14 09:07:49 WEST 2011
--------------------------------------------------------------------------------
INCREMENTAL Backup started. Fri May 13 00:05:03 WEST 2011

Job: 008
Protocol: cifs
Source: //192.168.0.48/testbak
Destination: [julian]//testbak

Backup failed. Fri May 13 00:12:09 WEST 2011.

Reason for failure:
Unable to access remote path //192.168.0.48/testbak.
--------------------------------------------------------------------------------

Any feedback/info would be appreciated. It seems that I have sort of solved my problem, in that by setting up a mapped drive on my PC it seems to have "unlocked" the backups (although the "Test connection" STILL reports a failure) but it's work-rounds, and I don't feel comfortable with it as a robust and reliable solution.

Having made a considerable financial investment in the NVX, I'm disappointed that it is not working more robustly/reliably.

Thanks a lot
Jules

Try setting the protocol to archive bit, running the job, and seeing what error message you get in the logs.