Hi Guido, 'incoming connection' means that your host has the ability to handle incoming TCP connections... it has nothing to do with a peer busy state or number of connections. So the Limewire statistics gives a true reflection of the small percentage of full operative peers.

There are three possibilities why a servant can not accept incoming connections: a) it's blocked by a firewall or packetfilter, b) it's running on a LAN with a NAT-router or masquerading (problem due to the nature of TCP, ask me if you need more details), c) your client does have a (sensless) switch not to allow incoming connections.

About a: you can add forwarding rules to your firewalll (one port must be assigned to each and every servant running inside the LAN), b: you can use an NAT-module or proxy (both is not available yet), c: just switch if off and then check for a+b.

I prepare together with Dun3 a document how to use Gnutella behind a firewall and whioch describes all technical details (TCP/IP, gnutella protocoll , firewalls, NAT, proxies)... sorry, it's not finished yet.

I will post more later, have to hurry and go shoping......