Active mode requires both TCP and UDP access on the same port incoming and all ports outgoing for DC++ to work properly.

If you are NOT behind a router:

•Click on File and then Settings. Click on Connection Settings.
•Select the Direct Connection radio button.  Leave the IP fields blank. This will make DC++ use the current IP assigned to your network card.  You must not have an internal IP address for this to work. 
•Leave the TCP/UDP/TLS ports blank also.  This will make DC++ randomize the port it uses each time.
•Leave the Outgoing Connection settings set to Direct Connection. Click OK.
•You may need to allow DC++ in your built-in or third party made software firewall. Consult its documentation on how to do this.
•Test active mode by joining several hubs and doing a search.  You should get results back.  If not, then you are likely behind a router, have an internal IP address, or haven't properly configured your software firewall.

If you are behind a router:

You can simplify the process of setting up active mode if your router and operating system is UPnP compatible (UPnP is available only on Windows XP and Windows Vista).  For setting up active mode with UPnP or get help how to decide that your router is UPnP compatible or not, please read the How to set up UPnP FAQ. If UPnP does not work or is not an option, follow the steps below.

The second option for using active mode behind a router or a gateway is to set up port forwarding manually. For an in-depth, but still easy to understand explanation of port forwarding, read What is Port Forwarding? The following steps describe the configuration of port forwarding in general. Later you will find links to get configuration information specific to your own router device.

•First you need to set up the router to forward the connections to the computer with DC++. This is could be called port mapping, port redirecting, port forwarding or something like that. Find out how to do this with your router / NAT in the user manual came with your device.
•You need to forward a port for both TCP and UDP protocols. You can use the same port number for both protocol type or different ones for each. Select one or two numbers between 1024 - 65535, they should mostly all be free. Make sure you select the corresponding protocol types (TCP, UDP or Both) when you create port forwarding rule(s).
•The IP that you are forwarding to should be the internal IP address of your DC++ computer. It usually begins with "192.168", "172.16." or "10.x.". To see your internal IP address go to the command prompt and type: ipconfig (Start Menu -> Run -> cmd /k ipconfig).
•When you have mapped the port(s) on the router, in DC++ click on File and then Settings. Click on Connection Settings.
•Select Firewall with manual port forwarding.
•In the TCP/UDP port fields, enter the port(s) number that you are forwarding on the router.
•In the External / WAN IP field, you need to enter the external IP address of your router. This can easily be checked on here.
•Leave the Outgoing Connection settings on Direct Connection. Click OK.
•Active mode should now be working. For checking or troubleshooting if you have properly forwarded the port(s) to DC++, use www.canyouseeme.org. Make sure DC++ is open. Then, from the site, enter in the port you're forwarding and click Check. If everything has been properly set up, the site should say Success. If you get an Error message in red, then you need to double-check the port forwarding on the router, DC++ settings and possibly your software firewall settings.

You may find detailed how-to guides with screen shots for various router models at www.portforward.com. There is a huge list of models there, click on your model name, then select DC++ from the list of applications. An interactive guide will appear to help you how to access your router's configuration page and how to set up port forwarding for DC++. You can find some more how-to's for popular router models at the DSLReport FAQ page as well.

If active mode is working for a while, but the next time when you use DC++, you only get Connection Timeouts or no results when searching, your IP (either external or internal) is likely to have changed. Of course you can update your IP settings manually each time they changed, but there are better solutions to avoid constant IP address updates:

•If you find the external IP is constantly changing, you can sign up to a free dynamic DNS service such as No-IP , Dynip or DynDns and put your dynamic DNS address into the External / WAN IP field in DC++ Connection Settings. Each DDNS provider has a downloadable IP updater software what updates the dynamic name service with your latest IP. Make sure you download, configure and run this program while using DC++. Many router models have DDNS client software included for specific DDNS provider(s) so it worth a check in your router configurations before choosing a provider. After you setup the built-in DDNS client you won't need to run any IP updater software, your router will automatically take care of updating your DNS name.
•If you find that your internal IP changes when you restart your computer then your operating system is obtaining an IP address from your router at boot using DHCP protocol. If you want your computer to always have the same internal IP address you must setup Static DHCP in your router configuration. Static DHCP is a useful feature which makes your router always assign the same IP address to a specific computer on your network. You will have to find MAC address of your network card to set up Static DHCP.
Another option to ensure you'll always have the same internal IP address is to set up static IP address for your computer. Here's a FAQ how to do this for different versions of Windows.

For Linux based firewalls/routers, take a look at this FAQ on this subject.

•Alcatel SpeedTouch 510
•D-Link DI-604 / DI-704
•D-Link DI-804
•D-Link (all other models)
•Linksys (many models)
•Netgear DG814, RP614, RP614v2, MR814, MR814v2, WGT624
•Netgear RM356, RH340, RH348, RT388, RT311, RT314
•Netgear (all other models)
•ZyXEL Prestige 310 / 314
•All other models not listed here

Besides normal file transfers DC++ is capable of secure (SSL encrypted) way of receiving and transmitting files on ADC hubs. If you plan (or required) to use this feature and you use DC++ in active mode with manual port forwarding you should forward one more port for SSL handshake. You must choose and forward another free port between 1024 - 65535 for TLS which is different than the one(s) you use for TCP and UDP. In the port forwarding rule you should set the protocol type to TCP or Both for the TLS port. Finally you must put the port number to the TLS field in Incoming connections settings of DC++ to be able to download from users who have secure transfers enabled.

Windows XP?

•Service Pack 1: Its strongly recommended that you do not use the SP1 firewall and instead use a third party one.  Make sure to disable the XP firewall if you do choose this option.  If you really must use it, then checkout this guide on how to set it up.  Remember you need both TCP & UDP.
 
•Service Pack 2 & 3: The firewall in SP2 & SP3 is a lot more robust than its original incarnation.  While it does not offer a plethora of options, its suitable to use by itself for protection.  Its wise to enable logging of packets that the firewall drops for troubleshooting applications.  To do this, go to Control Panels -> Windows Firewall -> Advanced Tab -> Security Logging -> Settings.  Enable Log Dropped Packets.  The log file is located at  C:\WINDOWS\pfirewall.log. Here's a complete guide How to Configure Windows Firewall on Windows XP SP2 & SP3.

DC++ Changelog Related Entries:
0.700: Files from passive users queued even when passive (in the hopes of finding an alternative source)
0.691: Passive users now also get ADC search results
0.68: No longer falls back to passive mode on failed UPnP
0.667: Fixed passive search results issue with international nicks (thanks garg)
0.4033: Added UPnP support (thanks mark gillespie)
0.305:  Added support for $UserIP, %[ip] as user command parameter and server side IP detection (automatically used if the IP field in settings is blank)
0.242:  Fixed problems with changing active port
0.21:  Fixed port changing bug (DC++ would still listen to the old port until restarted)
0.20:  A random free port between 1025 and 32000 is now used in active mode, unless a port specifically has been set.
0.16:  Changed default port to 1412, should improve compatibility with a lot of firewalls
0.03:  New settings, including passive mode and active port selection

feedback form

feedback form

Any feedback you provide (corrections, updates or suggestions) are sent to the owner of this FAQ
and anyone else involved in writing or editing this item.

by USR56K edited by eMTee
last modified: 2009-08-10 16:00:35