no valid upnp igds found

[vayvanne]

Hi folks. Why bitcoind v0.15.0.1 can say "no valid upnp IGDs found" and respectively do not map the 8333 port on a router?
I am certain that the router actually does support UPnP and it does work for other software like skype, utorrent etc. I can even map a port manually via windows explorer. But no luck with bitcoin. It's certainly not the firewall issue, I checked many times that UPnP and SSDP ports are open.
What else it can be?
Thanks for hints in advance.

[cr1776]

Can you try disabling the firewall and trying it?  (Or trying it in safe mode and see if it is the same?)

See: https://bitcointalk.org/index.php?topic=2135851.msg%msg_id%

[vayvanne]

Can you try disabling the firewall and trying it?  (Or trying it in safe mode and see if it is the same?)

See: https://bitcointalk.org/index.php?topic=2135851.msg%msg_id%

It does not help. Looks like it is kind of incompatibility with the router which is D-link DSL-3782. Prior to replacement I had Huawei HG633 where it did work but inconsistently. Would not like to make port forwarding knowing that UPnP should work.

[vayvanne]

upnpc-shared -a 192.168.1.199 8333 8333 tcp

upnpc : miniupnpc library test client, version 1.9.
 (c) 2005-2014 Thomas Bernard.
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
 desc: http://192.168.1.254:5555/DeviceDescription.xml
 st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://192.168.1.254:5555/UD/?9
Local LAN ip address : 192.168.1.199
ExternalIPAddress = 0.0.0.0
InternalIP:Port = 192.168.1.199:8333
external 0.0.0.0:8333 TCP is redirected to internal 192.168.1.199:8333 (duration=0)

bitcoin upnp on the same host machine still does not work. what version of miniupnpc lib is used in it?