I am seeking guidance. I have read many a post concerning the issue of firewalls and a few on routers, but none seem to be directly applicable. Here is my setup:

Cable modem via Linksys BEFW11S4 router. Computer is P4 2.0A running XP connected via Ethernet 100 mbps to router. Running Zone Alarm Pro 3.0.118, their latest version.

I am operating via TCP/UDP port 1214. Failed to connect. Added HTTP (TCP) ports 80, 8080, and 8000 and connection succeeded. Why was that necessary? All other programs are programmed to prevent access of TCP/UDP port 1214.

The program attempts to access other TCP/UDP ports which I block. Zone Alarm is also blocking ICMP (type10;subtype2) inbound requests within my home network and UDP outbound to my cable provider. I'm not sure why or what in my configuration is causing it nor do I know if it is impacting my connection.

Can someone help me with the correct configuration that will allow me to get the most out of my connection without making my computer vulnerable? Thank you in advance.

It is my understanding that Gnutella clients communicate via port 6346... as to whether Clients are using UDP or TCP I do not know.

I've had the best luck opening up 6346 tcp and udp as well as 6347 tcp and udp ... hope this helps.

fasttrack clients need 1214 open on tcp and udp ... just to let you know.

You need to let your client access to every port at every IP, because you never know what port the other end is using.

Then, you should enable port forwarding in your router, and forward all TCP packets (UDP packets can be blocked) from port 6346 (or other, if you wish) to your PC port 6346 (the same port as in router). Without portforwarding you are unable to download from other firewalled users. Portforwarding will remove the Firewalled status from your client.

Not yet .

your client only drops his firewalled status if it actually knows it real IP and that you are forwarding data to it .
That's where the "Force-IP" fucntion is for .

And if your outside IP is dynamic your stuck with BS since that's the only client I know of that has automated the procedure of finding the outside IP .

I ahve been having problems like this and I just opened all my ports and hey were fixed Try that out