Limewire and Peerblock AP2P on Amazon EC2 cloud

[bucknutty]

I'm having a problem with Limewire and Peerblock. I read the other posts about the Amazon EC2 cloud, but I still need help. Every time I open Limewire, it won't connect to the network, and Peerblock keeps saying Detected AP2P on Amazon EC2 cloud. I tried letting it sit a few times, for about half hour to an hour, but it never connects. I tried uninstalling/reinstalling the latest versions of Limewire and Peerblock, but I get the same message. Strangely, if I install Frostwire (which supposedly runs on the same network as limewire), I don't get the messages. It was running fine for the longest time, even after I upgraded from Peerguadian to Peerblock. I don't have any problems running Firefox or IE 7. I've searched for this endlessly, and I even scoured through Bluetacks forums, but this doesn't seem to be a big issue anywhere else. Did the netstat -b and it only lists Limewire.exe and the java updater (the 192.168.1.10 is my host machine, the Limewire PC is a virtual). I'll dump the log of the blocked IP's, but I can't seem to find any reverse lookup info on them. The port 14840 is the port assigned when I reinstalled Limewire, but I'm not sure about the 1146 through 1152 ports. As I was typing this I allowed the IPs with 14840 for 15 Minutes, and Limewire connected, but I want to make sure I'm not screwing myself somehow!! Any ideas would be greatly appreciated. Thanks.

Peerblock Log:
2010-08-05 13:39:31;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;184.73.75.66:62666;UDP;Blo cked
2010-08-05 13:39:31;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;174.129.126.183:60666;UDP; Blocked
2010-08-05 13:39:32;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;75.101.200.74:51557;UDP;Bl ocked
2010-08-05 13:39:32;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;184.73.75.66:51180;UDP;Blo cked
2010-08-05 13:39:32;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;184.73.53.2:61666;UDP;Bloc ked
2010-08-05 13:40:03;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;184.73.53.2:20181;UDP;Bloc ked
2010-08-05 13:40:03;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;174.129.179.240:9999;UDP;B locked
2010-08-05 13:40:03;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;184.73.30.125:1337;UDP;Blo cked
2010-08-05 13:40:03;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;174.129.116.219:9999;UDP;B locked
2010-08-05 13:40:04;Detected AP2P on Amazon EC2 cloud;192.168.1.5:14840;174.129.126.183:9999;UDP;B locked
2010-08-05 13:40:14;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1146;174.129.126.183:8080;TCP;Bl ocked
2010-08-05 13:40:17;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1146;174.129.126.183:8080;TCP;Bl ocked
2010-08-05 13:40:19;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1147;174.129.116.219:8080;TCP;Bl ocked
2010-08-05 13:40:22;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1147;174.129.116.219:8080;TCP;Bl ocked
2010-08-05 13:40:24;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1148;184.73.53.2:8080;TCP;Blocke d
2010-08-05 13:40:27;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1148;184.73.53.2:8080;TCP;Blocke d
2010-08-05 13:40:29;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1149;75.101.200.74:8080;TCP;Bloc ked
2010-08-05 13:40:32;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1149;75.101.200.74:8080;TCP;Bloc ked
2010-08-05 13:40:34;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1150;174.129.179.240:8080;TCP;Bl ocked
2010-08-05 13:40:37;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1150;174.129.179.240:8080;TCP;Bl ocked
2010-08-05 13:40:39;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1151;184.73.30.125:8080;TCP;Bloc ked
2010-08-05 13:40:42;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1151;184.73.30.125:8080;TCP;Bloc ked
2010-08-05 13:40:44;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1152;184.73.75.66:8080;TCP;Block ed
2010-08-05 13:40:47;Detected AP2P on Amazon EC2 cloud;192.168.1.5:1152;184.73.75.66:8080;TCP;Block ed

Netstat:
Active Connections

Proto Local Address Foreign Address State PID
TCP virtualxp:1125 localhost:1126 ESTABLISHED 1204
[LimeWire.exe]

TCP virtualxp:1126 localhost:1125 ESTABLISHED 1204
[LimeWire.exe]

TCP virtualxp:1128 localhost:1129 ESTABLISHED 1204
[LimeWire.exe]

TCP virtualxp:1129 localhost:1128 ESTABLISHED 1204
[LimeWire.exe]

TCP virtualxp:1133 localhost:1134 ESTABLISHED 1204
[LimeWire.exe]

TCP virtualxp:1134 localhost:1133 ESTABLISHED 1204
[LimeWire.exe]

TCP virtualxp:1124 192.168.1.10:netbios-ssn ESTABLISHED 4
[System]

TCP virtualxp:1139 iad04s01-in-f102.1e100.net:http ESTABLISHED
1204
[LimeWire.exe]