Setting up Direct Connect - P2P File Sharing ++ (http://dcplusplus.sourceforge.net/)

Configuration guide for n00bies

Page written by MadEng (ineer), for the private New Zealand Direct Connect P2P hub scene.

Introduction

I had helped half a dozen individuals set up their client so that they are not restricted to passive (PASV) mode - due to difficulties caused by a firewall or other NAT device (i.e. router/gateway). I wrote this page because repeating yourself isn't a lot of fun -- I was always repeating the exact same solutions.

An alternative if you can't seem to get things working is to use Passive mode.  When using PASV mode, other PASV users cannot connect to you, and you cannot connect to them.  This isn't too big an issue - last time I checked, out of 800 users 16 percent were connected this way.  However, it may become a problem for you if the one file you are after is hosted by a PASV user.  You are also contributing just that little bit more towards the NZDC hub by allowing PASV users to connect to you.

What is passive mode?  (Note: This brief explanation is taken from how FTP transfers work - I've only provided this here for the curious.)  Normally, in active mode, a client requesting a file will communicate with the server from a random port.  It then opens [random port +1] for receiving traffic back from the server.  If you are behind a NAT device (router), this process is broken by the fact that your router will not forward incoming data on that random port.  With passive mode, the server decides on the random port, rather than the client.  (Hopefully that is somewhat correct!)  See: http://slacksite.com/other/ftp.html.

Outline

There are a few basic steps you need to go through.  Skim read the following if you're a n00b.  Non-n00b type people could use the following to quickly get setup:

• Check what port that your Direct Connect client is using.  This is found under settings.  It may be 412, or 1412. I have used ports 612 because I like to be different.  Actually it's for security reasons, and in case someone else on the LAN happens to use this software.
• "Pin Hole" or open BOTH ports 612 UDP and 612 TCP on your router/firewall/whatever.
• Find your WAN IP address and enter it into the DC client settings.

You should be good to go. If you get results from file searches, you are probably up and running.

(Upgrading your client to 0.20 will clear your entry for 'port', making it 'Random'.  Be sure to re-enter your port number)

Detailed Help

Figure 1 - DC++ Client Settings

Figure 2 - Router Settings. Example is from a Dynalink RTA020 router. For the TCP port. An example for the UDP port can be found here.  RTA210 has the same interface.  RTA220 example of the TCP port here.  Example of both ports here.

Explanation:

It would be wise to read the manual for your hardware.  At least read over it so you are familiar with it.

In Figure 1 you can see my entry for 612. It is up to you what the port is, just remember what port you use. Notice the IP entry. I have joined up with the no-ip service.  This allows me to "set and forget" the IP address, otherwise every time my ISP changes my IP address, I would have to enter a new one.  The IP address you need to enter is referred to as your WAN IP address.  There are several ways to find it - try www.whatismyipaddress.com.  Be aware that those IP reporters may simply give your proxy IP address.  Your router should provide you with the correct IP.  With the Dynalink RTA020 it can be found in its web-based control panel under Status, Connection, ATM PVC.  Connecting to an IRC server will also report it.

Figure 2 shows how I have configured my router to re-direct incoming data on port TCP-612 to my machine, which sits at 192.168.1.3. Don't forget to also add the UDP port! 

More Help

You should be able to get results for file searches now.  Try downloading a few files.  Some people may already be retrieving your file list.  You do have at least a few gigs of data shared, right?!

Ask someone for help.  Most people are willing to lend a hand.

There are a few things you can do yourself, like check the following points:

• Correct port entered into the router (pinhole or virtual server).
• Matching port in client settings.
• Correct IP address entered into client settings.  Double check it by pinging it.  Try resolving it to make sure its not an ISP's proxy.
• Try double-checking what port the client is using by typing "netstat" (or "netstat -a") in a command prompt window.  Look for your port number.  If you can't find it there, try looking for a port that is listed twice: one UDP the other TCP.
• Using a firewall such as the one built into XP?  Before shutting down the XP firewall, install Zonealarm.  If you use an external router you can do away with a personal-firewall, otherwise if you connect to the net with a modem, you will be open directly to the internet.  Contact me on ICQ if you want me to test/demonstrate this for you.  After installing and running Zonealarm, give DCPP server rights.  I also suggest momentarily running with no firewall if you still have problems.  If Zonealarm turns out to be preventing transfers, you will need to manually configure ZA to unblock the ports you have used, AND ports 1024 to 65535 outgoing.

Further Help and links: NZGames.com Forums -  Try posting a question in the Techno. & Trouble. thread.

Dynalink (New Zealand) web page - firmware updates, online manuals, support.

Orcon ISP and hosting - The kind folks that house the said hub.

I hope this page was of use.  Comments are welcome.  For contact, I'd prefer that you sent me a message via ICQ (number found elsewhere on this page - add me first because I may not receive messages from those not on my list).  You can even talk to me in the hub chat if I'm online.  Thanks to those spreading word of this page.

 hits since August 2002

Thanks to http://webbiznz.co.nz/ for hosting the above PHP hit counter.