Outbound Connection Fail?
Nov 22, 2011 9:30 PM
I see no torrent activity whatsoever on Vuze. Running the Network Status plugin produces (among the normal stuff) these messages:
0 NAT devices found
One SOCKS proxy found
127.0.0.1:41, versions=unknown (Connect failed)
No HTTP proxy found
No explicit bind address set
Testing HTTP outbound
Test successful Testing TCP outbound
Test failed: Outbound test failed Testing UDP outbound
Test successful Testing TCP port 50000 inbound
Test successful Testing UDP port 50000 inbound
Sending outbound packet and waiting for reply probe (timeout=5000)
Sending completion event
1 public/external addresses found
And a lot of this kind of stuff, later on:
(RL 7) Incoming message received: BT_BITFIELD
Making outbound connection to /220.127.116.11:32278
Making outbound connection to /18.104.22.168:11740
(LL 9) Outbound connect start
(LS 10) Outbound connect start (LL 1) Outbound connection fail: Connection refused: no further information
(LS 2) Outbound connection fail: Connection refused: no further information Got incoming connection from /22.214.171.124:51491
(RL 11) Inbound connect start
(RL 11) Inbound connect success
(RL 11) Incoming message received: BT_HANDSHAKE
Got incoming connection from /126.96.36.199:54172
My router/modem/PC setup (wired connection PC<=>Router<=>Modem<=>AT&T):
Router: Trendnet TEW-651BR, does NAT with port 50000 TCP & UDP forwarded to Vuze (and that port set in Vuze options). Not uPNP.
PC has a static IP set in the TEW-651BR config.
Modem: AT&T Motorola
2210-02; No port-forwarding available, but "Let LAN device share Internet address" is set, and the router shows a public IP on WAN side.
ISP: AT&T DSL (not Uverse)
OS: WinXP SP2
Vuze V188.8.131.52/4 az3
Windows Firewall is Off
Re: Outbound Connection Fail?
Nov 23, 2011 8:47 AM
in response to: bazeemuth
Perhaps most importantly (oops): This same PC and AT&T modem allowed good Vuze connectivity with my old Netgear router (which was great, but failed after two years). So it seems likely that the $18 Trendnet router is site of the problem. I didn't have the modem set to "Allow router to use the same IP address" with the Netgear router, but I didn't with the Trendnet router, either, until I started trying to debug this Vuze problem.