Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

put your upload on 5k or so for a while - and its torrent like any bit of software like it u can never expect full download speeds, but u can get lucky.

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

BT is full of leachers now, it's gone bad, I can still max out my connection every now and then but it's hit and miss.

My advice, spend a day learning how to use news groups, sign up with a provider and go that way, max speed all the time, it's worth the effort.

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

Yes but if you set your upload limit to a few bytes below the actual limit you get consistant speeds. I was under the impression that 'leecher' meant they didn't upload at all.

Of course somepeople refuse to do it because bittorrent reminds them of communism :rolleyes:

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

On all p2p apps i set my upload on netlimiter to 12~13kb.

On Azerus the health is yellow, yet i have done everything to make it not go onto yellow.

In the faq - 'If you only see L connections, chances are you have a Port Forwarding problem'

All my connections are L, yet the ports are forwarded and no firewalls or other stuff is on...i might just take that newsgroup route you mentioned... :/

Anyway i thought your download is proportional to your upload so even if you didnt bother uploading you wouldnt get much of a download either?

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

That is usually the case, but I think it depends how each client is configured.

Use this port scanner to check the ports you have opened/forwarded.
https://grc.com/x/ne.dll?bh0bkyd2

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

I did try this before and it did report 6881-99 were open.

Ive tried it again -


----------------------------------------------------------------------

GRC Port Authority Report created on UTC: 2004-06-02 at 13:20:10

Results from scan of ports: 6881-6900

0 Ports Open
20 Ports Closed
0 Ports Stealth
---------------------
20 Ports Tested

ALL PORTS tested were found to be: CLOSED.

TruStealth: FAILED - NOT all tested ports were STEALTH,
- NO unsolicited packets were received,
- NO Ping reply (ICMP Echo) was received.

----------------------------------------------------------------------

All ports closed? Is that normal? Those ports are forwarded and werent in use when I did the test...

Thanks

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

Repeat the test while the torrent is running, you should get some of them 'open'

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

Oh yeah, im using a different port in Azureus - 50160, i ran the test then and it said its open.

Ive also tried this but get 'Attempting connect to: 62.254.0.36 (cache8-nott.server.ntli.net) port 50160
Fail!
Unable to connect. This likely means you need to adjust your port forwarding configuration, or there is no client running on that port. '

Dodgy ntl cache maybe? Just a non-technical guess :) I have tried putting a proxy in Azerus but i dont remember a difference.

Health is still yellow on the torrent...i just cant get my head around this :(.

Ive had a look at the logs..alot of requests, some are eventually cancelled, nothing to myself looks too bad but then again...to me. I might try ABC as a few people on a long bt thread on port forwarding problems said it worked for them.

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

by the looks of this I am coming into this thread quite late and I dont have time to go over the last few pages as I am leaving for work in a minute.
By the looks of it you are trying to get your connection working in active mode rather than passive mode, correct??
I will tell you what got my connection working green in Shadows experimental with Zone Alarm Pro.

opened ports 80, 6000-6999 for both incoming and outgoing TCP/IP on the trusted and Internet Zones.
Manually specified BitTorrent to use ports 6000+
Specified my IP as bittorrent was detecting my proxy as my IP address and it was causing me to act as passive (yellow) rather than active (Green). When I did this BitTorrent said I would have to restart my client for the changes to take affect, this didnt work, it wasnt until I rebooted my computer that the changes took effect.

Now I download at some mighty fast speeds and my upload works properly at last :D

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

Ok i entered my ip in azurereus and now im in the green and receiving remote connections :)

but...now i am only uploading at half what i would without the ip (6-7kB/s) and my dl is, tbh, worse :(

Help!

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

It could just be the particular torrent you are on, have you tried it on any different torrents? (dont forget your speed can be affected by the speed and quality of the connection that other peers are on)

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

I guess, but i wouldnt of thought that many people on poor connections would be downloading a 4.5gb file..im just going to try another torrent now.

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

Hi

I am on NTL 1 MEG Cable Modem using azureus.

How do i open ports?

I only have 6881 and 6882 open according to the check above. I have no firewall and no router.

Also where do i enter my IP IN Azureus?

What are the ideal settings i should enter into Azureus - i average 60 download but i should be getting nearer or over 100 on a well seede torrent.

Thanks

Dave

Re: [merged] NTL & BitTorrent (ports 6881 to 6889)
 

I recommend you do use some kind of firewall or router for protection. But since you don't have one, then you don't need to worry about opening ports.

As for making it faster try limiting you upload to something like 23. Nothing else can be done, bittorrent isn't the most predictable of protocols.

You shouldn't enter your ip unless you have problems but it's in config under force ip address on tracker or something.

torrent downloads in belfast
 

any probs in the belfast area with torrent files. i have gone from a solid 125k a second to less than 10k a second. web browsing is unaffected and microshaft update come down at a good rate of knots.

cheers

big sinky