Scary Protowall message

[nukehella]

I get this everytime I run a bittorrent client.Also I get a NAT error even though I have the correct port forwarded.I've run Adaware,Spybot ,,NOD32 and Trend Micro Housecall and came up empty.
Below is what I get.

Packet to "copyright-agency.com" ( 213.186.33.2 ) blocked. [protocol: TCP - src: 1100 / dst: 80]

EDIT:this message pops up when I run the NAT test in Azureus.Then I get a message(from Azureus) saying unable to test.2 days ago my speeds started to crawl and at first I thought it was just a bad torrent day.Then I tried to d/l something that should have been fast and threw all my upload B?W into it.When the speed still sucked I statred looking into it.
I even tried doing a system restore to when I was getting good speeds and I still get this evil looking message

[crackerjacker]

What it means its preventing upload packets to that ip address. *thats what protowall is suspose to do* so its protecting you. It will not allow you to upload parts of the bittorent file your downloading which is good.
You have that ip address range blocked. I dont know if your familiar with peer guardian, its the same concept. Its blocking alledge riaa enemies from downloading off of your bittorent client.
peace

[nukehella]

OK-This is just on the list because of the name according to what I Googled up and is not a threat.
Now why does it come up when I try to test the port and why have my speeds gone to shit since it started?

EDIT:-this happens with absolutely nothing up or down loading.It just happens when I test the port and I think it is clogging the port somehow whe I do download,thus causing my crappy speeds since it appeared.

[Rickio]

so your saying your not running anything and you get that?

If so you should get a process viewer and see what is running when that happens. prcview is good and freeware.

or explain a bit more if i misread you.

or is your bitorrent loaded but not actually up or downloading when this happens?
if that is the case. dump that client and get another. it might have something calling that ip address in it.

[nukehella]

This is getting strange.Now when I test the port I get this one
Packet to "Microsoft London Internet Data Center" ( 213.199.154.11 ) blocked. [protocol: TCP - src: 1738 / dst: 80]

Anyway I realize Protowall is doing it's job.I just don't see why it is happening with no torrents open-only when I do the NAT test

[crackerjacker]

do what rickio says get a process viewer to see what processes are being used.
i also would like to add if you already have a torrent file and were downloading and then are resuming then they are basically seeking to re establish the downloading of the file.

however if protowall is giving u these messages and are still having problems still i advise you to go visit protowalls website and show them a screenshot of the problem that way they can help you.

have you whois the ip address might wanna consider that as well. I am sure you mighta hmm

you might wanna reinstall protowall as well
cheers

[nukehella]

I'm thinking I'm making to much of this and I really have some kind of router problem.Last night when this started I was going on way to little sleep.I downloaded something and I got an invalid serial number message after the crap was already on this computer.Right after that was when I noticed all of this.
So I think I'm looking for somekind of software/spyware thing when I really have a hardware problem.
I'm going to take a chill break and wake up before I go any further.

[nukehella]

I dunno.I reset the router,reinstalled Azureus and Java and I still get the NAT error.Specifically
Testing port 6881...unable to test.
Ports are right,firewall is right,I guess I'm back at the software conspiracy thing.

[nukehella]

Well although the NAT error is still there I now have green health so I'm happy.I guess either Azureus or Java got corrupted.That NAT error is going to bug me though. Thanks CJ and Rickio.

[donkyboy]

I dunno.I reset the router,reinstalled Azureus and Java and I still get the NAT error.Specifically
Testing port 6881...unable to test.
Ports are right,firewall is right,I guess I'm back at the software conspiracy thing.

you can correct me if im wrong but the port "6881" has been banned due to there being known viruses on that port of the worm type if not misstaken.

easy fix chose another port probably a bit higher ive found that over 3000 is usualy a good choice of port dont goto far though as i think you can only go upto 65550 not to sure about that 1 though

plus dont forget to open these ports in your router and your firewall :)

also for extra security i run the safe peer plugin for asureus as well as protowall it still blocks some ips you can find this here http://azureus.sourceforge.net/plugin_list.php and dont forget to read the install notes as it can make azureus hang on startup if it starts insync mode

also make sure your not using any beta v of asureus i tried v2.3.0.7B24 and it sent my adsl router and network nuts nat problems and the like

[Dark Messenger]

nukehella did you ever get this sorted?

[donkyboy]

nukehella did you ever get this sorted?

even though you didnt ask me i fixed my prob here how incase any need it
I had to uninstall all network drivers then reinstall using different ip adresses
then i had to reflash the firmware on my adsl router (Thomson Alcatel Speedtouch 530)
thankgod I keep a working backup just incase.

and i reverted back to an older stable azureus v 2.3.0.6 as i belive it was the beta version that caused this other persons on the azureus forums had reported this to

now all is fine

[Dark Messenger]

thanks for bumping such an interesting thread donkeyboy.

[nukehella]

Yeah I got it sorted out a year and half ago.

Edit-since donkeyboy is new and must have dug this moldy old thread up by using the search function let's cut him a break.People who use search are trying.And I haven't used port 6881 in over a year and barely use Azureus anymore.

[Dark Messenger]

haha....didn't realise it was that old.

edit: So your solution was to quit using Azureus (nukehella)? hehe

[donkyboy]

haha....didn't realise it was that old.

edit: So your solution was to quit using Azureus (nukehella)? hehe

thanks guys i guess i should have checked the date how ever it did seem relevent
also i still see so many people out there trying to connect to me with port 6881 or 6898

[kokanezub]

thread too old delete it!!!!!!!!!!!!!!