Since the release of version 1.6.3 I have had a problem receiving from other's using the Gnucleus client (this problem does not occur when receiving from other clients and only occurs with versions 1.6.3 and up, including 1.7.4).

Here's what happens. Gnucleus will find a client that has the file I want. The server will start transfering. The transfer speed will read 0.00 kb/s until it times out and then gnucleus will continue searching. This is good, but the problem is that the server that gnucleus still thinks that it is receiving from the server that timed out. A stop/start of the transfer has no affect. The only way to clear the faulty server is to remove the file from the transfer window and then resume it.

Anybody have any suggestions?

Edited April 22, 2002
This also occurs when recieving from morpheus

A similar thing has been happening to me as well and might be related. Gnucleus will find a host which lists initially as busy, and then enters into the "waiting to retry" mode. After a long while, it is still retrying and when I check the extended info, it shows that it has timed out - but the transfer window still indicates that Gnucleus is retrying, instead of saying unable to connect.
I have had this occur with Bearshare, Gnucleus, Limewire and Morpheus hosts.