I suppose that could be it. The problem is its consistently losing connection on only this machine, with these newer versions of cgminer. No other miners connected to the same pool have the issue, so its hard to see how its a pool specific issue. The pool is still up according to every other miner connected. Also when this error occurs, the failover never takes over either ( in cgminer.conf)....
Oh and to clarify, its not reconnecting which is the issue, both the miner and the pool show there are no more shares being submitted. It could very well be coinotron, its just strange its only happening on this one new miner. And not trying to failover at least when it does happen...
How often are you talking about? If it's still hashing away, then it HAS reconnected. That message doesn't mean it has lost the connection forever. However if no shares are being returned at that stage, that's because cgminer only reports the response from the pool, not when you actually send them, so my guess is there's some lossiness in your connection. Ironically new cgminer versions do it "the right way" and expose problems that older versions pretended never happened. I had one user who tracked a somewhat related issue to a bad network card/connection and upgrading the driver fixed it.Oh and to clarify, its not reconnecting which is the issue, both the miner and the pool show there are no more shares being submitted. It could very well be coinotron, its just strange its only happening on this one new miner. And not trying to failover at least when it does happen...
Network card might be a place to check, I'll see if I can find some updated drivers. I'm on the same network as my other miners so the outbound/inbound connectivity is good (35mbit/10mbit). But to answer your question, no it never reconnects and fails to continue hashing, and the pools show that as well.
