NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jc2010
Jan 28, 2011Aspirant
Backup Connection Error
I'm trying to backup my PC (Windows Vista, 64-bit) using Frontview. The PC and ReadyNAS are both on my local home network, and I don't have a login/password on my computer. I've selected "Remote: Wi...
Blackadder
May 14, 2011Aspirant
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
- 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
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!