TerrificInToronto / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 0 forks source link

an attempt was made to access a socket in a way forbidden by its access permissions #329

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.it just crashes and the torrent client reply this error "an attempt was made 
to access a socket in a way forbidden by its access permissions"

What is the expected output? What do you see instead?
everything conected to the internet drops

What version of PeerBlock are you using? On what operating system? 32- or
64-bit?
1.00 32bit

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

i didn't made any screens

Original issue reported on code.google.com by mythn...@gmail.com on 26 Jun 2010 at 3:15

GoogleCodeExporter commented 8 years ago
Very strange - definitely never heard of this one before.  Does the problem 
happen 100% of the time?  Does it happen when you start PeerBlock, or when you 
run your Torrent client while PeerBlock is running?  Which torrent client?  
Have you tried other ones?  What about other network programs, do they crash?  
What version of Windows are you running?  What firewall/antivirus are you 
running?  When you say "it crashes" I assume you just mean the program itself, 
not all of Windows?

Other than that info, if you could attach the peerblock.log and peerblock.conf 
files from your C:\Program Files\PeerBlock directory - along with peerblock.dmp 
if it exists - that would be helpful.  Hopefully with this information in hand 
we'll be better equipped to figure out what's going on here.

Original comment by peerbloc...@gmail.com on 26 Jun 2010 at 3:40

GoogleCodeExporter commented 8 years ago
it happens very often and it happens after a period of time after is started
i run only utorrent (didn't tried other ones because it crashes the entire 
internet conection (chrome and IE)

i am running WS2008 with a nod32
the windows is still fully functional except the internet conection (with one 
exception, i connect to the server with RDP and rdp connection is just fine)

after i stop the peerblock the internet conection is just fine
but very strange the peerblock blocks every conection going out, but also 
nothing comes in and in the program is just showing my lan ip with diferent 
ports and says just blocked like this

192.168.1.1:2156 blocked
192.168.1.1:2157 blocked
192.168.1.1:2158 blocked
192.168.1.1:2159 blocked
192.168.1.1:2160 blocked...

no dmp file

Original comment by mythn...@gmail.com on 26 Jun 2010 at 3:54

Attachments:

GoogleCodeExporter commented 8 years ago
when the peerblock is working it usually saysa provider (or firm) - and its ip 
that it is blocked

soo the lan ip i was tallking about was the server's own ip (not the router)

Original comment by mythn...@gmail.com on 26 Jun 2010 at 3:57

GoogleCodeExporter commented 8 years ago
Hmm, well I don't see anything going on in the logfiles that sheds any light as 
to what might be going on here.  I do see that PeerBlock doesn't seem to be 
exiting cleanly, which would be the "crashes" you reported.  Generally we 
should be creating a peerblock.dmp file on the way down . . . is there no such 
file in the C:\Program Files\PeerBlock directory?

PeerBlock actually blocks connections when they're first instantiated, so if 
you have an open RDP connection when you start PeerBlock it *shouldn't* kill 
that connection on you, even if it would have blocked it otherwise.  Is it safe 
to assume you're just using some of the default list?  I didn't see any 
peerblock.conf file attached (just the .log), and that's one of the things I'd 
have looked for in there...

To be honest, I'm really hoping you'll find a peerblock.dmp file in that 
directory.  That should let us pinpoint the source of the PeerBlock crash 
you're experiencing.  Without that, though, I'm not too sure how far we'll be 
able to take this investigation...

Original comment by peerbloc...@gmail.com on 26 Jun 2010 at 4:42

GoogleCodeExporter commented 8 years ago
look what i found out
soo there is a file in the folder where te program is installed that has over 
545 MB
hystory.db

i entered in the history option of peerblock
and ifound this (atached jpg)

Original comment by mythn...@gmail.com on 26 Jun 2010 at 7:47

Attachments:

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
many other users are complaining

pls help

Original comment by mythn...@gmail.com on 29 Jun 2010 at 4:19

GoogleCodeExporter commented 8 years ago
Have you tried allowing that remote IP address that PeerBlock is continually 
blocking according to your history logs?

Original comment by peerbloc...@gmail.com on 29 Jun 2010 at 5:12

GoogleCodeExporter commented 8 years ago
yeap it did work

why that address has been blocked by your updates?

Original comment by mythn...@gmail.com on 29 Jun 2010 at 6:29

GoogleCodeExporter commented 8 years ago
What PeerBlock does is pretty simple on the face of it - it blocks access to IP 
addresses specified in any lists you tell it to use.  As per our "Why is 'Some 
Company or Site' Blocked?" FAQ (http://www.peerblock.com/docs/faq#why_blocked), 
we don't author these lists ourselves, we merely use those created by other 
people.  That FAQ link should help you track down who you'd need to contact to 
figure out why a given IP address is on a blocklist.

Marking this bug as "Invalid" in order to close it, as PeerBlock was correctly 
blocking this IP address since it was in one of your blocklists.

Original comment by peerbloc...@gmail.com on 29 Jun 2010 at 6:34