UPnP/NAT-PMP: Port Mapping Failure: Can't Foward Ports

[war59312]

Hi,

OK, I am having a major issue with getting a port successfully forwarded for qBittorrent.

Running qBittorrent v3.0.10 on Windows 7 x64 SP1.

Router: D-Link DIR-655
Firmware Version: 1.35NA
Hardware Version: A2

UPnP/NAT-PMP: Port mapping failure log:

11/07/2013 00:21:57 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP:
11/07/2013 00:21:57 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 31362
11/07/2013 00:21:55 - 'magnet:?xt=urn:btih:IE2CRCBU424MO2DWB2QKJQYIIRG5IIP5' added to download list.
11/07/2013 00:21:55 - Options were saved successfully.
11/07/2013 00:21:55 - Embedded Tracker [OFF]
11/07/2013 00:21:55 - Encryption support [FORCED]
11/07/2013 00:21:55 - Local Peer Discovery support [ON]
11/07/2013 00:21:55 - PeX support [ON]
11/07/2013 00:21:55 - DHT support [ON], port: UDP/31362
11/07/2013 00:21:55 - Anonymous mode [OFF]
11/07/2013 00:21:55 - HTTP user agent is qBittorrent v3.0.10
11/07/2013 00:21:55 - UPnP / NAT-PMP support [ON]
11/07/2013 00:21:55 - qBittorrent is bound to port: TCP/31362
11/07/2013 00:21:55 - Listening on IP address FE80::2CBD:D16E:83A3:49F1%17 on network interface {B551646B-93C4-45AC-891A-B8084EEFCDDA}...
11/07/2013 00:21:55 - Peer ID: -qB30A0-

Even my router shows that UPnP is working fine:

UPnP added entry 255.255.255.255 <-> myIP:31362 <-> 192.168.1.105:31362 TCP timeout:0 'qBittorrent v3.0.10 at 192.168.1.105:31362'

So it should be working, but's it is NOT. Port 31362 is still closed and torrents show up as "stalled" in qBittorrent.

Seems qBitorrent is alone with this issue. All other software on my network that requires a port to be opened or that uses UPnP works just fine.

Does NOT appear to be any firewall blocking it either. After all, you can see the request from qBittorrrent makes it all the way to the router.

Note the messages in RED. So it says within less than a second that it was successful and then failed. Pretty lame!

So then I tried to manually forward a port (tried 5 random ports, and no the ports are NOT already is use), and that fails as well.

Again, only having this issue with qBittorrent.

Thanks for the help,

Will

[loki]

I think something weird is happening within your network... I see IP address 255.255.255.255 what is this?  I'm just guessing here but do you possibly have more than one network interface, if so, try explicitly selecting the proper network in the advanced tab under network interface. Or try each one, checking to see if it solved the issue each time.

Also, seems odd that other upnp programs work fine given this same configuration.

[war59312]

Hi,

255.255.255.255 when it comes to UPnP being reported by a router is normal it seems. Google shows a lot of results.

Besides it is a Subnet mask which would mean all address, iPv4 anyways.

And yes more than one network interface. I tried to set it to the proper network. In fact,when I reported this issue, I failed to mention that I already had in fact done just that.

Indeed, it's odd. But the only viable conclusion I can make at the moment, is that qBittorrent is doing something wrong. Since my router and PC appears to be operating normally (as expected).

Take Care,

Will

[sledgehammer_999]

The failure seems to be related to something else. The mapping to port 31362 succeeded. The one that failed was to another port which is not printed in the log, probably a "null" value that's why it failed. I'll try to take a look at the relevant code.

Listening on IP address FE80::2CBD:D16E:83A3:49F1%17 on network interface {B551646B-93C4-45AC-891A-B8084EEFCDDA}...

Is this IPv6? Funny I thought qbt couldn't handle IPv6 addresses. I guess I was wrong.

[war59312]

Hi,

Could be..

Well I re-downloaded qBittorrent and that line is no longer being logged and it is NOW working as expected.

My modem supports iPv6 but my router does NOT. Perhaps that was breaking it.

Yet, I did NOTHING to turnoff iPv6 to fix this. I simply redownloaded and reinstalled qBittorrent, hope perhaps the download was bad or something.

Appears to be the case since simple reinstalled fixed it. That's all I did. Changed nothing else.

Oh well, looking good now. Working correctly, is all that matters.

Take Care,

Will