Cannot Save Image to Folder on other Network Computer
I am using AOMEI BackUpper Free.
I am trying to save a System Image of one machine in a folder that resides on another machine on my home network.
I have all permissions in order.
When I browse to the folder and click "Open", AOMEI tells me that the path does not exist or in unwritable.
I even made the folder a mapped network drive and AOMEI does not recognize it as such.
I am almost certain that I was able to do this a couple years ago, but it sure won't let me now.
Is AOMEI incapable of saving a system image on a different machine ?
What am I doing wrong?
Thanks for reading and all help is appreciated.
I am trying to save a System Image of one machine in a folder that resides on another machine on my home network.
I have all permissions in order.
When I browse to the folder and click "Open", AOMEI tells me that the path does not exist or in unwritable.
I even made the folder a mapped network drive and AOMEI does not recognize it as such.
I am almost certain that I was able to do this a couple years ago, but it sure won't let me now.
Is AOMEI incapable of saving a system image on a different machine ?
What am I doing wrong?
Thanks for reading and all help is appreciated.
Comments
I entered my IP address and all the folders showed up in the right pane; I chose the folder I wanted and clicked OKAY, just like the instructions said to do.
I still get the "path does not exist or is unwritable; please enter a writable path"
If the path does not exist, then why does AOMEI's browse dialogue show it ?
EDIT:>>> I have now tried this on three different machines.
I also tried various other drives/folders on the target machine and I always get the "does not exist/is not writable"
I am going to try Macrium Reflect and see if it can't at least cooperate.
Even though the exact same path was being navigated and displaying across the address bar in the AOMEI browse dialogue regardless of the many ways I tried to make it work, no matter what I tried, I always got the error.
I figured it would be another waste of time; however, I clicked Computer in the left margin, and navigated to my network folder via that route and it finally accepted.
Alas, this was all still a complete time waste, as now that AOMEI is finally recognizing and accepting my mapped network folder, no matter what I try, I keep getting the dreaded Error 4101.
This program had all of these same problems five years ago and nothing seems to be any better now than it was then.
Sometimes if the share is not set to give complete control over read and write,
you cannot access the shared folder properly to write a new file.
Peter
All share settings are 100% correct with complete control.
I can read, write, add, delete, change anything in any folder on any machine from any machine.
Now that I finally was able to convince AOMEI that my target path was indeed legitimate, I start the backup and it acts for a few minutes like it is working, and then I get Error 4101.
There should not be a problem; AOMEI writes the necessary folders in the target location, so I know that it has ability to continue, else it would not be allowed to create the folders.
In my own experience, I have found AOMEI to be a good program for saving images on a local drive; but, ask it to save anywhere else and it is 50/50 whether it will work.
Once you start getting the Error 4101, then you may as well give up and seek help elsewhere.
*I had a power outage where after power was restored, PC#2 was assigned a different IP address. This did bust the backup and is why I suggested to assign the backup destination a static IP address in your router.
I contacted support; and, after about a day, received a generic reply that a representative would contact me within 24 hours; I am still waiting for that to happen.
Do a search on this Error 4101 and you will find a ton of questions about the issue and not a single solution.
The only way I could get AOMEI to even accept a path was to map a network drive.
I appreciate the moral support.
I have used AOMEI often to do things within a single machine and to a directly USB-connected drive on a machine and it seldom gives a problem with that.
I have even sometimes been able to accomplish what I am having problems doing now.
Peter