UPNP failed to create port mappings stopped working

What happens if you enable 'Automatic connection detection' ?

With "Enable Automatic incoming connection type detection" checked off, I click Detect now and I get this:

Determining connection type...
Public IP address detected, selecting active mode with direct connection

It just stays that way after 5+ minutes.

Is it possible that you have more than one network devices in your computer? If so, make sure DC++ accessing the Internet through that router by explicitly setting the bind address of the correct network interface.

Hi eMTee,

You are completely right! I use VPN Software called Logmein Hamachi that sets up virtual network devices on my computer and it interfered with DC++'s auto UPnP mappings. If I disable the network devices in my Window's device settings, DC++ works perfectly fine and I get this message:

"UPnP: Successfully created port mappings (TCP: 58913, UDP: 61715, TLS: 58914), mapped using the MiniUPnP interface"

However, could you please help me out with which IP address to bind so that I do not have to disable the Hamachi devices every time I use DC++? I use Hamachi fairly often for work and it would be great if I could leave it on all the time. I tried all of the addresses I thought would work in the binding setting, but none of them work. I get the message shown below for each of them (except the TCP port varies). Below is a list of the IP addresses I have tried binding.

UPnP: The MiniUPnP interface has failed to map the TCP 58356 port
UPnP: Failed to initalize the Standard Windows interface
UPnP: Failed to create port mappings

List of Bindings:
- 0.0.0.0 (Default)
- External/WAN IP (from http://www.whatismyip.com/)
- IPv4 Address, Subnet Mask, DNS Address, and Default Gateway (from command prompt under Ethernet Adapter Local Area Connection)
- IPv4 Address, Subnet Mask, DNS Address, and Default Gateway (from the WAN configurations page on my router that runs tomato)

Thank you very much for your helpful and prompt responses so far! I am glad that I at least know a work around to get DC++ up and running now.

- Chris

Of course, you have to bind all DC++ socket operations to your physical Ethernet adapter. You have to put the adapter's local IP address to the Bind Address box in Settings/Experts Only panel.

(If your adapter obtains the local IP address from the router via DHCP then you'd better set up a static DHCP or a fix local IP address for your adapter before.)

I can see why I would need to set a static DHCP or Fixed IP address, but would you mind elaborating on what it takes to bind DC++ socket operations to my Ethernet Adapter? Is this process similar to changing the priorities in which my computer chooses an Ethernet adapter? I know where to bind my main Ip address, but I do not know what you mean by binding DC socket operations to my adapter. Sorry for all the questions, Thanks!

- Chris

>what it takes to bind DC++ socket operations to my Ethernet Adapter?
You have to put the adapter's local IP address to the Bind Address box what can be found in DC++ Settings / Experts Only panel.

>Is this process similar to changing the priorities in which my computer chooses an Ethernet adapter?
Yes. But in this case its a fix binding to make sure DC++ uses the Ethernet adapter always

>I can see why I would need to set a static DHCP or Fixed IP address,
To avoid putting the always changing IP address to the bind address setting every time you restart your computer.