fregnergstrom Posted January 28, 2004 Report Share Posted January 28, 2004 Recently I upgraded all my Retrospect Client installs (OS9, OSX and Windows). Everything went fine, except on a 4D Server running Windows NT4. The machine let me upload the update through Retrospect's interface, but after doing so it altered the client name, and when I select the client from my Retrospect server machine to configure it, I get the message "Can't log in, -506 (duplicate activator code)". My server was running Retrospect Server 5.1.175 under OSX Panther at the time. Since then I've upgraded to Retrospect Server 6.0.178, but the upgrade didn't change this particular behavior. I tried using NT4's Add/Remove Programs to dump the Retrospect Client install from the machine, then I did a fresh install with the latest Windows installer. But the error message reappears when I try to log into the client from my backup server. Thanks for any help you can offer. Link to comment Share on other sites More sharing options...
natew Posted January 29, 2004 Report Share Posted January 29, 2004 Hi I run into this too from time to time. I think Retrospect is detecting the client running on both NICs and getting confused. You can try blocking port 497 on one interface with a fire wall. You can also bind the client to one interface by running the following command from a command line c:\program files\dantz\client\retroclient -ip xxx.xxx.xxx.xxx the x's are for your IP address of choice. Thanks Nate Link to comment Share on other sites More sharing options...
fregnergstrom Posted February 2, 2004 Author Report Share Posted February 2, 2004 The client machine has only one Ethernet interface. I did do a full restart of the machine after removing the original client install, for what that's worth. Link to comment Share on other sites More sharing options...
fregnergstrom Posted February 2, 2004 Author Report Share Posted February 2, 2004 Oops, spoke too soon. Though there IS only one IP interface, I did as you suggested and it worked. Thanks for your help! Link to comment Share on other sites More sharing options...
fregnergstrom Posted February 16, 2004 Author Report Share Posted February 16, 2004 OK, next question. Your solution works, but I have to reapply it every time I restart the client machine. Is there a way to lock the setting? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.