Port 27016 and 7001 are used by Hostiles. Port 27016 by spammers, 7001 usually by upload slot containment but their shares suggests they are also spammers using temporary static shares (68 GB). Although I've never seen evidence of them (port 7001) as spammers per se. Those that use port 27016 and 7001 are BOTs all the same.

Yes , birdy did suggest photobucket and that did work out well for moving photos and images in .

Ok , for 2 weeks i have been observing my 3 hosts carefully and that number , 27016 , that you warned me about in message 354 has come up every day ; i only use the built in lw blocklist so is that only updated every 12 months ??

About 6 months ago , my emails that tell me that a new post has been added to the threads , just stopped coming ; why is it so ??

Can you send me their addresses if you still have a list of them?

No the LW 'built-in' Blocklist does not get auto-updated. That blocklist will not have been updated for 3 years or a little over 3 years. The LimeWire company produced the 'built-in' blocklist but the LW company no longer exists.

The blocklists I offer are based off the BearShare Full-Hostiles blocklist with continual updates. I also combined it with the blocklists from a couple of other gnutella programs and made sure the listings from the LW 'built-in' list were also included. So the so-called Security blocklists I supply are continually updated lists. Not only added spammers and hostiles that are designed to fill your upload slots, but also hostiles designed to DDoS your client, and also some criminal investigation groups. I update the LW list about once every two months (it's due for another update.) If more people were downloading it I would update it monthly. There's 4 choices. Two are 'light' lists which are a fraction of the size of the other two. This is in case your LW has memory problems. The other two are very large but a little smaller than the BearShare blocklist. You have a choice to block all Japanese hosts or not. The reason for this is not only to block Japanese hostile hosts but also for those who had contacted me in regards to keeping their search results and connections limited to their cultural interests.

Apologies. This is a bug that occasionally happens with the forum. Sometimes threads you might be subscribed to are updated with a new post but emails are not sent to those subscribed to the thread. The mail-server has a limit of emails it can send and this might be one of the problems. There's a lot of people who might be subscribed to this thread for example. I have no control over the mail-server, all I can do is nag the owner lol. Did you receive an email notifying you of this post reply?

No , i did not get an email ;

please edit my posts to protect the innocent .

27016 will be somewhere in my next post .

Fri Dec 07 15:56:01 WST 2012

LimeWire version 5.6.2
Java version 1.6.0_35 from Sun Microsystems Inc.
Windows Vista v. 6.0 on x86
Free/total memory: 15596432/66363392

Detail: Console Log

-- BEGIN LOG --
102727 DEBUG [Message-Executor] gnutella.HostCatcher.add - Pong from 76.24.217.225:27016
102728 DEBUG [Message-Executor] gnutella.HostCatcher.isValidHost - Validating host 76.24.217.225:27016
102729 DEBUG [Message-Executor] gnutella.HostCatcher.isValidHost - Host is valid
102729 DEBUG [Message-Executor] gnutella.HostCatcher.isValidHost - Validating host 76.24.217.225:27016
102730 DEBUG [Message-Executor] gnutella.HostCatcher.isValidHost - Host is valid
102730 DEBUG [Message-Executor] gnutella.HostCatcher.add - Adding host to free leaf slot set
102730 DEBUG [Message-Executor] gnutella.HostCatcher.addPermanent - Not permanently adding host with low uptime
-- END LOG --

Thanks, only one found though. You might want to check your gnutella.net connection file to see if any :27016 hosts exist. Remove them. You can open it with Wordpad and search that term. Oh, and also search :7001
FrostWire 4 is terrible for connecting to those spammer hosts. LimeWire 5 much less if at all but you still get spam from them.

LOTR, The space where LW allows you to add a host connection port (that frequently keeps popping back to 6346) What number or different numbers would be wise to enter in there for true music hosts? And European?
Thanks

These days probably the only client programs that keep that port as the default would be the older ones such as Cabos, Acqlite, BearShare, etc. Programs like GTK, LW, FW & Phex will tend to use UPnP where the port will vary each time the user opens their program, unless they port forwarded the program.

So in answer, I think you can even just keep it blank. And in some ways (at least in general) I'm not sure it even matters if you add a port the client is not using at the time.

I've manually added host addresses for programs like BearShare 5, Gnucleus, LuckyWire. And it did not seem to matter that the port was different or no port, a connection was still able to be made to the hosts manually added. Two of the best Phex hosts I'm aware of (obviously same household) use different static ports, yet when I've added the address, sometimes I've connected to one or the other regardless of the port I added.

I'm not sure what difference it makes when the hosts are port forwarded.

As far as seeking music hosts, I don't think the port number has any relevance.