blm14 Posted July 9, 2008 Report Share Posted July 9, 2008 So, I downloaded and installed retrospect 7.6 on both of my windows servers. So far so good. The 7.6 server install included .rcu files for the new mac and PC clients, which I promptly used. Now none of my clients can be seen from either of the retrospect servers. help! Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 9, 2008 Report Share Posted July 9, 2008 http://kb.dantz.com/article.asp?article=9688&p=2 Quote Link to comment Share on other sites More sharing options...
blm14 Posted July 9, 2008 Author Report Share Posted July 9, 2008 It broke all the PC clients as well... I tried to revert to 6.1.130 on the mac clients but they all failed. Am I going to have to go, physically, to every machine and reinstall the client? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 9, 2008 Report Share Posted July 9, 2008 To revert the Macintosh clients, you must install Retrospect 7.5 again temporarily and run the .RCU file for the old clients. You can fix the Windows clients by copying the publickey.dat file into the Retrospect Client Applications directory. Quote Link to comment Share on other sites More sharing options...
blm14 Posted July 9, 2008 Author Report Share Posted July 9, 2008 But that doesn't help me with the PC clients correct? Quote Link to comment Share on other sites More sharing options...
blm14 Posted July 10, 2008 Author Report Share Posted July 10, 2008 Ok so all the PC clients have to have the windows firewall exception re-added. So I still have to go to each machine and re-enable the exception which isn't quite as bad as reinstalling the client. Why would using the .rcu files cause the windows firewall exception for retrospect to go away? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 10, 2008 Report Share Posted July 10, 2008 Why would using the .rcu files cause the windows firewall exception for retrospect to go away? It is the Macintosh clients running 10.5 that will need to be re-added to the firewall. As long as your WIndows firewall has port 497 open for tcp/udp, you should be okay. Quote Link to comment Share on other sites More sharing options...
blm14 Posted July 10, 2008 Author Report Share Posted July 10, 2008 All of these windows-machines had the retrospect client installed before and they had been working, so port 497 was open before I used the .rcu file to update them. After using the RCU, every single one of them had the retroclient.exe exception in the windows firewall vanish. I am having work-study students painstakingly go to each machine to correct this, but I'm curious why this would happen. Maybe you guys should warn customers about it? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 10, 2008 Report Share Posted July 10, 2008 The upgrade process runs an uninstall of the old client, and an install of the new client. So this may be the reason. Quote Link to comment Share on other sites More sharing options...
blm14 Posted July 10, 2008 Author Report Share Posted July 10, 2008 But shouldnt the new install have restored the firewall exception? If using an RCU will always end up killing the firewall exception then what is the value of using them? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.