I'm leaning towards internet connection!
-It happens on multiple pools, at random times, even after a period of connectivity.
-others aren't having the same problem at said pools
These two things say it's not the pool, and the first one also says you have things set up properly to mine...when it's working!
Check your ping and run trace route to your pool! Try this!
If you have serious lag during certain (Peak?) times of the day, or many "hops" in your connection to the pool server, it could have a negative impact, causing latency in submitting shares, or even timing out due to slow connection.
ISP package isn't bad but it is compared to other countries. I've got a 2.0 MB/s download & 400 KB/s upload package.
Also the cable modem is a docsis 3.0 compliant and is enabled with my ISP if this matters at all.
But Slush and I spoke, something most highly is cutting out long living connection. modem/router/8 port hub, win7.
For the first 20-30 minutes it goes fine, then I get nailed with Long Pool: IO Errors & rejected.
Slush explained the reason for rejects, because of the LP error and then LP errors most highly is happening because long living connection is getting cut.
All explained here > https://bitcointalk.org/index.php?topic=1976.msg556444#msg556444
I am mining regular, LP disabled. It is running fantastic, I get like 4 stales out a few thousand shares. Wish I could say the same for LPing.
Tonight or tomorrow, I am gonna hard wire my pc directly to the modem, do some LPing, I'd like to pin point the problem.
Thanks for the traceroute link, I will use it.