Bug or 'configuration error on my part'?

[Console Cowboy]

I'm running AltBinz 0.31.2 (backed off 0.31.3 until the minimize/close bug is fixed) on WinXP SP2+  and use Ngroups.net as my NSP.  Every now and then one of the 8 threads I'm running seems to go into a failure mode where it cannot connect.  The only way I can get that thread to re-connect is to 'pause' the whole thing, wait until all the other active threads are done, 'disconnect', 'unpause' and then 'connect'.  I didn't find anything of interest/help in the log file.  Does anyone have any suggestions on how to avoid/fix this problem?  I've tried disabling and then re-enabling the thread in question, it still doesn't actually connect (just keeps trying every 20 seconds).

Thanks.

[Ascathon]

Try not to use all threads, try six if you still reach the maximum speed of your connection. That was my way to solve it. Sometimes (and not only with AltBinz) a new thread is started before one of the eight has finished. Your provider doesn't like this ninth thread.
Also play around with timeout settings, for example 120 seconds.

[Console Cowboy]

Thanks, I will try tuning the timeout value.  FWIW: Ngroups.net allows 12 simultaneous threads and I found that disabling 2 of the 8 active threads did cut into DL speed, so now I'm trying 7 active threads; I also spent part of the day using Xnews to grab bunches NZBs and did have any thread failures with AltBinz at 8 and Xnews at whatever it uses (I assume one per transfer or group update).  I will continue to tinker.  Thanks again.