I did respond, if you look directly under the post that you made, then you will see what I wrote. I guess your looking for anyway to ruin my pool. What a loser.
Lol you just edited your post
![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
Still have a copy in another browser window.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fcommunityhosting.net%2Fih%2Fimages%2Fa1editehe.png&t=665&c=Bh9HAoNFVfUSWw)
As for "not sure why I can't connect" that's surprising, as you are dropping the packets at your box:
From one of my mining IPs:
Tracing route to a1bitcoinpool.com [24.14.210.199]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms deadcat.pixelrover.com [XXX.XXX.XXX.XXX]
2 9 ms 8 ms 5 ms XXX.XXX.XXX.XXX
3 16 ms 9 ms 12 ms CPE-65-28-18-110.kc.res.rr.com [65.28.18.110]
4 30 ms 26 ms 27 ms CPE-69-76-62-253.kc.res.rr.com [69.76.62.253]
5 42 ms 30 ms 28 ms ae-4-0.cr0.chi10.tbone.rr.com [66.109.6.100]
6 41 ms 53 ms 49 ms ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
7 40 ms 37 ms 38 ms te-1-14-0-0-pe01.350ecermak.il.ibone.comcast.net [75.149.230.201]
8 82 ms 70 ms 46 ms pos-2-1-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.86.37]
9 37 ms 50 ms 67 ms pos-0-12-0-0-ar01.area4.il.chicago.comcast.net [68.86.90.54]
10 33 ms 44 ms 30 ms te-3-3-ur04.romeoville.il.chicago.comcast.net [68.86.187.170]
11 53 ms 43 ms 49 ms 68.86.118.254
12 * * * Request timed out.
13 * ^C
From a different IP:
traceroute to a1bitcoinpool.com (24.14.210.199), 30 hops max, 60 byte packets
1 69.30.224.129 (69.30.224.129) 99.790 ms 99.774 ms 99.763 ms
2 69.30.209.125 (69.30.209.125) 99.789 ms 99.780 ms 99.770 ms
3 te0-3-0-4.mpd22.mci01.atlas.cogentco.com (38.104.86.1) 99.714 ms 99.706 ms 99.691 ms
4 te0-0-0-5.ccr22.dfw01.atlas.cogentco.com (154.54.5.157) 99.678 ms te0-4-0-5.ccr22.dfw01.atlas.cogentco.com (154.54.46.214) 99.670 ms te0-0-0-0.mpd21.mci01.atlas.cogentco.com (154.54.30.149) 99.629 ms
5 te0-4-0-2.ccr21.dfw01.atlas.cogentco.com (154.54.46.202) 99.630 ms te4-3.ccr02.dfw03.atlas.cogentco.com (154.54.6.54) 199.734 ms te0-1-0-1.ccr21.dfw01.atlas.cogentco.com (154.54.5.169) 99.585 ms
6 te2-1.mpd01.dfw03.atlas.cogentco.com (154.54.7.46) 199.648 ms 199.753 ms te2-8.mpd01.dfw03.atlas.cogentco.com (154.54.7.38) 199.744 ms
7 be-10-204-pe01.1950stemmons.tx.ibone.comcast.net (75.149.230.149) 99.803 ms be-10-304-pe01.1950stemmons.tx.ibone.comcast.net (173.167.56.165) 99.799 ms 99.784 ms
8 pos-2-4-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.87.217) 99.689 ms 99.701 ms 99.686 ms
9 pos-2-8-0-0-cr01.denver.co.ibone.comcast.net (68.86.85.217) 99.730 ms 99.715 ms 99.697 ms
10 pos-0-8-0-0-cr01.chicago.il.ibone.comcast.net (68.86.87.221) 99.721 ms 99.705 ms 99.700 ms
11 pos-0-12-0-0-ar01.elmhurst.il.chicago.comcast.net (68.86.94.106) 99.883 ms 99.875 ms 99.884 ms
12 te-3-1-ur03.romeoville.il.chicago.comcast.net (68.86.187.158) 99.878 ms 99.872 ms 99.862 ms
13 68.86.118.254 (68.86.118.254) 99.844 ms 99.890 ms 99.804 ms
14 c-24-14-210-199.hsd1.il.comcast.net (24.14.210.199) 99.822 ms 99.838 ms 99.821 ms
Funny how it stops at at your box... almost as if you blocked the IP. Dude, seriously... stop lying.
![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
That's two lies, now in one post. Once about you "answering me" and once about blocking my IP. Just man up and admit it. Not to mention lying about me "ddos'ing" you... wasn't aware connecting some of my miners was considered a ddos.
hey chill down man, i'm sure he will pay all the miners when the pool finds a block
How is he going to pay if I can't login and request a pay out?