Hello, it seems that, since I updated to the new LimeWire Pro, some funny behaviours are taking place. I'm on mac OS X 10.4.6, and for some time my main PC being on repair, I'm using only my second one with only 400Mhz and ram 512 mo (but it also worked perfectly earlier). Anyway, it seems that Lime wire doesn't succeds very much or with any real stability to connect to the net...it takes much longer than before, stays oftens for ages on "starting connection", or poor connection, raising some time to "fair" or "excellent connection", but not always to "turbo-charged connection", an even then, returning from time to time to excellent or good...
I verified many times my config. in the built in mac fire wall, but everything seems to be OK, except that, once or twice, on the LW pref, I did find a different number in pref/advanced/firewall config/listening port (why and how, dunno!). I think the default one is 6346, and, once or twice I did find an other one... of course, since my FW was not configured for that other one, I tried to change it and open a hole for that new number, but it had no effect whatsoever and the connection was just the same, so, I came back to the previous config, allowing 6346, in FW, and indicating that number for listening port in the LW prefs.
Some times, I tried to shut LW and to then start it again, and, OCCASIONALLY, it then arrived fast at turbo-charged, but only occasionally.
I must also note that I'm using JAP, but NOT for LimeWire to go trough, and also that I've got ClamXav as AV (because some of my friends to whom I send things, using windows, and also some gnutella windows operating uploaders, I do not wish to have all of them knocked out), I did experiment with both JAP and ClamXav bein off. No change anyway.
I'm also using LittleSnitch, and it's configured to let LimeWire go to any Net connection, any port... And, even so, I did experiment putting that one off for few minutes (for that one, I didn't want to do much longer without it !), and without any change.
To day, looking at the console, I did notice that there seems to be a strange message going on and on, every 1,5 sec, days on end, and I'm wondering if it had anything to do with LimeWire. Here it is : <Looking for devices matching vendor ID=1193 and product ID=8718>... there are pages from that !
I'd very much appreciate any suggestion concerning this problem... thanks

re the vendor ID--it'sfrom a Canon scanner

see here

http://discussions.apple.com/thread....hreadID=121983

If the LW prefs are set to use UPnP, then your port could well change each time you start up, or if you tried using a different LW-based gnutella client (like Acquisition) at the same time.

Thanks, Stief, for the data, first, I know now at least that the message in the console has nothing to do with LW (true, I've got a canon Lide20). Second, I didn't know that LW was able to change now and then its port nr... it never did it before.
I've tried to come back to the previous version (4.10.9) but after a day where it seemed to work OK, it has started again to be only at good or excellent connection... so it was not the version !... I really wonder !...

Well, it's going from bad to worse... now my connection is "Poor connection", and there is no fire wall detected (the little green earth is clear of any wall).
I looked in "connections, and there are about six (peer) in and out going, plus about a dozen trying to stay on, but changing all the time (protocole 0,6)... now, since I started to write that post, the number of open connection has about doubled, and it says now : good connection... it took 20mn for that ( it is LW Pro, and should go much higher)... I really don't see now what I could change in any config to correct that... what more, it did work OK up to few weeks ago on the same settings... hope some one sees that and has some idea.

Ah--that sounds like your machine is in the throes of connecting as an Ultrapeer. The first few times that happens, things are slow.

You can always disable Ultrapeer mode in the Prefs.

Well, true, I let that ultrapeer choice on, since it seems to help some others, and I didn't know it could affect that much the performance from my client... in fact it didn't, up to recently... Reading your post, I did just go to LW prefs and checked the "remove ultrapeer ability" as trial... on the spot, my client passed from good connection (it was meandring from good to fair and vice versa) to turbo charged... I hope it'll stay like that...
Thanks anyway for the tip

Hi, stief, I just want to confirm, after I waited a bit to be sure of it, so, I checked the box "disable ultrapeer possibility", and since then, it stays at "turbo" all the time !
Only, the curious thing is that when, in monotor, I check the box for "show incoming research", it gives me the message : "Your client is a leaf node shielded by an Ultrapeer. Hence you will see few or no searches in the monitor window"
First, I don't quite understand what is meant by that, and second, for what "Ultrapeer" is concern, since I did remove that possibility, should it be still like that ?

Ultrapeers are used to create a better network. Right now you are running as a "leaf" which uses much less of your computer's resources. You are "shielded" from most of the network traffic, like searches.

When running as a leaf, you only have to connect to 3 or 5 (Pro) machines which run in Ultrapeers mode. You send your searches to those Ultrapeers, and they send it to the many more computers (~64) they are connected to.

The ultrapeers decide which search terms to send to your machine, based on your shared files. They only send the terms that may match your shares, which means your machine doesn't have to process all those other messages, which frees up your bandwidth from unnecessary traffic.

So, some machines act as ultrapeers if they are fast enough and can handle the traffic, which allows the leafs to run more efficiently.

Your machine looks to be *almost* capable of running as an Ultrapeer, but it wasn't working for you that well at first. So it looks like you are usually better running as a leaf.

Sometime when you don't have a lot of uploads and downloads happening, uncheck that "disable ultrapeer possibility" box and see what happens. It can be interesting, and if you don't share a lot of popular files, it's a very good way to contribute to the network by letting your machine do useful administration work.

Cheers.