Backup Connection Error

Done. This is the log:

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

session setup failed: SUCCESS - 0
Files copied: 0

Backup finished. Fri May 20 18:35:49 WEST 2011
---

I'd suggest opening up a ticket with support and see if they can reproduce the issue.

Anyone run into trouble with frontview backups just after updating Windows Security Essentials ?

After years of flawless backups, I'm suddenly getting connection errors and the only thing that I can think of is that I recently updated Security Essentials. That obviously isn't proof, but I'm wondering if anyone else has had this similar experience ??

I'm getting this same issue but it seems to have started just after I upgraded to RAIDiator 4.2.17 on my ReadyNAS Ultra 6.

I upgraded because my Tivo archive was not working (still isn't)... upgrade went fine but I started getting backup failures for my Windows 7 machine. WinXP from shares seems fine though ... any help would be great!

Could be something related to the 4.2.17, not sure.

I got mine going again, but with Security Essentials turned on this time, so I'm somewhat baffled at this point. I wouldn't say this is proof that it is not related to the recent Security Essentials update, but I'm starting to think it may be something else. XP feels more and more like it is defensive because it isn't as sophisticated as Win7- whereas Win7 is less defensive because it sort of has a better understanding / sophistication level to the LAN.

Just my $0.02

Figured it out, finally!

With two young daughters, who are getting more and more adventurous on the internet, I had my router setup to utilize the familyshield opendns domain name servers instead of my isp's default dnservers. Once I changed that back to the isp's dns'es, all my backup jobs immediately began working again.

That is really strange because I wouldn't think the nas has to go to a dns to get to an address on our LAN, does it? Obviously, the opendns / family shield organization doesn't know whether my lan addresses are any good, so they block them.

Any other comments are welcomed on this as I try to better understand this- but I have confirmed that the backup jobs were unable to connect to my pc (running xp) when I instructed my router to utilize these third party dns sites.

Can someone please help? Looks like I have a similar problem to others.

I have tried creating a backup job to backup data from a Windows 7 machine. I have used the following details;

Windows/NAS (Archive Bit)

Host: 192.168.1.22
Path: C/Users/Dave Edwards/Documents

When I click on 'Test Connection' I get;

Error connecting to //192.168.1.22/C/Users/Dave Edwards/Documents

I know the IP address is correct & I know that the folder in question is accessible as I can get to it from another machine!

Getting frustrated - but hopeful!!!!

Path should probably be: "C$/Users/Dave Edwards/Documents" - without the quotes of course

Example running under XP that works for me:

Thanks sphardy for that!

I have tried your suggestion but still does not work!

Any other ideas?

Regards

I don't have Win7 to compare and see if there are any specific issues related to Win7, but here are some suggestions off the top of my head of general steps to try:

- When using the "C$" share I believe you must use an admin account for login - not a standard user account - double check the account you are using is appropraite
- Make sure you do not have the Windows Firewall enabled - at least whle testing
- Try simplifying the settings further - ie create a specific share in Windows for the the data you want to backup and use the name of that as the path to avoid potential issues with spaces or other special characters in the path.
- If the specific share still doesn't work try disabling authentication as a test
- If the connection does work when authentication is disabled, does the username/password being used have any special characters or spaces that might be causing a conflict?