wilsson Posted April 4, 2002 Report Share Posted April 4, 2002 Retrospect desktop is unable to see the client on my network which is acting as my internet gateway. Moving the "ethernet port" to the top of the "Active Network Ports" list, as has been suggested, will allow it to work, but it changes my default route and prevents my machines from connecting to the internet. In the interim, I'm able to perform this switch to do the backups, but it's rather painful. Any suggestions? Link to comment Share on other sites More sharing options...
wilsson Posted April 8, 2002 Author Report Share Posted April 8, 2002 As of 4/8/02, this continues to be a problem. Link to comment Share on other sites More sharing options...
shadowspawn Posted April 8, 2002 Report Share Posted April 8, 2002 I think adding the client by address will work, since the problem is that the client acting as a gateway and broadcasting on the default interface does not reach the server. (However, this may require Workgroup or Server rather than Desktop.) Link to comment Share on other sites More sharing options...
wilsson Posted April 8, 2002 Author Report Share Posted April 8, 2002 John, I'm really not thrilled to pay a $100 premium (Workgroup upgrade differential) for a shortsighted design issue on Dantz' part. I've got two machines; this should be a no brainer for the Desktop solution. Before upgrading my machines to OS X, this configuration, using Retrospect 4.3, worked perfectly fine. I'm sure Dantz can find a reasonable solution to this problem. Thanks for the suggestion, though. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.