Sponsored Links

Connection Closed by Peer is it me or ISP

I was with Ezeedsl until Tiscali pulled the plug. I then moved to Firenet ISP,( I believe is part of 186k), honoring my contract with ezeedsl.

I now seem to get “Connection Closed by Peer”:mad:.
When running a Bittorent with uTorrent, after the first up date of the tracker I then get “Connection Closed by Peer”, never had this before, it was running OK before I joined Firenet.
I phone firenet and complained. The operator was vary good and checked my line and said there was no restriction on the line and my account was unlimited , I then asked so you would not mind if I joined a forum like ISPreview for advice she said no go ahead.

I am not convinced I still think its Firenet, this is why.
The trackers close down on the up date of the tracker with “Connection Closed by Peer” then the down load runs at a trickle.
If I disconnect from the ISP wait a bit then reconnect the torrent will restart and pick up until the trackers close down with “Connection Closed by Peer”
even my private trackers start and work but that will stop, but not as quick, with “Connection Closed by Peer”

Could some one put me right please.

All trackers seem to close even with the DHT open.
 
Incase it helps we saw this when an access control list (ACL) was blocking various torrent sites.

I've also seen it due to MTU issues and some SFI firewalls cause it - seems it can have a lot of causes.

Hope that helps a bit :)

Mark
 
Sponsored Links
Thank you Mark & Mark

Looks like I have the same problem, I did read that thread, and the ISP (mark) put the problem right.

The link http://www.measurementlab.net looks promising, I have just installed windows 7. 7057*64, and it is having trouble with the Java plug-in on that web page.
I installed the latest update from Sun, still not working. I will try again when I have more time.

I got the torrent working by using this program uTorrent 1.7.7 with DHT patch:D, when it started to down load I stopped it and deleted all the trackers from the list, then re started it.
It come down quit fast, no trackers no “Connection Closed by Peer” .

I will let you know how I get on.
mike
 
I have been talking on the phone with a friend and is ISP is firenet and he been expreinceing the same problem as me.
I got him to look up the web page and see if he could run the program. He did and there was no restriction on the line up or down with the torrent.

I asked him if he could retry http://www.measurementlab.net again when he experience problems like “Connection Closed by Peer”.

mike
 
Just a update, Not down loaded any thing big yet, but what I have came down OK with no problems, using the way I have already outlined.

I have now started a large down load 3 gig and getting “Connection Closed by Peer” the trackers are thepiratebay and denis.stalker.:mad:

So I went on the Glasnost site and run the test.


"Is BitTorrent traffic on a well-known BitTorrent port (6881) throttled?
There was a problem with the BitTorrent upload (seeding). Our tool did not detect forged TCP RST packets,but nevertheless no data could be transfered.
There was a problem with the BitTorrent download. Our tool did not detect forged TCP RST packets, but nevertheless no data could be transfered.
*
Is BitTorrent traffic on a non-standard BitTorrent port (10009) throttled?
There was a problem with the BitTorrent upload (seeding). Our tool did not detect forged TCP RST packets, but nevertheless no data could be transfered.
There was a problem with the BitTorrent download. Our tool did not detect forged TCP RST packets, but nevertheless no data could be transfered.
*
Is TCP traffic on a well-known BitTorrent port (6881) throttled?
There's no indication that your ISP rate limits all uploads at port 6881. In our test, a TCP upload on a BitTorrent port achieved at least 1139 Kbps while a TCP upload on a non-BitTorrent port achieved at least 251 Kbps. "

Any Help please, is it my ISP?:confused:

mike
 
I had this issue with Vispa recently, I ended up accessing my torrents via a proxy and by changing the port used every few hours; luckily the problem has now cleared, but at it's worst my P2P connection would drop from 70KBps to 0.5KBps after an hour or 2.

At the beginning of March though, my connection speeds suddenly shot up and I was d/l ing at 445KBps and I used all my available bandwidth in 2 days!!!! (60 gig download file).
 
Sponsored Links
So I went on the Glasnost site and run the test.

"Is BitTorrent traffic on a well-known BitTorrent port (6881) throttled?
There was a problem with the BitTorrent upload (seeding).
There was a problem with the BitTorrent download.

Is BitTorrent traffic on a non-standard BitTorrent port (10009) throttled?
There was a problem with the BitTorrent upload (seeding).
There was a problem with the BitTorrent download.

I wish I could help, but the results you're getting from the Glasnost test are completely different from the results I got when I was experiencing problems. My test revealed no problems like those, above, at all.

Apparently, ISP's can use some sort of hardware to shape torrent traffic, which, I think, shows up on the Glasnost test. My ISP was blocking from some kind of list, based on recognizing client user-agents (or something!) which doesn't show up on Glasnost (now cured, thankfully).

Any Help please, is it my ISP?:confused:
mike

See my second post on the thread that Mark.J links to, above. As Captain C says, in the last post above, using a proxy helped the problem slightly, though as I said your situation could be different from mine. But it's worth a try.

The Firenet forum seems to be dead, but you could try starting a thread there, just in case Firenet customers check-in occasionally and see if anyone else is affected.
 
Last edited:
Thank you all for your comments.:)

I still think it the ISP, but before I start accusing them of stopping me using P2P, I like to be right.

If I pull the power out of my router wait a bit then plug it back, I get a new address, the torrent then starts (working), until it up dates the tracker and I get “Connection Closed by Peer” .

Thinks Pipeless I will post in Firenet forum.

I'm not sure how to work a proxy.

Is there a way to stop the tracker updating? Or increase the time it takes to up date.
:confused:
 
Top
Cheap BIG ISPs for 100Mbps+
Community Fibre UK ISP Logo
150Mbps
Gift: None
Virgin Media UK ISP Logo
Virgin Media £22.99
132Mbps
Gift: None
Vodafone UK ISP Logo
Vodafone £24.00 - 26.00
150Mbps
Gift: None
NOW UK ISP Logo
NOW £24.00
100Mbps
Gift: None
Plusnet UK ISP Logo
Plusnet £25.99
145Mbps
Gift: £50 Reward Card
Large Availability | View All
Cheapest ISPs for 100Mbps+
Gigaclear UK ISP Logo
Gigaclear £17.00
200Mbps
Gift: None
Community Fibre UK ISP Logo
150Mbps
Gift: None
Virgin Media UK ISP Logo
Virgin Media £22.99
132Mbps
Gift: None
Hey! Broadband UK ISP Logo
150Mbps
Gift: None
Youfibre UK ISP Logo
Youfibre £23.99
150Mbps
Gift: None
Large Availability | View All
Sponsored Links
The Top 15 Category Tags
  1. FTTP (6027)
  2. BT (3639)
  3. Politics (2721)
  4. Business (2440)
  5. Openreach (2405)
  6. Building Digital UK (2330)
  7. Mobile Broadband (2146)
  8. FTTC (2083)
  9. Statistics (1901)
  10. 4G (1816)
  11. Virgin Media (1764)
  12. Ofcom Regulation (1582)
  13. Fibre Optic (1467)
  14. Wireless Internet (1462)
  15. 5G (1407)
Sponsored

Copyright © 1999 to Present - ISPreview.co.uk - All Rights Reserved - Terms  ,  Privacy and Cookie Policy  ,  Links  ,  Website Rules