FrostWire suddenly firewalled but LimeWire is not
 

Suddenly FW is really firewalled. 4.9.37 has been running well (apart from the odd firewall icon appearing & disapearing) for ages. Now, 'recieved incoming this session' is false & has been for most of the day. 4.10.0 is the same. (Limewire 4.10.0 works fine, no firewall).

I've given FW plenty of time to settle down but it's just not happening! I've deleted the preferences folder & given it a good hour to work itself out.

My test for port 6346 worked. My connection's excellent & downoads are uneffected.

I have Win XP, sp2 (patched)
1 GB RAM, 93 GB free HDD space
Port forward thru a Netcomm NB1300 modem
XP firewall (configured)
ADSL connection from home
FW 4.10.0 Java 1.5.0_01

My comp's been in the shop for the past week but the guys who worked on it swear they didn't change any of my settings. I've been right thru the firewall, static IP & port forward...all settings are the same.

I've been trying to figure this out all afternoon & it's just driving me insane. Maybe I'm missing something really basic but I don't think so. Why is it only FW, not LW?? Please put me out of my misery

;)

Am I going to have to port forward for FW using a different port?

TIA!!

birdy

I found that Frostwire is sensitive to firewalls. I have experienced the same as you before with Frostwire and LimeWire when running in port forward Frostwire would detect a firewall while LimeWire did not.

But it did not affect my connection or UL and DL ability. The only way I have found to make it stop detecting the NAT firewall in my router is to run in UPnP mode. And make sure UPnP is enabled on your router and on Frostwire.

Grandpa,
Thanks for the reply. My modem doesn't use UPnP, I've just got the PF set up & enabled within FrostWire.

One of my concerns was that while 4.9.37 Beta did show me as firewalled now & then, my uploads seemed to be as normal. With 4.10.0, they're way down but downloads are as usual.

I don't really want to just jump in & PF thru a different port if it's not going to make any difference. Lazy:D

I have had some strange results with PF with both LW and FW and I can not explain them I only know what happened. I really have been reluctant to post them because people would just think I am a crazy old fart.

But what I have found when playing with different ports is that as I change ports the files that I am sharing (how do I explain this) lets say that I have 600 files that I am sharing an on one port lets say that only 10 of them are getting uploaded. Now when I change ports it will be maybe 5 seem to be getting UL and it is a different 5. Now I can go to another port and all 600 seem to be getting UL.

But the next time I run LW it will be back to maybe 5 or 10 that are getting UL. I have tried numerous times to try and figure out what is happening but have never been able to so to answer your question I drought it would do you much good to change ports. ( But on the other hand it might)

Thanks Grandpa,
I was hoping that this'd turn out to just be a glitch with the new version. The whole thing just locked up on me & wouldn't even show up in Task Manager. Within my monitor window, instead of the progress of the one person who's been able to push thru my firewall, it said "upload limit reached". Never seen that one before:eek:

I'm dubious about changing ports for FW because, knowing me, I'll confuse LW and then that'll stop working too. I'll keep playing around with it & maybe the gremlins will go & haunt someone else:D

Birdy are you using the same PF port as LW? If yes, I think you need to use a different port. ie: manually port forward different/separate ports for each specific p2p program. That's what I do.

Thankyou LOTR!
Yes, I'm using the same port for both. I wasn't sure if you could or not...should've asked eh:rolleyes:

I guessed it didn't matter as previous versions of both have shared a port no worries.

Sorry to sound clueless but does it matter which other port I choose ( ie is there a best choice for a second port)??

THANK YOU LOTR, Grandpa and Hobo,

LOTR: Yes, just PF through the different port has totally fixed it. (my query of what port to use qualifies for The World's Most Stupid Question)

Grandpa: Your advice is always good and you're not a crazy old fart!

Hobo: You were right, the port had changed:)

Cheers!

That's to be expcted. If you change ports, peers that would previously download from you can't connect anymore and FrostWire starts replying to searches again. Once you have a certain number of uploads again, FrostWire stops replying to searches and the files you are uploading remain the only files other peers know about.