Topic: [1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration! - page 139. (Read 499597 times)

You won't earn more, if the pool has more power!

Greetz
NetworkerZ

I'll be happy when the Avg Luck: reaches +55.81%!!! Right?!!?

The pool needs more hashpower?! Like 800~900GHash?!

Best!
Thiago

wow look at those blocks fly! wee go EMC...
time for more!

You could always offset the PPS risk by proxying miner shares to hoppable pools. With the extra from hopping and a PPS fee, you'd own a Ferrari in no time. You wouldn't even be the first pool to do it.

[/tongueincheek]

That may be, but the earnings in the last 24 hours with pretty good luck (almost double typical 24 hour earnings) still haven't made up for the abysmal average on the last 50 blocks, especially in the last week, where your earnings were less than half of what you would have got with PPS.  It should all average out over time, so hopefully our luck streak keeps up long enough to average us lucky again (maybe we don't want that 30-70 GHash that left during the unlucky streak to come back).

I don't think we need to move to PPS.. Look at the nice run we had in few hours. I just made a lot more BTC than I would do with PPS.

Also,This.

WOW, look at our good luck recently, cept that invalid block...pooh
But dang.
NO to the PPS LOL!
Prop is awesome cuz its like getting a present each time, ya never know how long a round will last =P
Kinda is like gambling on luck a bit rofl, theres a bit of a rush in it. HAHA

I'm back! LOL
Gameover to btcserv.net... 
Lets change EclipseMC to PPS?!
Down there, where no lucky exists, it is too dark, and there is a lot of invalid blocks down there too! brbrbrrr....

Now we are seein some good luck...keep it up =)

Correct. Was only able to hit one and three.
Brought the rig home tonight to test another card.
We'll see how the connection does tomorrow when I take it back to work.
I'll complain again if I can't connect to any of them.
I still wonder what the H' was going on.

Thanks for your great support.

Let me know when/if it happens again and I'll try to do some more troubleshooting.  Are you not able to ping US2?

Up and running 
.....for now

Yeah, go with us3.  

.117 is pointed at the same server, so there's nothing blocking it on the server.  Very strange.

Can you post your routing table? On windows cmd type "route PRINT", perhaps there are some strange settings!

Greetz
NetworkerZ

can ping us1 & 3 at the moment!
Should I try mining?

Sorry to have kept you waiting.  Work getting in the way.

ping 208.110.68.117
PING 208.110.68.117 (208.110.68.117) 56(84) bytes of data.
64 bytes from 208.110.68.117: icmp_req=1 ttl=50 time=49.4 ms
64 bytes from 208.110.68.117: icmp_req=2 ttl=50 time=46.8 ms
64 bytes from 208.110.68.117: icmp_req=3 ttl=51 time=47.3 ms
64 bytes from 208.110.68.117: icmp_req=4 ttl=50 time=46.8 ms
^C
--- 208.110.68.117 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 46.828/47.626/49.482/1.112 ms
mickey@mickeyatwork ~ $ traceroute 208.110.68.117
traceroute to 208.110.68.117 (208.110.68.117), 30 hops max, 60 byte packets
 1  * * *
 2  ge-2-10-ur01.east.tn.knox.comcast.net (68.85.38.93)  15.943 ms  17.326 ms  18.464 ms
 3  te-8-3-ar01.sharpsridge.tn.knox.comcast.net (68.86.136.25)  34.809 ms  36.133 ms  37.484 ms
 4  xe-4-0-0-0-ar03.nashville.tn.nash.comcast.net (68.86.176.169)  21.486 ms  22.859 ms  24.021 ms
 5  pos-2-9-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.93.189)  44.151 ms pos-2-15-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.90.73)  46.882 ms pos-2-9-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.93.189)  45.355 ms
 6  pos-1-8-0-0-pe01.350ecermak.il.ibone.comcast.net (68.86.87.166)  41.582 ms  33.440 ms  30.843 ms
 7  te0-4-0-7.ccr22.ord03.atlas.cogentco.com (154.54.12.129)  32.195 ms  31.279 ms  36.759 ms
 8  te0-4-0-1.ccr22.ord01.atlas.cogentco.com (154.54.6.209)  37.013 ms te0-2-0-1.ccr21.ord01.atlas.cogentco.com (154.54.29.17)  31.850 ms te0-2-0-1.ccr22.ord01.atlas.cogentco.com (154.54.29.21)  29.096 ms
 9  te0-3-0-0.mpd22.ord01.atlas.cogentco.com (154.54.5.9)  33.823 ms te0-3-0-3.ccr21.mci01.atlas.cogentco.com (154.54.2.189)  56.252 ms te0-4-0-5.ccr22.mci01.atlas.cogentco.com (154.54.45.149)  52.350 ms
10  te0-2-0-0.mpd22.mci01.atlas.cogentco.com (154.54.30.158)  53.781 ms te0-4-0-0.mpd22.mci01.atlas.cogentco.com (154.54.30.178)  57.797 ms te0-1-0-0.mpd22.mci01.atlas.cogentco.com (154.54.30.154)  55.235 ms
11  everest.demarc.cogentco.com (38.104.86.2)  58.230 ms  55.518 ms  56.231 ms
12  69.30.209.1 (69.30.209.1)  56.154 ms  56.197 ms  55.895 ms
13  208.110.68.117 (208.110.68.117)  55.796 ms  55.662 ms  48.834 ms

Try ping and traceroute on .117 now.  I made a change as a test, it should fail like us1, us2 and us3

I'm just gonna go bang my head against a wall now. 

I'll keep looking into it and see if I can come up with something.  At least we know it's not the DC filtering it.

Hate for you to go to that much trouble for one tiny miner. ~400Mhs

It works
ping 208.110.68.117
PING 208.110.68.117 (208.110.68.117) 56(84) bytes of data.
64 bytes from 208.110.68.117: icmp_req=1 ttl=51 time=48.1 ms
64 bytes from 208.110.68.117: icmp_req=2 ttl=51 time=48.3 ms
64 bytes from 208.110.68.117: icmp_req=3 ttl=50 time=49.5 ms
64 bytes from 208.110.68.117: icmp_req=4 ttl=51 time=49.4 ms
64 bytes from 208.110.68.117: icmp_req=5 ttl=51 time=48.7 ms
64 bytes from 208.110.68.117: icmp_req=6 ttl=51 time=48.3 ms
^C
--- 208.110.68.117 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 48.100/48.754/49.532/0.606 ms
mickey@mickeyatwork ~ $ traceroute 208.110.68.117
traceroute to 208.110.68.117 (208.110.68.117), 30 hops max, 60 byte packets
 1  * * *
 2  ge-2-10-ur01.east.tn.knox.comcast.net (68.85.38.93)  14.810 ms  16.015 ms  18.638 ms
 3  te-8-3-ar01.sharpsridge.tn.knox.comcast.net (68.86.136.25)  17.312 ms  19.807 ms  20.971 ms
 4  xe-4-0-0-0-ar03.nashville.tn.nash.comcast.net (68.86.176.169)  22.471 ms  26.755 ms  28.186 ms
 5  pos-2-9-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.93.189)  40.047 ms pos-2-15-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.90.73)  44.008 ms pos-2-9-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.93.189)  41.214 ms
 6  pos-1-8-0-0-pe01.350ecermak.il.ibone.comcast.net (68.86.87.166)  42.660 ms  31.280 ms  31.445 ms
 7  te0-4-0-7.ccr22.ord03.atlas.cogentco.com (154.54.12.129)  31.343 ms  34.852 ms  32.448 ms
 8  te0-5-0-7.ccr22.ord01.atlas.cogentco.com (154.54.44.165)  33.746 ms te0-5-0-1.ccr22.ord01.atlas.cogentco.com (154.54.43.233)  36.027 ms te0-2-0-1.ccr22.ord01.atlas.cogentco.com (154.54.29.21)  37.741 ms
 9  te0-4-0-1.mpd22.ord01.atlas.cogentco.com (154.54.25.69)  37.547 ms te0-3-0-0.ccr22.mci01.atlas.cogentco.com (154.54.6.201)  49.726 ms te0-1-0-0.mpd22.ord01.atlas.cogentco.com (154.54.6.177)  28.819 ms
10  te0-1-0-0.mpd22.mci01.atlas.cogentco.com (154.54.30.154)  53.104 ms te0-2-0-0.mpd22.mci01.atlas.cogentco.com (154.54.30.158)  53.239 ms te0-1-0-0.mpd22.mci01.atlas.cogentco.com (154.54.30.154)  56.305 ms
11  everest.demarc.cogentco.com (38.104.86.2)  56.242 ms  56.454 ms  55.552 ms
12  69.30.209.1 (69.30.209.1)  56.910 ms  54.381 ms  55.731 ms
13  208.110.68.117 (208.110.68.117)  55.315 ms  54.478 ms  56.604 ms