Big problem with connection

[jeronantropis]

hi

i'm at this huge university network here, and i used to use bitcomet to download, cuz it was the only torrent-clietn that worked on this network (don't know why).

now i try utorrent, and as all others: doesn't work. it's always trying to connect, but i get always errors for the trackers, like "invalid url" or "connection closed by peer".

as i said: the only torrent client that works here is bitcomet. does anybody know how i can fix this, or how utorrent-developers can fix this, so i can use it like bitcomet on this network? what does bitcomet have that utorrent doesn't (and it is NOT DHT).

maybe this can help: all peers i'm connected to in bitcomet, have "initiation"-status "local" (whatever that may be). i might have something to do with it ...

i'm getting desperate :?

thx

[Ultima]

Maybe it gets through because of the encrypted header thingy? That's the only thing I can think of that would allow it to get past what other clients can't... The devs are planning on adding encrypted header support to some future version, if they could first get their hands on the specifications for it...

[jeronantropis]

Maybe it gets through because of the encrypted header thingy? That's the only thing I can think of that would allow it to get past what other clients can't... The devs are planning on adding encrypted header support to some future version, if they could first get their hands on the specifications for it...

strange. even very old bitcomet versions work. but the thing is: the initiation status in bitcomet is "local" for all peers, meaning I am the one connection to THEM and not the other way around. this suggests i'm behind a firewall or router, but i know that. isn't there a way to work around this in utorrent (maybe i should post this in the feature-request-section)? if bitcomet can do it, why not in utorrent? o - i did try everything within utorrent options 8) .