I was wondering. Could this connection issue also be because most gnutella servents listen on the default gnutella port of 6346 and they simply blocked outgoing connections to that port and a few more ports after that such as the range of 6346 to 6352? I did a quick test to see if I could even connect to gnutella after blocking outgoing ports 6346 to 6352 connections with my home broadband router and after 15 to 20 minutes, no gnutella connections were able to be made with LimeWire 3.8.6. The second I removed that block of the outgoing ports 6346 through 6352, LimeWire was able to make connections to 5 gnutella ultrapeers. So it seems like a simple thing of randomizing the port it listens on when it is first installed for everyone could solve the outgoing connection problem for people who aren't able to connect out on those ports due to ISP/college blocking of that port range.