Net retry endlessly after disconnect

[kmiles]

I saw this question raised earlier, but the post was hijacked without any solution.

 

When a client disconnects from the network in the midst of being backed up, Retrospect hangs with a "Net Retry" window up, trying to reconnect to the client endlessly. The "Net Retry" window stays up there indefinitely and Retrospect never polls another client, unless I manually stop the net retry and force it to resume.

 

Is there not some solution to this? Perhaps a setting in Retrospect that would say "After X attempts at Net Retry, move on to the next client".

 

Thank you for any help you can give as this is extremely frustrating.

 

Kyle

[rhwalker]

What version of Retrospect, what version of Retrospect client?

[kmiles]

Macintosh Server is 6.1.230

Macintosh Clients are 6.2.234

[twickland]

While we have occasionally seen this problem in the past, we haven't seen it recently. In our case, Retrospect kicks up the Net Retry for several minutes, and then logs a 519 "Network communication failed" error. This is what's supposed to happen.

 

Back when the Net Retry would go on for hours, we were able to solve the problem by uninstalling the client software (using the Installer), forgetting the client at the backup computer, reinstalling the client software, and then logging it back in.

 

We're running 6.1.230 on a G5 dual processor; our clients are various versions running on PPC and Intel Macs under Panther, Tiger, and Leopard, as well as on various Windows machines.