US Cable Support > RCN > Bit Torrent Uploads Being Disconnected

reply to phundercover

Re: Bit Torrent Uploads Being Disconnected

And my new mac is: 00159A3343FA

On the DaD forum there were 2 other RCN users from NYC with the problem and one from Boston.

reply to ALapo
Actually the limit is 10 connections per second. Many people seem to misunderstand this XP behavior.

Trust me, I get hundreds of active connections. It just takes longer to establish them due to SP2's limit of connection number RATE. Not total number.

I read there's a way to kill that rate limit in the reg. but why???? BT inherently has enough delays where the 10 connection per second creation rate minimally impacts it and even if it does, so you wait a few seconds for all the connections to establish.

Over the time of a torrent, it's trivial... JMO and observation.
--
Dave, Chicago - Edgewater/Uptown, @ the lakefront

dlconkey, thanks for your input on this one. However, I run SP1 and when I am *only* seeding I cannot connect to *any* torrents on *any* tracker.

EDIT: Downloaded a torrent today and watched what happened after I completed it - the number of leechers started to reduce. It appears that if a leecher was not connected to me at the point I finished downloading they could not connect to me later. (There were about 200 in total)

Right, phundercover. And just to further clarify: it is also impossible to seed a torrent (meaning to start a seed, rather than move from a download to a seed).

When I start a seed, the torrent immediately goes to "blue health" in Azureus and others can't connect to it. The tracker (Dime) sends an error reading "protocol error 1, no/erroneous BT client listening or misconfigured router." (At BootCity when I tried this my seed is listed as unconnectable.)

I have experienced this problem on two computers, with all new network equipment experiencing the same problem as the older equipment it replaced. The problem is consistent with numerous software packages. The only thing that we all have in common is the network: RCN.

John

I'm an RCN customer and have been having the same problem for the last few weeks. I can download just fine but once I start seeding, I can't connect to other peers

Hi thecolonial.

Thanks for adding your post. Would you also leave your cable modem's mac address in case someone here from rcn decides to check this problem out?

For anyone interested, I now have a thread on the Azureus support forum related to this problem. Link is here: »sourceforge.net/forum/forum.php?···d=349817. You'll need to register to participate, but not to read.

As of today, I'm now seeing the same issue. Anyone from RCN care to comment?
Since I have access to a machine elsewhere can anyone suggest a test that will prove beyond all reasonable doubt that RCN is the party that is blocking traffic?

EDIT - I switched the logging on in Azureus. I see quite a few of the following
[10:25:35] {0:0:0} Incoming TCP connection [xx.xx.xx.xx:xxxx] socket read exception: An existing connection was forcibly closed by the remote host

Does this mean RCN are doing something evil perhaps? I could forsee that they could make some technical decision to allow people to initially download over Bit Torrent, but then prevent them from acting as a seed for a completed file by sending a close packet back for any attempt to connect from a remote peer. This would reduce the upload stress on their network, but would also make it a bitch for us to get any ratio.

EDIT2:
Indeed if I stop Azureus (no clients are connected on multiple seeds) then reconnect using my neighbors Comcast connection - uploads start up at full tilt.
RCN - whats the story guys?

And JPJacob - my hat is in the oven with the rest of the dinner

I mean it doesn't quite fit with RCN's professed policy of 'we dont care as long as your not a virus/spam zombie', but then again it could be a sneaky way to reduce traffic without too many people noticing/ figuring out RCN is up to something.

reply to phundercover
How do you get your mac address?

This would suck big time if RCN pulled an Optimum Online

reply to jpjacob
As jpjacob has already phoned the help desk several times I sent them an e-mail yesterday describing the problem and referring them to this thread. Hopefuuly that will prevent a "it's your PC/software/modem/tracker you're accessing" response.

reply to thecolonial
Thecolonial, In your Start menu open a command window by clicking on Run, then entering cmd. At the prompt, type in ipconfig /all and press enter.

Your mac address is the 12 letter code after Physical Address (ie, Physical Address: 00-00-00-00-00-00) listed under the connection you're using. Post it here in case any of the RCN participants in this conference decide to help out. I assume that more addresses to test on may help solve the problem.

Noz, misery loves company! I hope we can figure this out together...

And a note to all: Anyone experiencing this problem who hasn't already called to RCN tech support should do so, please.

John

Hello,

I'm away from home for a few days so can't try this myself. But, would it be possible for one of you with this problem and also using Azureus to set Logging on in Options and then try to capture the problem in the console window?

If that works, please either copy & post it here or PM me for an email address. I'd like to submit the error log to Azureus support in the thread I've got going now for their analysis.

It's obvious that this is not an Azureus problem, since we've experienced it with other software as well, but Azureus' error handling may enable us to pinpoint the problem, which we can then forward to RCN support (if appropriate).

Thanks for the help.

John

reply to jpjacob
Your instructions for obtaining the mac addr of the modem are not correct.

The procedure you outlined will return the MAC of the network card in use, not that of the modem.

A quick simple way to find out the mac is to go to speedtest.rcn.net, select any region.

There will be some text at the bottom of the java window, including your modem mac.

Another way is to go to the diagnostic page of the modem. Typically 192.168.100.1 (»192.168.100.1/address.html for motorola modems) .
--
Insanity is living in a state of disillusion.

reply to jpjacob
I second that this is an issue with other torrent clients - I've tried ABC and uTorrent and have the same issue. Connect to another ISP, problem goes away.
It wouldn't surprise me if RCN pulled an Optimum - after all BT is a real pig on upload, and DOCSIS is pretty sparse on available bandwidth. It may be they've figured they have to do something for the network to survive an upgrade to 2Mbit.
And much as it saddens me to admit it, I can totally see why they would have to do this. Its a kinder approach than the optimum one, but it sucks for getting ratio up.

noz

reply to phundercover
Been trying all sorts of various methods to seed, and I see it is an RCN problem. I am listed as unconnectable on a large number of my torrents (though not all - leading me to believe some kind of filter is in place).

Also, when I download my client naturally connects to leechers/seeders, allowing my upload rate to be fine. When the torrent is completed however, the client expects others to connect toyou. If you are unconnectable, then of course your upload will be nonexistent.

I don't understand why RCN is denying it though. I called them and they said no, they haven't touched anything. Obviously they have.

reply to phundercover
According to ny.speedtest.rcn.net, my MAC address is:

00:08:0d:41:5a:89

reply to phundercover
my mac address:

00:08:0d:47:1c:89

pretty weird - when i did the download test, it went very very quickly. but when i switch to upload, it was pretty piss poor and even crapped out my wireless network. strange...

reply to nozzer
This may be unconnected with our current troubles but.....has anyone noticed that they now seem to be connecting to fewer peers when downloading? I was on a torrent with 200 peers and only connected to 40 (I use Azureus 2.2 and the setting for this is unlimited). I'm not firewalled so there is no reason why a lot more weren't connected.

Sorry about the incorrect mac address instructions. And there I was thinking I was so clever...

If anyone can run the Azureus logging test and post the results that would be great. I won't be able to get to it until after Xmas otherwise...

John