Comment 31 for bug 230973

Oh my god. I'm so happy. If any developers read this, just consider it a big rose. Situation's like this. For as long as I can remember (since initial DC++ release probably) the UPnP has not been working properly in Windoze XP. It looks like some people has had it working, so I guess there could be some issue with my particular router. I've always had D-Link routers (mainly the DIR series). Anyways, the UPnP has never worked properly.

A couple of years ago, I found out that DC++ had has spin-offs (i.e. StrongDC/ApexDC). I was delighted, and hopeful, perhaps these "new" clients had taken care of this issue. Unfortunately, the not working UPnP remained a fact, although I still chose to stick with ApexDC++ ever since I discovered it, since it's simply the best in terms of functionability and user interface. However, it still struck me as weird, this thing with UPnP. Other software worked fine with UPnP, eg. Utorrent. I still ran the known Windows app "upnptest.exe" (and its sequel "upnptest2.exe" aswell), just to make sure everything was fine. It was, but DC clients still wouldn't catch UPnP port redirection.

Now, I At one time, I seemed to manage to pin-point the issue. I went into "Network Connections" (ncpa.cpl) / "Internet Connection" / Properties / Settings, to see how the redirection list looked like after having launched DC/StrongDC/ApexDC. The pattern was consistent for all these DC++ clients. Whereas Utorrent (which worked correctly) had forwarded its desired port to LAN IP of my actual machine (eg. 192.168.0.123), the DC forwardings simply pointed at "127.0.0.1". I then tried manually changing 127.0.0.1 (loopback IP) for my actual LAN IP, and voila, suddenly it worked like a charm. However, every time I restarted ApexDC/StrongDC/DC, it would "reattach" to stupid loopback IP, so the procedure was more or less useless.

Now, I havn't been using DC for a while. So, the other day I downloaded and installed ApexDC v1.3.5, and just by curiosity I chose "UPnP" for connection mode. It worked! And now when I look in the ncpa.cpl it lists my actual LAN IP, not the loopback IP. I'm so delighted, looks like it finally works. As I see it, there are two possibilities here. Either the failure has lied within Windows XP operating system, and thus it has been fixed by any of the Windows hotfixes that I automatically install whenever possible, _or_ the issue has actually lied within the DC core, and has thus been (quite recently) been patched.

Either ways, I'm really happy!

Cheers!
..and thanks for supplying the best DC++ client ever!