Testing TCP port 61351 inbound

[VuzeDude]

Q: Any advice on how to resolve the errors. I'm perhaps an intermediate level pc user as far as tweaking goes, so please dumbify it for me. TIA! 

When doing both general testing and NAT/Server testing, the following resulted:
[Using an paid VPN service and private router.]

-BEGINS-

General Settings Test Results:

Testing TCP port 61351 inbound
    Test failed: NAT test failed: Connection to 104.156.228.134:61351 (your computer) refused
    Check your port forwarding for TCP 61351
Testing UDP port 61351 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 61351

  (LS 12) Outbound connection fail: end of stream on socket read

  No incoming connections received, likely NAT problems


NAT/SERVER Port Test Results:

Testing port TCP 61351 ... 
NAT Error - Connection to 104.156.228.134:61351 (your computer) refused.

Testing port UDP 61351 ... 
    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
NAT Error. Inbound test failed, timed out.

-ENDS-

[Pendaws]

VPN Configuration
To a large extent Virtual Private Networks (VPNs) are transparent to Vuze - they intercept your network packets at the point where the operating system routes them and forces the packets to be sent to the VPN servers for forwarding. However, assuming that your VPN is implemented on your machine as a separate network interface you can set some configuration option in Vuze to explicitly tell it to use that interface. This can be an advantage if your VPN connection is unreliable - if it fails, rather than the OS falling back to routing packets though the public IP network Vuze will continue to explictly attempt to route those packets through the VPN (which will fail, but at least the packets won't have be sent elsewhere)

Vuze options are documented here. First set your Mode to 'Advanced'. Next go to Connections->Advanced Network Settings and locate the interface name for your VPN (e.g. eth<number>). Enter this interface name in the 'Bind to local IP address or interface' box. Now scroll down to the bottom and check the 'Enforce IP bindings even when interfaces are not available' option.

More recent versions of Vuze will attempt to detect when your traffic is being routed via a VPN interface and offer to perform this configuration change for you.

If your VPN provider doesn't support incoming connections then you can explicitly disable these in Vuze by deselecting 'Incoming Connection' under 'Peer Sources' in Connections - if for some reason your public IP address is leaked (e.g. you start a download with your VPN disconnected and haven't bound explicitly to an interface) this will prevent other peers from connecting to you via this public IP.

If you have either manually or automatically setup the VPN interface binding the VPN connectivity status is shown in the status area:

Route
This will be red if there are connectivity issues, for example your VPN connection has failed.

Note that lack of incoming connection support by your VPN provider will cause Vuze to report that you have a 'NAT problem' - this is reported whenever Vuze detects an absence of incoming connections.

[VuzeDude]

Thank you!