I've been using Reflect since v4. In fact, I still have a Win XP Pro machine that executes an image backup to my NAS every Sunday for years. So now I have a refurb PC running Win 7 SP1 64-bit. I installed Reflect v7.1 64-bit on this "new" PC so that I could backup this image to the same NAS. However, I am having problems with Reflect consistently recognizing the network directory to which I'm writing. Here are some facts:
1. Sometimes I can execute the script successfully when I open reflect and run the job. I can close reflect and watch the job run. Other times it crashes.
2. I have not yet been able to run job successfully when letting the scheduler execute the job. (Full run sunday at noon, incrementals at 10 every night).
3. I've set a NAS user with the name "UniFi Administrator". This matches the user name on my Win 7 PC. Passwords are same on PC and NAS.
4. NAS user has "admin" access rights.
5. NAS share is named "\UniFi (HP-6300)"
6. I've mapped this network drive successfully to my PC. Finds it without any difficulty.
7. When it fails, this is the message I get...
File Name: \\NETWORK-DISK\UniFi (HP-6300)\System Disk Images\F6030858BB53D491-00-00.mrimg
Attempting to connect to: '\\NETWORK-DISK\UniFi (HP-6300)\System Disk Images'
Failure: User - UniFi Administrator - Access is denied.
Failure: User - No user - Access is denied.
Failure: User - anonymous - Access is denied.
I've had a Network guy out doing some other work here, so I asked him to see if the NAS user and share are configured correctly, and he saw nothing wrong. And again. sometimes it DOES run if I submit job myself. If the PC connects consistently, why can't Reflect? Any ideas on how to address this problem?
Thanks a bunch