Jump to content

UPnP in 1.6 not working for you? Post here


Firon

Recommended Posts

from http://www.utorrent.com/faq.php

# net.outgoing_port makes µTorrent use a single outgoing port. This should only be used in specific cases. "This can be used with full cone NAT routers to reduce the number of NAT table entries and thus prevent crashes on some router models. When the outgoing port is bound to the same as the incoming port that might even solve NAT problems on full cone NAT routers." - AzureusWiki. This option may not be working properly. It will only work on Windows 2000 and later.

Link to comment
Share on other sites

  • Replies 299
  • Created
  • Last Reply

Yes I read this if the FAQ and understand the role of thet setting. But my question is why UPNP would fail with this is set and would work when it is not set....

I left the net.outgoing_port bound to 59626 and varied the incoming port port from 59600 to 59610. Each time I recieved the same error in the log that it couldn't set any of the ports (59600-59610) while the net.outgoing_port was defined.

I then set net.outgoing_port back to default and ran though the same port range for the incoming port (59600-59610) and the UPNP registration worked fine.

So I think the bug here is that UPNP doesn't work when setting net.outgoing_port.

Here is the log of the messages while the net.outgoing_port was set:

[17:35:33] UPnP: Discovered new device: http://192.168.10.1:5431/uuid:0016-018d-88d20200e1b4/WANIPConnection:1

[17:36:29] UPnP: ERROR -3 mapping port 59600 -> 192.168.10.3:59600

[17:36:42] UPnP: ERROR -3 mapping port 59601 -> 192.168.10.3:59601

[17:36:57] UPnP: ERROR -3 mapping port 59602 -> 192.168.10.3:59602

[17:37:05] UPnP: ERROR -3 mapping port 59603 -> 192.168.10.3:59603

[17:37:15] UPnP: ERROR -3 mapping port 59604 -> 192.168.10.3:59604

[17:37:37] UPnP: ERROR -3 mapping port 59605 -> 192.168.10.3:59605

[17:37:43] UPnP: ERROR -3 mapping port 59606 -> 192.168.10.3:59606

[17:37:59] UPnP: ERROR -3 mapping port 59607 -> 192.168.10.3:59607

[17:38:10] UPnP: ERROR -3 mapping port 59608 -> 192.168.10.3:59608

[17:38:18] UPnP: ERROR -3 mapping port 59609 -> 192.168.10.3:59609

[17:38:29] UPnP: ERROR -3 mapping port 59610 -> 192.168.10.3:59610

Link to comment
Share on other sites

  • 2 weeks later...

UPnP: error -3

I am using a Belkin F5D7230-4 Ver.6 wireless G router and uTorrent 1.6.1 Build 490

In the logger section of utorrent i see the message "[06:27:35] UPnP: ERROR -3 mapping port 35515 -> 192.168.88.200:35515"

I have upgraded the firmware to the latest build and still the problem persist.

So i tested using "UPnPPW_Win32-b2.0a" and the UPnP port mapping works fine with the router.

Now I can safely say that it is a bug in the UPnP function of uTorrent.

So currently I have to use "UPnPPW_Win32-b2.0a" to handle the UPnP port mapping.

Hope it will be fixed soon in uTorrent.

Link to comment
Share on other sites

I don't know if this is the right place to post it, but I had a strange problem where uTorrent would find something on 192.168.1.1 which shouldn't exist on my network, as all my ip's are 10.xxx. Through much trial and error I found out that it was the wi-fi adapter for my Nintendo DS. So, I disabled it, restarted uTorrent and then let uTorrent get a UPnP socket on my ACTUAL router, and then reenabled the wifi adapter, and it works!

Just thought I'd share, in case other people have wifi adapters.

Link to comment
Share on other sites

  • 2 weeks later...

Temp fix for UPnP in Vista Ultimate!

This is going to sound wierd but it seems to work,

Download Azureus,

Install,

Once installed run Azureus and MINIMIZE the program,

Once MINIMIZED run Utorrent,

Now look, UPnP is working

Make sure your router supports UPnP etc

Now close Azureus & Utorrent and re-open Utorrent on it's own and UPnP will be unable to map again :-\ Strange

P.S. Sorry if this has been posted before!

Link to comment
Share on other sites

Yeah, it has been posted before :P

Don't hold me responsible for unfulfilled hopes if this doesn't prove true, but I think the next build of the 1.7 betas *should* fix most of the UPnP issues for users. The devs tested a bunch of builds with someone having UPnP issues, and got it working nicely. Here's to hoping!

Link to comment
Share on other sites

My uTorrent 1.6 (build 474) isn't working and I get this error message:

uTorrent_Naplo_www.kepfeltoltes.hu_.jpg

I have SMC - SMC7004VBR router and I can download very slowly and I can't seed. :(

These are my settings:

I use Windows XP with Service Pack 2 and I have static IP.

My uTorrent's settings (the language is hungarian but teh function af the buttons are the same):

uTorrent___Beallitasok___Kapcsolat_www.kepfeltoltes.hu_.jpg

My router's settings:

status_www.kepfeltoltes.hu_.jpg

NAT___Virtual_Server_www.kepfeltoltes.hu_.jpg

help me, please...

Thank you.

Link to comment
Share on other sites

Hmm, it seems that last beta of DD-WRT x86 (DD-WRT v24 Beta (05/02/07) std - build 6916) works with UPnP, as formerly it wasn't working at all.

Ofcourse I can'ttell is it DD-WRT or uTorrent 1.7 fix, but in any case I'm only too happy and wanted to share this to other DD-WRT users here. Reminder: This affected AFAIK users with 64-bit Windows and DD-WRT router.

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

With 1.6.1 (490) utorrent isn't able to map a port at startup or during the periodic retry, but if I go into the preferences and change the port it's able to map it right away.

I'm pretty sure it's not a problem with my router (linksys wrt54g v5) because it happens even when utorrent is set to randomize the port at startup.

Link to comment
Share on other sites

Same deal with 1.7:

[00:12:19] UPnP: Discovered new device: http://192.168.1.1:2869/WANIPConnCtrlUrl

[00:12:19] UPnP: ERROR 718 mapping port 40901 -> 192.168.1.100:40901; Deleting Mapping and trying again

[00:12:19] UPnP: Removed port 40901

[00:12:19] UPnP: ERROR 718 mapping port 40901 -> 192.168.1.100:40901

[00:12:31] UPnP: Mapped port 29872 -> 192.168.1.100:29872

[00:12:31] UPnP: Getting external IP

[00:12:31] UPnP: Got external IP: xxx.xxx.xxx.xxx

Link to comment
Share on other sites

As I mentioned in my initial post this happens even when the Randomize Port option is set, the ports aren't already allocated to another client.

I played around with it a bit more and noticed that if I leave it to retry on it's own it'll keep failing, but if I change to a different port, then wait a few minutes and then change back, the original port will work. Whatever is going wrong only happens at startup, if the ports are mapped while the program is running everything is fine.

Link to comment
Share on other sites

[09:36:51] UPnP: Discovered host: http://192.168.2.1:49152/gatedesc.xml

[09:36:51] UPnP: Mapped TCP port 16654 -> 192.168.2.101:16654

[09:36:51] UPnP: Getting external IP

[09:36:51] UPnP: Unable to get external port.

[09:37:02] UPnP: Removed TCP port 16654

[09:37:02] UPnP: Getting external IP

[09:37:02] UPnP: Unable to get external port.

XML file: http://warp.aeoland.com/gatedesc.xml

Checked with UPnP software checking - shows that everything passed and ok.

I have sweex (like edimax) router (LB00002153c230044) based on Infineon ADM5120P chip.

Link to comment
Share on other sites

My router D-Link DI-524 is UPnP capable and enabled. Everything that could possibly turn on or enable UPnP is on and enabled. DMZ is not enabled. My Log says that ports are mapping just fine. And I used this port forwarding test by this one program, and everything seemed to work just fine. But yet when I do the utorrent port forwarding test, it says the port is not open. My dad also tried manually port forwarding for utorrent and that didn't work either. I have not tried testing the UPnP on any other BitTorrent client so I don't know if it is just utorrent or its the network. Maybe I could try that?

Link to comment
Share on other sites

  • 3 weeks later...

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...