TechSpot

NAT error with Azureus even though UPnP works

By insanexyz
Aug 25, 2011
Post New Reply
  1. Hi, sorry to be annoying with this again, but I spent 3 hours trying everything I could possibly find on the internet to no avail.
    I've set up a static IP at 192.168.1.101, set Azureus to listen at TCP/UDP ports 53981 then went into my router and set up port forwarding with the aforementioned details. While I was browsing through that i noticed that Azureus works with the UPnP feature of the router, it even notified me itself that it established the connection.

    However, when I use the NAT testing feature in Azureus (Vuze) it still says connection refused. Internet port checkers with the port 53981 still say the port is closed too. Any advice will be greatly appreciated.

    Edit: also disabled my software firewall, no help there either.
     
  2. jobeard

    jobeard TS Ambassador Posts: 9,311   +617

    get a command prompt and enter netstat -an ; the results are shown below
    If your program is active, then the second column will contain 0.0.0.0:53981
    Code:
    Active Connections
    
      Proto  Local Address          Foreign Address        State
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:1028           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:8019           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:44334          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:44501          0.0.0.0:0              LISTENING
      TCP    127.0.0.1:1025         127.0.0.1:44334        ESTABLISHED
      TCP    127.0.0.1:1028         127.0.0.1:1030         ESTABLISHED
      TCP    127.0.0.1:1030         127.0.0.1:1028         ESTABLISHED
      TCP    127.0.0.1:1031         0.0.0.0:0              LISTENING
      TCP    127.0.0.1:1039         127.0.0.1:1040         ESTABLISHED
      TCP    127.0.0.1:1040         127.0.0.1:1039         ESTABLISHED
      TCP    127.0.0.1:1041         127.0.0.1:1042         ESTABLISHED
      TCP    127.0.0.1:1042         127.0.0.1:1041         ESTABLISHED
      TCP    127.0.0.1:4785         127.0.0.1:4786         ESTABLISHED
      TCP    127.0.0.1:4786         127.0.0.1:4785         ESTABLISHED
      TCP    127.0.0.1:4787         127.0.0.1:4788         ESTABLISHED
      TCP    127.0.0.1:4788         127.0.0.1:4787         ESTABLISHED
      TCP    127.0.0.1:12080        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:12110        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:12143        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:12993        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:12995        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:19989        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:44334        127.0.0.1:1025         ESTABLISHED
      TCP    192.168.0.4:139        0.0.0.0:0              LISTENING
      TCP    192.168.0.4:4945       74.125.53.113:80       TIME_WAIT
      UDP    0.0.0.0:445            *:*
      UDP    0.0.0.0:1026           *:*
      UDP    0.0.0.0:1029           *:*
      UDP    0.0.0.0:4987           *:*
      UDP    0.0.0.0:44334          *:*
      UDP    127.0.0.1:123          *:*
      UDP    192.168.0.4:123        *:*
      UDP    192.168.0.4:137        *:*
      UDP    192.168.0.4:138        *:* 
     
  3. insanexyz

    insanexyz TS Rookie Topic Starter

    It indeed does, both TCP and UDP
    everything still says 53981 is closed though
     
  4. jobeard

    jobeard TS Ambassador Posts: 9,311   +617

    If you have a second system on the same LAN - -

    get a command prompt and enter CMD

    then use telnet 192.168.1.101 53981

    If the connection is refused, or timesout, then your firewall is still impacting you.
    Otherwise your FW & systems are ok and the router is not forwarding
     
  5. insanexyz

    insanexyz TS Rookie Topic Starter

    No telnet on win 7. I guess I'll just give up, I've been trying to get this to work for years and it never did.
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...