jwright Posted July 15, 2008 Report Share Posted July 15, 2008 I have a Mac OS X client running retrospect client 6.1.130. The machine is up and responds to a ping from the retrospect server, but the server is unable to connect to the client. When I try to access it via the "Clients" list, I get "Sorry, couldn't connect to clientname, error -530 (backup client not found). If we reinstall the client, the machine immediately becomes visible and I can back it up, but at some point, it disappears again. Any _specific_ suggestions? What are the names of the retrospect-related services we should be looking for on his system? Also, what exceptions should we be looking for in his firewall? Thanks, Jeff Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 15, 2008 Report Share Posted July 15, 2008 What is the Retrospect Client status displayed when you open the client software? If you have the firewall turned on, make sure you add the client. Quote Link to comment Share on other sites More sharing options...
jwright Posted July 15, 2008 Author Report Share Posted July 15, 2008 The client status says "Ready". Yet, I can't see it from the server. The client was added to the firewall. Jeff Quote Link to comment Share on other sites More sharing options...
jwright Posted July 18, 2008 Author Report Share Posted July 18, 2008 Any more suggestions? Is there a mac client config document somewhere? I couldn't find anything beyond the basic install steps. Thanks, Jeff Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 18, 2008 Report Share Posted July 18, 2008 Under clients, click test and enter the IP address of this client. What happens? Quote Link to comment Share on other sites More sharing options...
jwright Posted July 18, 2008 Author Report Share Posted July 18, 2008 I get the "Opening..." Client test window, which eventually fails out with a: "Can't access a client at "IP ADDRESS", error -530 (backup client not found). Here are all the details that I have relating to the problem. We installed the 6.1.130 client on his system. During the install we got a pop-up asking to allow the Retrospect client access through the firewall. We said yes. Next we got a pop-up asking to allow the pitmond service access through the firewall. We said yes. Then we got a 'restart required' box. We restarted. After the system came up, the client was visible through the firewall to the Retrospect server and it began backing up. The Mac OSX client had the "Allowing all incoming connections" exceptions set for the Retrospect client and the pitmond service in the firewall settings. By the next day, the Retrospect server could no longer see the client. By this, I mean if you tried to add it, test the connection or look at the properties of the client, you got a "530" error. The server that is running Retrospect has the firewall turned off and can ping the machine at all times. We checked the firewall settings on the client and they were unchanged. When we looked at the firewall log, there were a lot of messages like "DENY pitond connectioning from IPADDRESSofServer:1172". They were there every few minutes and the only difference was a slightly higher port number. The only ways to get the server to connect to the client is to reinstall the client as described above, or to turn off the firewall on the client. It appears at some point the server and client are trying to communicate on the wrong port. Just my initial guess. Ideas? Jeff Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 18, 2008 Report Share Posted July 18, 2008 Retrospect does connect to a random port above 1100 (I think that is the number) and pitond is a Retrospect process. When the "test" option fails with a 530 error it means that Retrospect can not see the computer at that IP address using port 497 (or the random port above 1100). It goes beyond seeing the client software itself, Retrospect can't talk to the computer. Quote Link to comment Share on other sites More sharing options...
jwright Posted July 18, 2008 Author Report Share Posted July 18, 2008 That has been my understanding so far. It is obviously related to the Mac OS X firewall. Any ideas what needs to be configured on the mac so that retrospect can see the computer? He has the latest Mac OS X version and patches. I would have thought that the client installer would have handled the firewall appropriately. The fact that the server and client communicate for some period of time initially after the install suggests that it does. Any idea why they would stop communicating and the mac would start ignoring the firewall exceptions? Quote Link to comment Share on other sites More sharing options...
MRIS Posted July 19, 2008 Report Share Posted July 19, 2008 Have you configured your Apple firewall as shown in this screenshot? Either choose: * Allow All Incoming Connections (thereby turning the firewall OFF) or * Set Access for Specific Services and Applications (then ensure the Retrospect Client is in the list, you will need to add it, set to allow incoming connections as shown) Quote Link to comment Share on other sites More sharing options...
jwright Posted July 20, 2008 Author Report Share Posted July 20, 2008 Yes, we have configured the firewall, exactly as shown in the image. We also have the piton exception too. Still same problem. Jeff Quote Link to comment Share on other sites More sharing options...
MRIS Posted July 20, 2008 Report Share Posted July 20, 2008 If the mac isn't directly exposed to the Internet, then you may be able to simply turn off the firewall as per the first option. Does it actually work reliably with the first option selected? * Allow All Incoming Connections Quote Link to comment Share on other sites More sharing options...
jwright Posted July 28, 2008 Author Report Share Posted July 28, 2008 The mac is exposed to the internet. Turning off the firewall is not an option. The client works perfectly with the firewall on the mac turned off. This is not an option though. Thanks, Jeff Quote Link to comment Share on other sites More sharing options...
dpages Posted September 16, 2008 Report Share Posted September 16, 2008 You can manually configure the ipfw firewall through the terminal to allow access to individual ports (it's a pain though), or there's a GUI front end called WaterRoof which makes it a lot easier. That gives you much the same degree of control you used to have under OS 10.4 Quote Link to comment Share on other sites More sharing options...
lauzon Posted November 17, 2008 Report Share Posted November 17, 2008 same probleme as jwright on X.5.5 : retrospect can acces to 4 mac but 4 others are unreachable, despite the same configuration. Turning off the firewall is not an option. Any progress from emc on this point ? May be a tutorial on WaterRoof can be another way to solve the problem, until X.6 is available ? Thanks in advance Quote Link to comment Share on other sites More sharing options...
Mayoff Posted November 17, 2008 Report Share Posted November 17, 2008 Have you confirmed that it is a firewall issue by turning off the firewall for 5 minutes? If it is a firewall issue you just need to aded Retroclient to your exclusion list Quote Link to comment Share on other sites More sharing options...
lauzon Posted November 18, 2008 Report Share Posted November 18, 2008 Turning off the firewall make retrospect recognize the mac. But turning on the firewall, make the mac unreachable, despite retrospect and retroclient in the exception list... Quote Link to comment Share on other sites More sharing options...
Mayoff Posted November 18, 2008 Report Share Posted November 18, 2008 Maybe this will help: http://forums.dantz.com/showpost.php?post/113750/ Quote Link to comment Share on other sites More sharing options...
lauzon Posted November 19, 2008 Report Share Posted November 19, 2008 yes ! that's it ! Thanks for the tip ! This "Command click" force Mac Os firewall to open REALLY the port ! i wonder if this tip has been in the FAQ or in the Product Documentation, it would have been usefull... Thanks a lot ! 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.