Any Port Forwarding In A Storm

Hi,

Cannot seem to get Port Forwarding to work
ISP - Comcast
Windows 7 Pro 64 Bit
Vuze Plus & PIA VPN
 Have Static IP Address
I am connecting to Network WIFI
My NAT / Server Port Tests for TCP and UDP are OK
I am connecting to a country that allows Port Forwarding
RT-N16 Asus Router - Port Forwarding Enabled and Port 56621 added for TCP and UDP
Inbound and Outbound rules to allow port 56621 to connect thru my Windows Firewall 

Here is text from VPN Helper Plugin I added:
Port Forwarding and IP Binding 
VPN HAS WARNINGS 
Vuze UDP is currently bound to 110.42.1010 aka eth5 (TAP-Windows Adapter V9) 
Found bindable address /10.42.10.10 on eth5 (TAP-Windows Adapter V9) which is likely VPN’s local IP 
 Non-Vuze probably routing through /10.42.10.10 aka eth5 (TAP-Windows Adapter V9). Same as bindable address:) 
‘Excellent Vuze already bound to eth5 
 Could not get Forwarding Port. Ensure PIA Manager directory is properly set, or set user/pass in plugin config. 

[Verity public address(es)
Last Checked 27-Jan-2017 12:37:21 
HTTP outbound - /46.166190.224 - Netherlands 
TCP outbound - /46.166190.224 - Netherlands 
UDP outbound - /46166190.224 - Netherlands 

Test starting

Default public address is 46.166.190.224

Bindable addresses: 127.0.0.1, 192.168.1.38, 10.42.10.10

0 NAT devices found

No SOCKS proxy found

No HTTP proxy found

1 bind addresses

    10.42.10.10

Testing HTTP outbound

    Test successful

Testing TCP outbound

    Test successful

Testing UDP outbound

    Test successful

Testing TCP port 56621 inbound

    Test successful

Testing UDP port 56621 inbound

    Sending outbound packet and waiting for reply probe (timeout=5000)

    Sending completion event

    Test successful

1 public/external addresses found

    46.166.190.224

    AS details: as=43350,asn=NFORCE , NL, bgp_prefx=46.166.184.0/21[/46.166.184.0-/46.166.191.255]

Vuze Services test

    Vuze Website - www.vuze.com

        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)15, OU=GT10270993

        Connection result: 200/OK

    Client Website - client.vuze.com

        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)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(R), OU=See www.rapidssl.com/resources/cps (c)15, OU=GT10270993

        Connection result: 200/OK

    License Server - license.vuze.com

        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)15, OU=GT10270993

        Connection result: 200/OK

    Plugins Website - plugins.vuze.com

        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)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(R), OU=See www.rapidssl.com/resources/cps (c)15, OU=GT10270993

    Connection result: 200/OK

Distributed protocol test

  Incoming routing established for EE4B9A55C45FCFBA4AEDEC27C2BE1445663D0D52

  Searching 128 contacts for 8 test targets

  Making outbound connection to /95.34.210.153:49132

  Making outbound connection to /82.11.49.250:61646

  Making outbound connection to /109.97.116.145:35524

  Got incoming connection from /82.11.49.250:59500

  Making outbound connection to /49.176.181.76:31277

  Got incoming connection from /95.34.210.153:61654

  Got incoming connection from /109.97.116.145:56663

  Making outbound connection to /65.41.7.175:56410

  Making outbound connection to /85.3.107.157:29952

  Got incoming connection from /49.176.181.76:61444

  Got incoming connection from /65.41.7.175:49413

  Got incoming connection from /85.3.107.157:58591

  Making outbound connection to /89.115.27.237:63853

  Making outbound connection to /184.156.221.195:6881

  Got incoming connection from /184.156.221.195:56943

  Got incoming connection from /89.115.27.237:54361

  Searching complete, 8 targets found

    Status: sessions=16, out_attempts=8, out_connect=8, in_connect=8

    Status: sessions=16, out_attempts=8, out_connect=8, in_connect=8

  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

    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

    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

    Inbound,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

    Outbound,Seed,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 successful

Test complete

  Incoming routing destroyed for EE4B9A55C45FCFBA4AEDEC27C2BE1445663D0D52

Thanks in advance!


gregmy123

Sign In or Register to comment.