OSX Tiger Firewall Detected
 

I've did the whole "search" thing and I'm not a "newbie" to such forums. So here is my question:

I currently have 4.9.37 Limewire and 1.4.2_09 JAVA installed on my iBook. I've set it to manual port forwarding (Limewire), have added the port to my firewall (which is off), have set up my router (Linksys WRT54GP2) for the 6346 port. I've already had the port open on my router for Shareaza for my Microsoft based PC. Now everytime I open Limewire, it tells me there is a firewall detected. I am able to DL files fine and am showing a very strong connection to the network. Is this a glitch with the program or is there something that I'm missing here???

Hopefully someone can answer this question straight, without trying to redirect me with a link to another dead-end. I know I'm not the only one trying to figure out this detection thing, so any help would be great. Answer without a link if you know anything about this problem or glitch please.

Thanks in advance:D

You can only do manual port forwarding for a port for one computer. One port per computer. Besides, most Linksys use UPnP which means manual port forwarding shouldn't be necessary. But I don't think Shareaza has UPnP capabilities. Perhaps try a different port for LW to listen to. ie: LW Prefs>Advanced>Firewalls

Okay, Limewire is listening to port 8051 and I'm using UPnP. I'm still getting the firewall message? Do I have to set something up in the router UPnP settings?

Example:

Application----Ext.Port----TCP----UDP----Int.Port----IP Address----Enable
Lmwire--------8051-------this or this-----8051-------11-------------Check Marked

Do I check TCP or UDP???

Also, my firewall is off, but I kept the settings for 6346 port both TCP and UDP.

Re: OSX Tiger Firewall Detected
 

Haven't got time for essays.

WOW! that helps and not even a deadend link like your other posts to members hahaha. Isn't this a help forum?

Hey troll ... like your attitude. Now hope someone else is willing to help you. Your the one who set the tone in the beginning. If you knew how to use Mac OSX then you wouldn't be here would you. I've been using macs for 13 years. But I'm not an expert at anything nor do I pretend to be. I'm willing to help people who are a little more gratuious but your attitude makes me want to avoid you. I am now unsubscribing from this thread. I'm sure someone else will show up. As a volunteer, I don't have to put up with your attitude. I do this as a hobby. And why should I write a 100+ word answer to people who have posted questions that have already been answered on the forum. That's the reason for the links. Over 90% of questions on the forum have been asked before. :rolleyes: Comprehendo

Like water on a ducks tail, forum attitude rolls off my back. :rolleyes:

But um yes...this sounds like the same thing i'm seeing on my imac. Good connection, ports forwarded, mac firewall off, and still LimeWire detects a firewall. Curious.

Wish I knew what is going on too, but I am happy Limewire is working.

((sigh))
;)

yeah, sounds exactly the same as me....except LimeWire isn't working. No search results, nothing. Even when it says it has a good connection.

lol going out of my mind here...and I have NO IDEA how macs work really.... oh well...

:D

a firewall icon will always show at startup, until an incoming connection attempt is detected. Then the firewall icon will change.

So, once you are connected for a few minutes, check for incoming connections (you know where to find that info).

If no incoming connections are detected, something (like a firewall in the OS, router, ISP, etc.) is blocking incoming and the firewall indicator will remain bricked.

katracy--your problem sounds a little different. PM me and we can run a few tests.

As I've said, I can't complain about my LimeWire experience (ports are forwarded, etc, blah di blah..). I am just curious why I still see the bricked firewall icon even though I have the "turbo" connection.

I'd just like to know if LimeWire is detecting a bottleneck to it's operations, or if it is detecting a general condition of my router. If someone could help me figure that out, then the world would be right as rain.