Search the Community
Showing results for tags 'network'.
Found 4 results
Running trial of v14 Installed new client on remote Mac (public key), defined proactive scripts, sources, media sets. When defining the client all is well; it recognizes the remote Mac and hard drives/folders. I can restore individual files from previous backups back to the client. Dedicated connection between 2 Macs, with manual IP address set on each. Everything works in set-up, but client shows "No network connection". If I force a regular (non-proactive) script to run, the client shows "Protected by Retrospect" while it is running, but as soon as that is complete, the client reverts to "No network connection". While this forced backup is running, status on server shows "Media not available"; as soon as forced backup is complete, goes back to "Status: (Not yet determined)". Is this normal behavior? So far none of my proactive scripts have started - they all show a status of "(Not yet determined)". On-demand features show Unavailable as well.
One of my scheduled Retrospect 7.7 tasks is to regularly duplicate the whole content of a folder with subfoleders into a shared folder on another computer in a network organized as a workgroup. This works fine as long as I am logged on and the computer is unlocked. However, if I log off or even lock the computer with me logged on, the duplciation stops (error -1017, insufficient permissions). I have the same logon names and passwords on both the computers, and I usually do not have any authentication problems in accessing shares on various computers in the workgroup. What can I do to make the duplication work smoothly even when I am not at my computer? What should I put into the field "Log on to" to make it possible to select the option "Always run Retrospect as a Specified User"? Windows 7 Pro is on both the computers. Thank you.
I'm having clients go missing to Retrospect 10.1.0(187) way too often and I'm wondering if it's happening to others as well. It's usually laptop users and they are all running Mac client 10.1.0.107. Force quitting the retroclient process immediately fixes the problem and Retrospect will see them on the network shortly after doing so. If I go to Sources and click the Locate icon and then on Test Address, entering the address gives me the correct name, client version and address of the client but Retrospect shows them as unavailable and won't back them up. There's nothing fancy about the network and as far as I can tell, their IP address assignments aren't changing from what they had the day before when Retrospect could see them on the network. Any idea how to make the client work more consistently or is it just buggy?