forums.etree.org

I have gone thorugh all the steps to get my torrents recognized by etree. They show with leeches and sometimes seeders, but I can never connect, or rarely, to upload! I am on-line with uTorrent, the port is open - I checked - I have stopped all other U/L's and still, no connection.

I can connect to D/L when I release torrents from "pause" but for the life of me I cannot connect to etree to upload.

HELP!!!

_________________
Nov schmoz kapop

I think that the only way we'll find out is if you start seeding a torrent and leave the thing running for as long as it takes for one of the admins to notice and check it out. I'd start a seed, and then post here about it, and then DO NOT SHUT IT OFF!

Last time this was happening, you kept deleting your torrents before anyone had a chance to investigate.

Well, I have had this uTorrent open of the 6 torrents I have lilsted on your etree service (?) all afternoon and evening and not gotten one hit that I know of. I see others are connected to these torrents but not through me. OK, that does not tell us much. But I will leave this uTorrent runing all night and all tomorrow to see what happens. I get discouraged when I put the stuff together, list it and start the torrent here on my machine and nothing happens. Let's see how it goes this time around.

I think my real question is how can it be that I am on-line hooked up to u/l and there are downloaders waiting for these files and we do not connect???

Thanks and cheers.

PS - Have an egg cream for me.

_________________
Nov schmoz kapop

OK, I ran the U/L for a day and a half with no hits on the two most recent files (FMR set 2 (11th) and set 1 (18th)). Seems I have done about all I can do unless you can point out my errors. I am making and honest effort to do this and would appreciate whatever help you can provide.

I will restart the u/L's again and leave them on for at least a day to see if there is an u/l from the newest torrents.

Also, I get the following cheery error codes when I log on:



Warning: mysql_query(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /usr/local/wwwcache/etree/projects/bt.etree.org/html/include/bittorrent.php on line 74

Warning: mysql_query(): A link to the server could not be established in /usr/local/wwwcache/etree/projects/bt.etree.org/html/include/bittorrent.php on line 74

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /usr/local/wwwcache/etree/projects/bt.etree.org/html/include/bittorrent.php on line 75

Warning: mysql_query(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /usr/local/wwwcache/etree/projects/bt.etree.org/html/include/bittorrent.php on line 77

Warning: mysql_query(): A link to the server could not be established in /usr/local/wwwcache/etree/projects/bt.etree.org/html/include/bittorrent.php on line 77

_________________
Nov schmoz kapop

OK, sorry, I dropped the ball looking into this. Please let everything open, and I'll take a look tonight. Thanks.

The problem is probably a firewall of some sort on your end. I started a port scan of your PC about 20 minutes ago, and it's still going. That's almost always the sign of a firewall. Also, the bt.etree logs show you connecting to the site only once between the 17th and the 19th. Essentially, whenever you reach out to bt.etree to tell the tracker that you're there, the tracker isn't getting the message, and that's why no one can download from you -- you're invisible.

The usual firewall culprits are routers and software like ZoneAlarm or another program. What's your setup like? We can troubleshoot it from there.

We have a problem. I get this at my end:

Welcome to the µTorrent Port Checker.
A test will be performed on your computer to check if the specified port is opened.

Checking port 22349 on 66.190.nnn.149...

OK! Port 22349 is open and accepting connections.

You will be able to receive incoming BitTorrent connections.

I have run uTorrent with PeerGuardian up and down with no change in results. But, as I always do what I can for counsel, I will bring down PG and we will see if that changes anything. Also, I have tested the port/PG combo and can D/L other torrents just fine. Anyway, phaser shields down.

Cheers

_________________
Nov schmoz kapop

An honest question: Why do you even bother with Peer Guardian?

If you use it to block spyware / advertising, Firefox + Adblock + GreaseMonkey (optionally) will do all that for you.

If you're using it to prevent 'spying' by the gov or MPAA or RIAA, you're wasting your own time and CPU cycles.

It doesn't block your IP from being shown and the usage of block lists is laughable.

More criticism here:
http://en.wikipedia.org/wiki/Peer_Guardian

Maybe you have a good reason for using it, but it seems it relies on a false sense of security to me.

But, in fact, the port is closed:

Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2007-02-21 09:35 EST
Interesting ports on 66-190-xxx-149 :
PORT STATE SERVICE
22349/tcp filtered unknown

Filtered means that it's not open.

Here's what's probably happening. Most firewalls work by applying a set of rules in this order -- once a rule is met, the firewall is done and moves on to the next packet of data.

1) Everything from the inside is allowed unless specifically blocked
2) Anything that returns from the outside after being sent from the inside can come back in if the 'header' on the incoming packet matches the 'header' on the outgoing one.
3) Everything from the outside is blocked unless specifically allowed.

So, what's probably happening is:

A.1) You use utorrent to check port 22349. It sends a request to utorrent's website. B/c the request originated on your PC and isn't specifically blocked, it's allowed out (just like any time you visit a website). B/c the request originated on your PC, and is returning w/ the same 'header,' the return is allowed back. Utorrent sees this and says that your port is open.

or

A.2) Same as before, but when Utorrent sends a request to port 22349, your firewall program intercepts it. B/c of the way it's set up, utorrent's website interprets that as open and tells you so, but it's not utorrent that's responding, it's your firewall, and your firewall is letting the traffic die.

Now, back in etree:

B) Someone gets your IP addy and port from bt.etree, and tries to connect on port 22349. Rule 1 doesn't apply. Rule 2 doesn't apply. Rule 3 says "I don't know who you are" and drops the packet. You are, in fact, firewalled.

This is usually done by a piece of software, b/c a home router usually doesn't have enough settings to do something so complicated. Either the port is open, or it's closed. The exception is "gaming mode" or "virtual server" mode, which does something like case #2) above.

So, the question is, what hardware and software do you have running? There's no way to make a suggestion w/o knowing more.

Running software: uTorrent, Folding@home, AVG and Kerio 2.1.5

I can d/l from anyone else just fine. Maybe we should both have a egg cream. ;o)

No router, no "gaming" and no "virtual server." Just a standaloone PC runing through a Motorola cable modem. And, it works for other boards.

I was also able to D/L Government Mule with no problems. So, I can D/L from you and other boards no problem. It is just the U/L's to your board. When I put music on line for other boards, no problemo. I will try again now.

OK, I was able to D/L from you and elsewhere and upload to elsewhere. It boils down to I cannot U/L to etree.

Currently:

Welcome to the µTorrent Port Checker.
A test will be performed on your computer to check if the specified port is opened.

Checking port 25379 on 66.190.nnn.149...

OK! Port 25379 is open and accepting connections.

You will be able to receive incoming BitTorrent connections.


Boardmeister - OK, I backed out uTorrent 1.6.1.0 and went back to 1.6.0.0 and it seems to be working OK now. I have connected to various downloaders and have passed on the music. That is what it is all about. Currently having a uTorrent problem with it naming a torrent with two different names. Arrggghh! Pfui, too! I have no idea why 1.6.1.0 was a problem. Could just be another problem went away coincdentally. Who cares as I am satisfied to be sharing.

If you have any insight pass it on.

Cheers

_________________
Nov schmoz kapop