Thanks for the detailed response Dave. I have two follow-p questions:
1. What is the easiest way to test any authentication changes I make? Currently when I run the profile, SyncBack seems to read the entire local drive for about 3 minutes and then tries to read the remote drive and only then it fails. Trying to avoid this 3 minutes delay.
2. My local machine is WIndows 7 and the remote machine is Windows 8. To make the dive mapping possible, I had to put both machines on the same homegroup. Even after allowing "Everyone" to have R/W access on the remote drive, the remote machine asks for credetials before it will map the drive. Although the local username/password are the same as the remore username/password, they are effectively different accounts (\\local\<myusername> and \\remote\<myusername). Is there a more "optimized" way to set up a remote drive?
Thanks again for your help.
1. What is the easiest way to test any authentication changes I make? Currently when I run the profile, SyncBack seems to read the entire local drive for about 3 minutes and then tries to read the remote drive and only then it fails. Trying to avoid this 3 minutes delay.
2. My local machine is WIndows 7 and the remote machine is Windows 8. To make the dive mapping possible, I had to put both machines on the same homegroup. Even after allowing "Everyone" to have R/W access on the remote drive, the remote machine asks for credetials before it will map the drive. Although the local username/password are the same as the remore username/password, they are effectively different accounts (\\local\<myusername> and \\remote\<myusername). Is there a more "optimized" way to set up a remote drive?
Thanks again for your help.