Community Forums

Home » Vuze Forums » Download / Connection Problems


Thread: Outbound Connection Fail?


Thread Locked This thread is locked - replies are not allowed.


This question is not answered. Helpful answers available: 3. Correct answers available: 1.

Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 3 - Pages: 1 - Last Post: Nov 23, 2011 8:47 AM Last Post By: bazeemuth
bazeemuth

Posts: 3
Registered: 11/23/11
Outbound Connection Fail?
Posted: Nov 22, 2011 9:30 PM
 
Click to report abuse...

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

Test successful

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 /86.165.230.5:32278
Making outbound connection to /70.81.102.169: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 /70.81.102.169:51491
(RL 11) Inbound connect start
(RL 11) Inbound connect success
(RL 11) Incoming message received: BT_HANDSHAKE
Got incoming connection from /86.165.230.5: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
Java 1.5.0_10
Vuze V4.7.0.0/4 az3
Windows Firewall is Off

Help?
newname600


Posts: 672
Registered: 03/29/10
Re: Outbound Connection Fail?
Posted: Nov 22, 2011 11:24 PM   in response to: bazeemuth in response to: bazeemuth
 
Click to report abuse...
You don't have your firewall set to high or cookie blocking ? Seems funny you got incoming but not outgoing. Something else using that port ?
bazeemuth

Posts: 3
Registered: 11/23/11
Re: Outbound Connection Fail?
Posted: Nov 23, 2011 6:57 AM   in response to: newname600 in response to: newname600
 
Click to report abuse...
Yeah, forgot to mention I have the router's firewall allowing port 50000, UDP and TCP outbound, from PC to anywhere on WAN side, and from anywhere on WAN side to PC.

Cookies? What cookies.

netstat shows nothing using port 50000 unless Vuze is running.

Edited by: bazeemuth on Nov 23, 2011 6:57 AM
bazeemuth

Posts: 3
Registered: 11/23/11
Re: Outbound Connection Fail?
Posted: Nov 23, 2011 8:47 AM   in response to: bazeemuth in response to: bazeemuth
 
Click to report abuse...
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.
Legend
Master: 800 - 9999 pts
Expert: 400 - 799 pts
Advanced: 200 - 399 pts
Intermediate: 100 - 199 pts
Beginner: 50 - 99 pts
Newbie: 0 - 49 pts
Vuze Staff Member
Vuze Community Moderator
Helpful Answer (3 pts)
Correct Answer (5 pts)

Point your RSS reader here for a feed of the latest messages in all forums