TCP/UDP Listen Port Connection Timed Out

[Thebaby]

Hello, first time posting in the forums and I'm new to Vuze and a lot of network stuff, so try to bear with me here.

Background information: I'm from Canada, my ISP is MTS allstream. I'm running a VPN on my computer. Currently, I have my downloading computer set up in a different house (using software to control the downloading PC from my house), so everything i refer to will be about the other house where the downloading PC is in (like router settings, IP addresses, etc). I have a wired connection to the PC. I also set Vuze to enforce IP bindings with my VPN (in Options>Connection>Advanced Network Settings), so that when my VPN drops, the downloads will stop, and when my VPN restarts, the downloads will start up again. I am running Windows Vista Home Premium (6.0, Build 6002), and my Antivirus is Microsoft Security Essentials and my firewall is the Windows Firewall that came with the PC. As for the forum announcement rules, here is my system info under Help>About Vuze:

Java 1.7.0_79
 Oracle Corporation
SWT v4508, win32
Windows Vista v6.0, x86
V5.6.1.0/4 az3

Now, as for the problem I am having. It seems to be a NAT problem. I have an Actiontec router that supports Network Address Translation, and i port forwarded it (first i set a static IP with the downloading PC). I did this all by going through the walkthrough from the wiki. Now a lot (actually all) of my torrents either have the yellow faces, and periodically turn red. Now, I do have a bad share ratio because i just started out yesterday, so there might be some users banning me from downloading from them, but i don't think that is the case.

I found that when i run my torrents WITHOUT my VPN, i get much faster speeds than when i run it WITH my VPN. However, the yellow/red faces stay regardless, which makes me think there is an underlying issue. So what i did, i went through the Wiki on NAT problems and did every step:

• Router has the option for UPnP. I pushed enable (only option was enable/disable, nothing else). It did not fix the issue
  
• I set a static IP for my downloading computer
  
• I port forwarded my router. While port forwarding, i put the LAN ip as the static ip assigned to my computer, and set individual rules for inbound TCP and UDP ports (port 44387, same as listed in Vuze under Options>Connection)
  
• I disabled my firewall and my antivirus. Still did not fix the issue, so i reenabled them.
  

After trying all this and still finding no success, i decided to run the NAT/Firewall test and Network Status test under Help on Vuze.

During the NAT/Firewall test, I test the Incoming TCP Listen Port 44387 (same as listed under Connections, and the port i set a rule to Port Forward), and this is what i get:

• Testing Port TCP 44387.... NAT Error - Connection timed out (50.188.22.173:44387)
  

Then the UDP Listen Port:

• Testing Port UDP 44387..... Sending outbound packet and waiting for reply probe (timeout=5000).... (timeout=10000)....(timeout=15000)...Sending completion event..... NAT Error. Inbound test failed, timed out.
  

Then i do the Network Status Test, and this is all the information copy/pasted:

• Test starting
  Default public address is 50.188.22.176
  1 NAT device found
      Actiontec GT784WN: address=192.168.100.254:5431, public address=207.161.103.83
  No SOCKS proxy found
  No HTTP proxy found
  1 bind addresses
      10.211.1.1
  Testing HTTP outbound
      Test successful
  Testing TCP outbound
      Test successful
  Testing UDP outbound
      Test successful
  Testing TCP port 44387 inbound
      Test failed: NAT test failed: Connection timed out (50.188.22.176:44387)
      Check your port forwarding for TCP 44387
  Testing UDP port 44387 inbound
      Sending outbound packet and waiting for reply probe (timeout=5000)
      Sending outbound packet and waiting for reply probe (timeout=10000)
      Sending outbound packet and waiting for reply probe (timeout=15000)
      Sending completion event
      Test failed: Inbound test failed
      Check your port forwarding for UDP 44387
  2 public/external addresses found
      50.188.22.176
      AS details: as=13367,asn=COMCAST-13367 - Comcast Cable Communications Holdings, Inc,US, bgp_prefx=50.188.0.0/17[/50.188.0.0-/50.188.127.255]
      207.161.103.83
      AS details: as=7122,asn=MTS-ASN - MTS Allstream Inc.,CA, bgp_prefx=207.161.103.0/24[/207.161.103.0-/207.161.103.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 ©15, OU=GT10270993
          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 ©15, OU=GT10270993
          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 ©15, OU=GT10270993
          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 ©15, OU=GT10270993
          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 ©15, OU=GT10270993
          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 ©15, OU=GT10270993
      Connection result: 200/OK
  Distributed protocol test
    Incoming routing established for 25489A74AE731556384D330DFEA347C6F9F0ACC2
    Searching 128 contacts for 8 test targets
    Making outbound connection to /69.249.72.77:28370
    Making outbound connection to /78.8.108.50:61145
    Making outbound connection to /220.240.162.131:27832
    Making outbound connection to /88.136.24.57:52108
    Making outbound connection to /89.95.25.41:48634
    Making outbound connection to /50.150.27.21:42473
    Making outbound connection to /24.228.33.203:29453
    Making outbound connection to /2.31.123.126:6881
    (LL 3) Outbound connection fail: end of stream on socket read
    (LS 8) Outbound connection fail: end of stream on socket read
    Making outbound connection to /86.6.80.20:6881
    (LL 9) Outbound connection fail: end of stream on socket read
    Searching complete, 9 targets found
      Status: sessions=6, out_attempts=9, out_connect=9, in_connect=0
      Status: sessions=6, out_attempts=9, out_connect=9, in_connect=0
    Destroying tester
    Results
      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,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
      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
  Test complete
    Incoming routing destroyed for 25489A74AE731556384D330DFEA347C6F9F0ACC2
  

Now i know this is a lot of writing, and I'm sorry for that. I see it says the test failed on my TCP and UDP port 44387, but I'm sure i port forwarded it correctly. And i don't understand the "end of stream on socket read" part of the test. And just to remind you, the speeds are slower through the VPN which i'm alright with, but even when the VPN isn't enabled, i still have all yellow/red smiley faces in Vuze.

I'm kind of lost at this point, so I'm hoping someone can help me out with the information I've provided. Thanks in advance.

[parg]

VPN is pretty much always going to be slower than direct connection - often VPNs don't support incoming connections so you won't be able to get happy green connections for downloads when running over VPN, then again, I don't know the specifics of your setup.

However, it is interesting that you appear to have two public IP addresses:

2 public/external addresses found

    50.188.22.176
    AS details: as=13367,asn=COMCAST-13367 - Comcast Cable Communications Holdings, Inc,US, bgp_prefx=50.188.0.0/17[/50.188.0.0-/50.188.127.255]
    207.161.103.83
    AS details: as=7122,asn=MTS-ASN - MTS Allstream Inc.,CA, bgp_prefx=207.161.103.0/24[/207.161.103.0-/207.161.103.255]

Is MTS routing stuff through Comcast? It seems as if connections from your computer are hitting the 207.161.103.0/24 network, getting routed to 50.188.0.0/17 and then getting to Vuze's NAT test servers.

[Thebaby]

Is MTS routing stuff through Comcast? It seems as if connections from your computer are hitting the 207.161.103.0/24 network, getting routed to 50.188.0.0/17 and then getting to Vuze's NAT test servers.

 

I'm not that knowledgable about this kind of stuff so I can't say with 100% certainty, but my VPN is located in the United States however, and it's IP address is 50.188.22.176 which seems to be the one associated with comcast.
And I'm alright with slower speeds, its just that with the VPN down i also don't get the green smiley's so i thought there was a bigger issue. For my torrents, most of the time there will be 80-100 seeds in the swarm, but i will only be connected to 0-5 of them at a time. I thought I'd ask in the forums to shed some light on it. Thanks for the input.

[FeRDNYC]

And I'm alright with slower speeds, its just that with the VPN down i also don't get the green smiley's so i thought there was a bigger issue.

Your Vuze setup is configured to listen for / forward incoming connections on your VPN connection. You can see that in the Network Status Test output, for instance:

Testing TCP port 44387 inbound
    Test failed: NAT test failed: Connection timed out (50.188.22.176:44387)
    Check your port forwarding for TCP 44387

Vuze is looking for incoming connections to 50.188.22.176 port 44387. So, when it's up you don't get green Health smilies because the VPN doesn't allow that (perhaps), and when it's down you don't get them because... well... it's down. :-)

To get green smilies with the VPN down, you'd have to make sure that Vuze is configured with your non-VPN address as its public IP, and that the appropriate ports are being forwarded from the public IP of your NAT router to your computer's private address, as seen here:

1 NAT device found
    Actiontec GT784WN: address=192.168.100.254:5431, public address=207.161.103.83

For my torrents, most of the time there will be 80-100 seeds in the swarm, but i will only be connected to 0-5 of them at a time.

That's not necessarily unusual, the "share" of torrent seeds you'll get is also a factor of how many other peers there are. If there are ~100 seeders and 1000 peers, they're going to be spread pretty thin. But, you should also be getting connections to (some of) those other peers, and exchanging blocks with them as well.

However, having incoming connections not working, and being limited to only the seeds/peers you're able to make outgoing connections to, will definitely lower your connection counts. Though, BitTorrent being what it is, that doesn't always mean it will limit your speed. I've had situations where network problems were interfering with incoming connections (crappy consumer routers!), but I could still get > 1MB/s transfer speeds just with to the few swarm members I was able to connect to!

Incoming connections are actually a bigger deal for small swarms, with few seeds — because that's when being limited as to how many of them you can reach becomes a more serious problem. If there are only 7 seeds and you can't establish outgoing connections to 5 of them, well... better cross your fingers that the other two have fast uplinks!

[GaryE]

Just to add my $0.02 worth.  I would contact your VPN provider and ask them if it is even possible for you to get connectible through their VPN.  Their answer could save you a lot of work LOL

Good Luck!