JustUs Posted June 3, 2007 Report Share Posted June 3, 2007 About a week ago started having seeding problems. Upload a torrent, starts seeding at good speed, tapers off, stops, waits a a minute+, and starts the process all over again. Have updated NIC drivers, new modem from Comcast, no Windows XP updates during that time, no newly installed applications, no problems with other internet activity.When the client is first started, all the uploaded torrents go great until the first tracker update. The tracker says all is OK on their end (hmmm). Hard to judge if this process is really happening with downloading. But I would suspect to some extent - yes. This problem also occurs on my other systems.Running --ProtowallPestPatrolNOD32CA AntiSpamWinXP SP2IE7No router in this mix - direct from PC to modem. No difference if router is in the loop.Here are some error msgs from another client.{peer} Peer connection closed: connection exception: An existing connection was forcibly closed by the remote host; {nwman} Incoming connection [/201.83.184.167:4774] forcibly timed out due to socket read inactivity [68 bytes read: {nwman} incoming crypto handshake failure: end of stream on socket read: in=0{nwman} Connection [/41.212.134.58:2712] forcibly timed out after 60sec due to socket inactivity{nwman} incoming crypto handshake failure: Protocol decode aborted: timed out after 60sec: 0 bytes readPLEASE HELP! THANKS IN ADVANCE! Link to comment Share on other sites More sharing options...
duntkno Posted June 16, 2007 Report Share Posted June 16, 2007 its comcast homie, they seem to have implemented something this week. i;ve yet to find a solution, tho i could just find a diff isp Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.