10. Shows port 6346 is completely blocked. 13. Shows you are having firewall problems.

Perhaps you didn't set port forwarding up correctly. The very first thing you should have done is set up a static ip. How to set up a Static ip for Mac OSX (click on link) If this was not the very first thing you did during the port forwarding process, then it was not done correctly & should be started from scratch, removing the previous port forward rule. For port forwarding your device, you should do both TCP & UCP. Even better to do them as separate port forward rules but not necessary. Then after setting up your port forward rules you save settings & depending on brand of device, may need to reboot that device to properly save & get the device into action with the new PF rules. Steps are (1) Static ip. (2) Set up port forward rules. (3) Save settings & reboot device if it requires it. (4) Set port forward settings for LW; Manual port forward instructions & sample image.

* Do not use the same port to connect thru as any other computer on the network. If the others are using port 6346 then choose another & make appropriate changes to your settings in LW, port forward rules, and as an extra OSX firewall rule.

My point was that, until it stopped working, I never changed anything pertaining to LimeWire anywhere. What you saw for my details were exactly as they were when the program WAS working (although, I can't verify that I always timed out going to the test link because I never tried it before). I always had a firewall icon, even when I could connect and download files (usually 20-60 KB/S, some near 100 KB/s). I have a static IP set, and my port forwarding is still set up as I first did it to use the program, and it worked then. I have only recently changed port numbers to see it that might help, but it hasn't. None of the other computer users are savvy enought to do anything much beyond answer emails and surf the web (and they don't know how to get into the router's settings to make changes). I have emailed my ISP to find out if they've begun blocking the Gnutella network, waiting on their response.

ISP reports they simply throttle the number of concurrent connections and bandwidth usage, not the ability to connect peer to peer applications.