Strange problem: Search at first goes fine, then drops after a short while
 

Ive had a strange problem for quite a while.
When i start up Limewire, and start searchin, i get good results. But, as a few minutes go, if i try to search more or search again, i get zero results. Even if i try the most common and likely stuff, i get NO results.

No, all the tips on reinstalling etc doesnt work at all.

Which version of LW are you using?
Sometimes if you search same terms too many times, the ultrapeers you are connected to stop reacting.

Same thing happens to me now & again. I don't really bother too much about it. Though I might restart my LW occasionally & try again later.

However, it might also be the ultrapeers you are connected to. I'd suggest going to View menu Show/hide connections. Select the one you've been connected to longest, press Remove. Wait a few minutes for your connection to stabilise. Sometimes it takes longer than other times to get a new stable ultrapeer.

Ultrapeers come in all shapes & forms. Some cheat their way to become ultrapeers but do not behave well as ultrapeers. And then there's some 'dud' ultrapeers that do not respond at all to search messages. And then there's some spam ultrapeers. The last two being the worst.

(Yes I know LW support pages suggest reinstalling to fix many types of problems. I think for most people it's wasting their time. They even suggest removing LW in the incorrect way via using the add/remove control panel. The installer they have used for past 4 years is different & has its own uninstaller. And using the LW support pages' removal advice can cause problems not removing all registry bits.)

Im using 4.8.1 pro, tried upgrading to later versions with same effect. (Sticking to the oldie, coz i really dont like some of the **** in the new version ;)).
Also, got Java 1.6.0_11.

Example: If i first search for "naked women" at start, i get loads of results. If i, after 4 minutes, search of "naked girls", i get zero. If i try to "search again" on naked women-query, it goes to zero results.

Tried to reconnect and remove hosts, and still its same result.

PS: No firewalls enabled/active

hmm, the network is quite dynamic. Searches go through each of your ultrapeers, then through each of their multiple ultrapeers, etc. until the search runs out of steam. But some of those leafs & ultrapeers change from one minute to the next at times so different results can occur.

Are you using LW 4.8.1 or 4.18 ? Just checking if it was a typo. :) The reason I'm asking is because versions of LW after 4.17 will no longer give upload slots to versions older than LW 4.14. So if using 4.8.1 which was my favorite version until many versions later, you may be missing out on connecting to 'many' of the newer users. (I'm using both LW 4.16 & 5 so getting best of both worlds with 4.16.)

My advice would be to search something else for a while. Then go back to searching what you were originally after 30 to 60 or 120 mins later. That's what I often do.

You may be connecting to some poorly responding ultrapeers, not returning or passing on the search messages.

LW 5 is missing many tools from LW 4. It's not really a good version for experienced users. ;)

BTW please do not mention artist names or titles of copyright songs. We need to keep such things off the forums for legal reasons. :)

Ok, it was just an example. I didnt want to type that i was looking for pr0n :D

Its actually 4.8.1, good old one. Ive tried the later ones, but same thing happens there.

I often browse hosts, both via upload & download windows. Yes it is much harder browsing host via upload window, but keeping an eye out for it ... they are often sharing similar material or similar tastes, etc. I find a lot of rare material that way, by having them come to me. I share a wide range of material. So I keep an eye out on upload window as well. Just a thought. ;)

Ok, just tried the latest version, clean install after deleting old version (including registry clean). NO search results at all.
Straaaange.
Reinstalled old version again, and got the same problem as mentioned in this thread.

Might add that i think this bugger started pestering round june-july 2008.. Anyone remember if any Windows-update or javaupdate came out round that time, which might affect?