UPnP not working with BitComet 1.17 in Win7

[jonquilmcd]

I'm using BitComet 1.17 with Windows 7 and a Netgear Wireless N 300 router. When I try using BitComet with UPnP it does not work (yellow connection indicator and no port is ever opened in the UPnP settings on the router GUI). I have ensured that UPnP is enabled in BitComet, the service is running in Windows, and that it is enabled in the router GUI as well. No other programs have issues using UPnP, and the indicator goes green in BitComet if I manually forward the port it uses in the router GUI. Is this a known bug in BitComet or is there something else I can do to get UPnP to work with it?

[The UnUsual Suspect]

uPnP is nice when it works, but it's almost always more work to diagnose then to simply open the port manually. The problem is that there is no standards that all router manufacturers use, making uPnP neither universal, nor plug n play.

However, we have a great tech support team here, so maybe one of our guys, or the development team know more about Netgear routers then I do. I suggest you provide the model number and firmware just in case its needed, and you seem to be capable, but just to be through, have you opened the port that uPnP uses in any software firewalls you may be using?

[kluelos]

There is probably nothing you can do. UPnP for router control has always been a very chancy proposition. When it goes wrong, as it does here, you can't diagnose the problem and you can't fix it. If UPnP doesn't work for you, the only effective alternative has been to just abandon it, turn it all off and configure your router manually. Fortunately, that isn't so difficult.

Most manuals make this seem far harder than it actually is. There's a big intimidation factor, but the actual task is bog-simple. Take a look in our Guides forum, there is a whole topic devoted to this subject, with lots of handholding through many variants.

[bugmenot1]

hello,

sorry for updating this old topic. i've figured out what's wrong with bitcomet, or is it? i'm using 1.33 64 bit and its not working. utorrent was redirecting. transmission under linux was not. the problem is some routers i think adsl are not reporting connection status. i once used a tool to check this, and status was unknown while informing of current upload and download speed. utorrent is blindly sending request, while others with proper upnp implantation first ask for connection status or look for device which says "i'm connected". bitcomet and transmission report "no upnp device found". if developers could implant this dummy upnp function perhaps as option to choose, we would have easier life

Edited September 14, 2012 by bugmenot1 (see edit history)

[The UnUsual Suspect]

hello,

sorry for updating this old topic. i've figured out what's wrong with bitcomet, or is it? i'm using 1.33 64 bit and its not working. utorrent was redirecting. transmission under linux was not. the problem is some routers i think adsl are not reporting connection status. i once used a tool to check this, and status was unknown while informing of current upload and download speed. utorrent is blindly sending request, while others with proper upnp implantation first ask for connection status or look for device which says "i'm connected". bitcomet and transmission report "no upnp device found". if developers could implant this dummy upnp function perhaps as option to choose, we would have easier life

If you want to prepare a report on this I'll deliver it to development, but please provide all of what it is/isn't doing and what you feel it should be doing, and most important, be very clear so the report survives translation... no slang, proper grammar/spelling.

Also, please register your own account in case we need to contact you regarding it, our forum is open to all so there is no need to use an anonymous account.