NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Remote access error for Backup Job
I'm having a problem with backups on my ReadyNas Duo v1. I've just reinstalled my Windows 10 Home PC and I am now getting "Remote access error for Backup Job". I've been trying various ways to get t...
Hi there,
try as followed
Here The ReadyNas has the IP : 192.168.0.100
Method 1 Testing (Batch/PowerShell)
a) Create a user on the ReadyNas e.g. username: WinBack / password : winback1 / Group: users
Create a WinBackup.bat with the following:
"WINDOWSUSER" has to be your Windows 10 Username without ":
runas /user:"WINDOWSUSER" "WBADMIN START BACKUP -backupTarget:\\192.168.0.100\backup\ -include:c -allCritical -vssFull -user:WinBack -password:winback1 -quiet"
pause
b) Plan a Task for following Application
C:\Windows\System32\wbadmin.exe
Trigger "Log In"
Application Parameters:
start backup -backupTarget:\\192.168.0.100\backup\ -include:c: -allCritical -user:WinBack -Password:winback1 -vssFull -quiet
Cheap Workarround1: Test to add the user credentials from your PC to the readynas in the Same SMB Workgroup as Workgroup user and test INSTEAD of the "WinBack" user credentials
Cheap Workarround2: Test the READYNAS ROOT / ADMIN Credentials INSTEAD of the WinBack dredentials
Mistakes: Make sure your SHARES have the Users/Groups listed - Read everything again :)
Thanks for that.
I was looking for a solution to pull the backup from the NAS which is what I used to do, rather than push from the PC. As a temporary work around I am currently pushing (by scripting Beyond Compare as it happens) but the problem with that approach is trying to get email warnings if there is a problem, I can get a warning with a script and Windows scheduled task but it is a lot more hassle. So given that the NAS is supposed to be able handle the backup itself and it was until my boot disk died I am trying to get back to that situation, but thanks any way.
Try to use NetBios Protocoll instead of TCP/IP. I had user related problems with pulling things down via TCP/IP to Win7/10 - With NetBios Protocoll it worked. Via TCP/IP it was jsut not acceptiing my user credentials. When I tested the same credentials with linux it worked.
So basically call \\mynas instead of \\192.168.0.100 OR Workarround - let anonymous User get access to your share. Then TCP/IP worked fine as well.
Thanks for the response.
The problem is pulling data to the NAS from the PC not the other way around. I cannot see anything on the NAS that allows me to set the protocol. My PC can see and interact with the NAS box with no problem.
Setting anonymous access on the share is a good call, unfortunately did not help.
Did you try using the PC's IP address in the NAS backup job instead of it's hostname?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
