merlin100 Posted April 30, 2003 Report Share Posted April 30, 2003 This backup was working perfect for over a month. I have a 10.2.4 Server with Retro 5.0.238 WG, and a 10.2.5 (Just updated from .4) client, (Retro 5.0.540) It appears that since the 10.2.5 update Retro will not connect to the client. Error -1028 I updated with the 3.5.104 5.0 update, made no difference. I can log into the client just fine from "Connect to Server" so it is not a network issue. (Both ways) Verified the IP address is accurate. I reinstalled the client. No change. Told Retro. to "Forget" the client and attempted to add it agin. Click on nework and it sees the client, but when I click on configure, I get the -1028 error after a couple seconds. Any suggestions? Link to comment Share on other sites More sharing options...
CallMeDave Posted April 30, 2003 Report Share Posted April 30, 2003 Quote: Any suggestions? Check the Firewall settings on either or both of the machines. Dave Link to comment Share on other sites More sharing options...
merlin100 Posted April 30, 2003 Author Report Share Posted April 30, 2003 Thanks Dave! I forgot that I turned on IP Firewall ;-( So, who knows which port needs to be opened for Retro to work? Link to comment Share on other sites More sharing options...
shadowspawn Posted April 30, 2003 Report Share Posted April 30, 2003 Quote: So, who knows which port needs to be opened for Retro to work? 497 Link to comment Share on other sites More sharing options...
dhwagner Posted April 30, 2003 Report Share Posted April 30, 2003 I have: ################################################# ## Retrospect ################################################# add 2009 allow tcp from any to any 497 in via en0 add 2009 allow tcp from any 497 to any out via en0 ################################################# ## Retrospect UDP ################################################# add 2010 allow udp from any to any 497 in via en0 add 2010 allow udp from any 497 to any out via en0 I believe you also need: ################################################# ## Non-Privileged Ports (TCP) ################################################# add 2042 allow tcp from any to any 1024-65535 in via en0 add 2042 allow tcp from any 1024-65535 to any out via en0 Put this at or near the end of your ipfw rules. If you use BrickHouse to configure ipfw (highly recommended) you will see that many (Windows-related) attacks are directed at non-privileged ports, and BrickHouse offers a number of rules to close those ports. For these rules to work, they need to be ahead of the "allow" rules for all non-privileged ports. David Wagner Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.