@xrpbtc:
orphans are normal, it's nothing you can prevent 100%
the orphan "streak" was a f---up on the backend of the pool, read the posts about it here
I am looking at my log and I received all the blocks solved by beeeeer from between 7-10 seconds after it reports them as being found on the website (which means that one or both of our clocks are off but also there shouldn't be a range of 7-10 seconds, shouldn't be greater than 1 second)
but for the one that was orphaned, 28296 2013-12-05 01:43:20, I received:
2013-12-05 01:39:22 received block 0000008c06a5cd9f9d1aa04fff50555e49215efe7a2df6c7fd152f6f7df44348 from xxx
2013-12-05 01:39:22 Committing 91 changed transactions to coin database...
2013-12-05 01:39:22 SetBestChain: new best=0000008c06a5cd9f9d1aa04fff50555e49215efe7a2df6c7fd152f6f7df44348 height=28296 log2_work=37.117473 tx=121129 date=2013-12-05 01:39:16 progress=0.999994
2013-12-05 01:39:22 ProcessBlock: ACCEPTED
about 4m earlier.
I guess the node reaction after block #28295 was received is relevant too:
2013-12-05 01:37:22 received block 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 from xxx
2013-12-05 01:37:22 Committing 16 changed transactions to coin database...
2013-12-05 01:37:22 SetBestChain: new best=000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 height=28295 log2_work=37.117204 tx=121100 date=2013-12-05 01:37:11 progress=0.999990
2013-12-05 01:37:22 ProcessBlock: ACCEPTED
2013-12-05 01:37:22 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500 from xxx
2013-12-05 01:37:22 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500 from xxx
all those nodes requesting 28294+, never received 28294 2013-12-05 01:35:47, until I sent it to them after block 28295
the same holds true for block 28303 (after beer got 28302 about 65 seconds earlier):
2013-12-05 01:52:57 received block 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 from xxx
2013-12-05 01:52:57 Committing 40 changed transactions to coin database...
2013-12-05 01:52:57 SetBestChain: new best=00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 height=28303 log2_work=37.119355 tx=121241 date=2013-12-05 01:52:51 progress=0.999994
2013-12-05 01:52:57 ProcessBlock: ACCEPTED
2013-12-05 01:52:57 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:57 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:57 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:57 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
so I think protoshare client connectivity is probably an issue here, for some of these
put 5.9.24.81 on addnode
