TCP-Problem

[Hoerspielfuchs]

Hi there!
I have the following problem:
The smiley is green and download i ok. But there is aboslutly no upload.
The NAT-Test says TCP is not ok but UDP is.
I've tested the internetconnection with the VUZE-test and here is the result:

Test starting
Default public address is 87.149.220.204
0 NAT devices found
No SOCKS proxy found
No HTTP proxy found
No explicit bind address set
Testing HTTP outbound
    Test successful
Testing TCP outbound
    Test successful
Testing UDP outbound
    Test failed: Outbound test failed
Testing TCP port 55250 inbound
    Test failed: NAT test failed: Connection timed out (87.149.220.204:55250)
    Check your port forwarding for TCP 55250
Testing UDP port 55250 inbound
    Sending outbound packet and waiting for reply probe (timeout=5000)
    Sending completion event
    Test successful
1 public/external addresses found
    87.149.220.204
    AS details: as=3320,asn=DTAG Deutsche Telekom AG,DE, bgp_prefx=87.128.0.0/10[/87.128.0.0-/87.191.255.255]
Vuze Services test
    Vuze Website - http://www.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©13, OU=GT10270993, SERIALNUMBER=6iRebnvENcZAngMRRe2EIbG-U9aO6U7U
        Connection result: 200/OK
    Client Website - client.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©13, OU=GT10270993, SERIALNUMBER=6iRebnvENcZAngMRRe2EIbG-U9aO6U7U
        Connection result: 200/OK
    Version Server - version.vuze.com
        Connection result: 200/OK
    Pairing Server - pair.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©13, OU=GT10270993, SERIALNUMBER=6iRebnvENcZAngMRRe2EIbG-U9aO6U7U
        Connection result: 200/OK
    License Server - license.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©13, OU=GT10270993, SERIALNUMBER=6iRebnvENcZAngMRRe2EIbG-U9aO6U7U
        Connection result: 200/OK
    Plugins Website - plugins.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©13, OU=GT10270993, SERIALNUMBER=6iRebnvENcZAngMRRe2EIbG-U9aO6U7U
        Connection result: 200/OK
Indirect Connect test
    Connecting to https://www.vuze.com
    Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©13, OU=GT10270993, SERIALNUMBER=6iRebnvENcZAngMRRe2EIbG-U9aO6U7U
    Connection result: 200/OK
Distributed protocol test
  Incoming routing established for BDF47071C9CF44F6005AAFF37A951E86C6102EA5
  Searching 128 contacts for 8 test targets
  Making outbound connection to /93.31.113.10:6881
  Making outbound connection to /87.21.52.141:17899
  Making outbound connection to /92.90.211.155:58189
  Making outbound connection to /109.131.134.163:25795
  Making outbound connection to /114.77.188.54:43724
  (LS 2) Outbound connection fail: Connection attempt to 87.21.52.141:17899 aborted: timed out after 15sec
  Making outbound connection to /88.234.221.78:54959
  Making outbound connection to /72.200.200.110:15211
  Making outbound connection to /84.48.102.152:50000
  Searching complete, 8 targets found
    Status: sessions=7, out_attempts=8, out_connect=7, in_connect=0
  Destroying tester
Test complete
  Results
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,not connected
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    No incoming connections received, likely NAT problems
  Incoming routing destroyed for BDF47071C9CF44F6005AAFF37A951E86C6102EA5

Could anybody help me please????????

Thank you for your help!!!!!
 

[renno69]

same problem here (plus others) thought at first it was my external ip (assigned by isp) because when they changed it everything started working again but after 24hrs it stopped again it could be possible the isp has done something they wont admit to or there is a conflict with vuze's latest update (this problem for me only started with the latest update), if anyone figures this out pls let me know also

[hakayova]

Same problem here. UDP port works well through 2 routers, software firewall and selinux. TCP port does not. Canyouseeme.org CAN reach and confirm Vuze service on the TCP port I am using. Please see below my Vuze test output.

Test starting
Default public address is 46.166.186.198
0 NAT devices found
One SOCKS proxy found
    -blocked by hakayova-
No HTTP proxy found
No explicit bind address set
Testing HTTP outbound
    Test successful
Testing TCP outbound
    Test successful
Testing UDP outbound
    Test successful
Testing TCP port 21003 inbound
    Test failed: NAT test failed: Connection to 109.201.154.213:21003 (your computer) refused
    Check your port forwarding for TCP 21003
Testing UDP port 21003 inbound
    Sending outbound packet and waiting for reply probe (timeout=5000)
    Sending completion event
    Test successful
3 public/external addresses found
    -blocked by hakayova-
Vuze Services test
    Vuze Website - http://www.vuze.com
        Failed: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: EC AlgorithmParameters not available
    Client Website - client.vuze.com
        Failed: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: EC AlgorithmParameters not available
    Version Server - version.vuze.com
        Connection result: 200/OK
    Pairing Server - pair.vuze.com
        Failed: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: EC AlgorithmParameters not available
    License Server - license.vuze.com
        Failed: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: EC AlgorithmParameters not available
    Plugins Website - plugins.vuze.com
        Failed: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: EC AlgorithmParameters not available
Distributed protocol test
  Incoming routing established for 53161D017DF03A5B69659FE94DBEE238DAC6B372
  Searching 128 contacts for 8 test targets
  Making outbound connection to /71.107.26.23:6881
  Making outbound connection to /90.171.16.116:56512
  Making outbound connection to /84.209.82.138:38012
  Making outbound connection to /84.29.224.244:20170
  Making outbound connection to /108.53.96.91:46267
  Making outbound connection to /90.165.176.68:51728
  Making outbound connection to /108.66.156.19:63654
  Got incoming connection from /71.107.26.23:56627
  Making outbound connection to /99.194.0.158:58273
  Got incoming connection from /108.53.96.91:50624
  Got incoming connection from /108.66.156.19:2007
  Got incoming connection from /90.171.16.116:58364
  Got incoming connection from /84.209.82.138:55148
  Making outbound connection to /203.173.13.96:19389
  Got incoming connection from /84.29.224.244:4902
  Got incoming connection from /99.194.0.158:56989
  Got incoming connection from /90.165.176.68:49525
  (LS 14) Outbound connection fail: end of stream on socket read
  Got incoming connection from /203.173.13.96:60822
  Searching complete, 9 targets found
    Status: sessions=17, out_attempts=9, out_connect=8, in_connect=9
    Status: sessions=17, out_attempts=9, out_connect=8, in_connect=9
  Destroying tester
  Results
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand !recv, bitf !sent, bitf !recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,not connected
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Test complete
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Test successful
  Incoming routing destroyed for 53161D017DF03A5B69659FE94DBEE238DAC6B372


I am using Fedora 21, java-1.8.0-openjdk, azureus 5.5.0.0. I tried this with selinux disabled as well as enabled/permissive and enabled/enforced options, all with the same result. Switching TCP port to other unused numbers (such as 55100, 61001, etc.) does not seem to change the behavior either.

Any pointers will be greatly appreciated.

 

 

 

[hakayova]

I hate to reply to my own post, but despite the errors reported above and yellow faces all over, Vuze/Azureus seems to work well and still gets the job done. Perhaps there is something wrong with the error reporting part.

 

[parg]

Incoming TCP connections via SOCKs will only work if your SOCKs proxy supports them, and I think a lot don't. UDP on the other hand has more chance of working.

That being said, the uTP protocol runs over UDP so the lack of TCP support generally isn't that much of an issue.

[hakayova]

Thank you so much for the response. That was exactly my experince so far. Thanks again for confirming.