·Any websites to help me set DC++ up?
·Can I import my NMDC queue into DC++?
·How to share network drives
·Why do I need active mode?
·How to set up active mode?
·How to set up active mode with ICS?
·How do I set up active mode with a Linux based firewall/router?
·How to set up active mode on FreeBSD
·How to set up UPnP?
·What ports does DC++ use?
·How do I log on as a registered user / OP?
·Alternative hublists?
·My university blocks DC++, anything I can do about it?

•DC++ Guide
The following is a great guide with plenty of pictures on how to do basic setup of DC++, written by TheParanoidOne.
 
• DCNet.be.
A guide written in Dutch

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
last modified: 2009-01-01 21:51:26

Depends on the DC++ version.

Clients newer than 0.4032 cannot.

Clients older than 0.4032 can. Go to File -> Import NMDC queue and browse to your NMDC directory and select queue.config.

DC++ Changelog Related Entries:
0.4032: Removed obsolete Import from NMDC queue (blame cologic)
0.163: Added NMDC queue importing (thanks, luca rota)

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 JMGullett
last modified: 2007-01-29 15:01:29

DC++ 0.4032 or newer

DC++ clients after 0.4032 are able to successfully share network drives from within DC++ with out mapping them.

•Go to File -> Settings -> Sharing -> Add Folder
•Navigate through your home network to the computer with a share and select one.
 
 
•Now you should see it listed as a shared folder in DC++


 

DC++ 0.305 to 0.403

DC++ clients 0.305 to 0.403 support sharing networked drives via their UNC name (i.e. \\servername\share), but the GUI does not have the option to navigate through My Network Places entirely.  This leaves two methods to sharing a network drive:

•Follow the method below in the next section for older DC++ clients.
•Edit your DCPlusPlus.xml file and add the UNC path for a share.
<Share>
        <Directory>F:\My Music</Directory>
        <Directory>\\somecomputer\share</Directory>
</Share>
 

DC++ 0.304 or older

NeoModus Direct Connect nor DC++ will allow you to directly share a network drive.  However, there is a solution to sharing them!

Simply map a network drive to a drive letter in windows (i.e. Z:\share). Once the network drive has been mapped to a drive letter, you can share it in NMDC or DC++ like a normal folder.

•Open up Windows Explorer or My Computer.  Go to Tools -> Map Network Drive

 
•Type in the computer name and the share point (or browse to it).  You might need to specify a different username when connecting to the computer.  Click on "different user name" and enter in the name/password.

 
•Inside DC++ sharing setting, select the drive you just mapped (Z: in this example).  That's it!
 

DC++ Changelog Related Entries:
0.4032:  Allowed sharing of network folders (thanks, garg)
0.306:  Fixed an issue with UNC paths (those starting with "\\")

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 JMGullett
last modified: 2007-01-29 15:06:09

In passive connection mode, DC++ will only make outbound connections to other users. All searches will be sent through the hub, and search results will be returned through the hub as well. DC++ will return a maximum of 5 search hits for a passive user. Passive users cannot download from other passive users. Passive mode is an extra strain on hubs, so please do not use it unless you must. To find out what DC++ users are in passive mode in a hub check their tag in the list of users. Passive users will have M:P in their DC++ tag.

That being said, active mode on DC++ will make inbound and outbound connections to other users. While all searches will be sent through the hub, search results will be returned directly from active mode users and through the hub for the passive users. Active users can download from either active and passive users and get more search results. Obviously that means you can connect to a larger group of people.

However, there is ZERO difference in download/upload speed between active or passive modes.

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
last modified: 2008-07-01 04:18:33

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

Part 1 - Installing ICS on the operating system

    Windows 98: Followthis guide from PracticallyNetworked.
    Windows ME: Followthis guide from PracticallyNetworked.
    Windows 2000: Followthis guide from PracticallyNetworked. 
    Windows XP:Followthis gude from PracticallyNetworked.

Part 2 - Port Forwarding

* For Windows 98/ME clients, it would be easier to use the ICS Configuration tool.  Once installed, follow the outline to this guide on how to set it up (although it won't look the same).
 

•Get properties on the network card that is directly connected to the Internet.

Make sure the firewall is disabled.  Click on Settings.
 
•Click on Add. 

 
•You will need to create two new services, one for TCP and the other for UDP.

This one will be for TCP.  Enter in the IP address of the computer that's attached.  It should be using a IP address that begins with 192.168.xxx.xxx.  To find out what it is on the attached computer, (Win 9x: Start > Run > winipcfg | Win 2k/XP: Start > Run > "cmd /k ipconfig" [without the ""]).  Pick any port between 1024 and 65535.  Enter this into both the External Port field and Internal Port field.  Lets say you choose port 40500, for example. 
 
•Use the exact same numbers from above, except select the UDP radio button.

 
•In DC++, go to File -> Settings.

Enter in your external IP address, which can be found here.  Use the same port you set up in the new service you created. 
 
•DC++ should now work in active mode!

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 JMGullett
last modified: 2007-01-29 16:01:06

It depends on what kernel version you are using. With 2.4 you can choose between doing postrouting or the easier prerouting. The difference is if you do a postrouting, all clients within your internal network (LAN) can connect and download/upload between each other. Postrouting is not necessary if you are the only client which uses DC behind the router/firewall. The examples below use the following settings: External Ethernet card: eth1, external IP 213.112.8.55, firewall (router) IP: 192.168.0.1, client IP: 192.168.0.2, external and internal port: 555

Linux 2.4, postrouting example

iptables -t nat -A POSTROUTING -d 192.168.0.2 -s 192.168.0.0/24 -p tcp --dport 555 -j SNAT --to 192.168.10.1

iptables -t nat -A POSTROUTING -d 192.168.0.2 -s 192.168.0.0/24 -p udp --dport 555 -j SNAT --to 192.168.10.1

iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 555 -j DNAT --to 192.168.10.2:555

iptables -t nat -A PREROUTING -i eth1 -p udp --dport 555 -j DNAT --to 192.168.10.2:555

iptables -t nat -A PREROUTING -d 213.112.8.55 -p tcp --dport 555 -j DNAT --to 192.168.10.2:555

iptables -t nat -A PREROUTING -d 213.112.8.55 -p udp --dport 555 -j DNAT --to 192.168.10.2:555

Linux 2.4, prerouting example

iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 555 -j DNAT --to 192.168.0.2:555

iptables -t nat -A PREROUTING -i eth1 -p udp --dport 555 -j DNAT --to 192.168.0.2:555

Linux 2.2, example

ipmasqadm portfw -a -P tcp -L 213.112.8.55 555 -R 192.168.0.2 555

ipmasqadm portfw -a -P udp -L 213.112.8.55 555 -R 192.168.0.2 555

Submitted by tajisen

How to use Shorewall to configure your iptables

Here's what you have to add to rules (assuming loc is the zone where your computer is located, 192.168.0.7 is your computer's IP, 666 is the port you wish to use and 123.45.67.89 is your external IP):

#ACTION

SOURCE

DEST

PROTO

DEST PORT

SOURCE PORT(S)

ORIGINAL DEST

DNAT

net

loc:192.168.0.7

tcp

123.45.67.89

DNAT

net

loc:192.168.0.7

123.45.67.89

Submitted by Ender

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 JMGullett
last modified: 2007-01-29 16:02:51

•Edit your ipfw rules list (usually something like /etc/rc.ipfw) . In there somewhere, you should have a rule that diverts all traffic to natd, which should look something like:
${fwcmd} add divert natd all from any to any via ${natd_interface}
•Below this, add as your next rule:
# Direct Connect Active Mode Port Forwarding
${fwcmd} add pass all from any to any 1776 via ${oif}
${fwcmd} add pass all from any to any 1776 via ${iif}
•For "1776," replace any port (preferably something above 1000) that you would like as your forwarded port. Save and close /etc/rc.ipfw.
•Next open up your /etc/natd.conf file. Make sure the top line has your interface listed (replace "de0" with whatever your outside interface is):
interface de0
•Then add the following two lines at the end:
redirect_port tcp 192.168.70.2:1776 1776
redirect_port udp 192.168.70.2:1776 1776
•For 192.168.70.2, substitute the internal IP of your machine running DC++. For "1776," substitute whichever port you used above in your /etc/rc.ipfw file.
•Finally, we need to reset ipfw and also natd.
Type: ps aux | grep natd
•Find the process # for natd. Now we need to kill the process and restart it:
Type: kill -9 && natd -f /etc/natd.conf
•Last step, time to reset ipfw to make sure our traffic gets through:
/sbin/ipfw -f flush
/bin/sh /etc/rc.ipfw

Submitted by SeeKay303

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 JMGullett
last modified: 2007-01-29 16:11:23

Universal Plug And Play (UPnP) is a technology to allow, among other things, Internet applications to configure home routers and gateways, bypassing manual port forwarding configuration. UPnP was introduced in Windows XP and is supported in that and later versions, including Windows Server 2003 and Vista. To take advantage of UPnP, you must have support enabled in Windows and UPnP capable hardware (typically a broadband router using NAT traversal). If you meet both of these requirements, setting up DC++ is normally a simple process. UPnP support introduced in DC++ 0.4033. For using DC++ with UPnP under Vista you need version 0.695 or newer.

To enable UPnP:

•Click on the File menu and then Settings. Click on Connection Settings.
•Select Firewall with UPnP.
•Restart DC++.

If your UPnP system is setup correctly, DC++ will now automatically create the required port mappings for DC++ to operate in Active Mode. It will also detect your external IP address and switch into Active Mode.

Troubleshooting:

If you are having trouble getting this all to work (or see messages in the DC++ System Log like "Failed To Create Port Mappings"), and you are sure you meet the minimum requirements mentioned above, firstly, download a UPnP diagnostic tool. The recommended one is Mark Gillespie's UPnP test tool. This program will tell you what network interfaces on your computer support UPnP.

Alternatively, to test your UPnP functionality, you can run the web based Internet Connectivity Evaluation Tool from Microsoft. This tool is avaliable only for Windows XP and Vista and requires IE6 or later to run.

If your router fails the UPnP test(s), then it's doubtful DC++ will function properly with UPnP either. If none of your network interfaces are reporting UPnP capabilities, try the following suggestions:

•Ensure your UPnP hardware has the UPnP service switched on (some routers default to off), consult your manufacturers documentation.

•Ensure Windows UPnP services (Control Panels -> Admin Tools -> Services) are running. "Universal Plug and Play Device Host" and "SSDP Discovery Service". Both of these XP services should be set to "Automatic" startup and "Started" status:

•Switch on the UPnP User Interface. To do this: Open "My Network Places", and in the Network Tasks Panel, select Show icons for networked UPnP devices.

If UPnP is working, you should see your routers name in My Network Places:


Also, when you go to: Start | Settings | Network Connections, you should see Internet Connection listed under the Internet Gateway category.



•Reboot both your PC and your UPnP device (router).

•If you do not see your router as a network device in "My Network Places" after several minutes, UPnPTest will fail to create an UPnP mapping to the router, resulting in something looking like: INFO: Adapter #0 - 192.168.8.17 - UPnP Disabled. Make sure the windows firewall or your third party firewall is not blocking UPnP packets.

Windows XP Firewall:
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 If you see any packets being dropped with the port 1900 or 2869, the the firewall is misconfigured and is preventing UPnP from working.

Third Party Firewall:
Checking this setting varies widely between firewalls. Most decent firewalls have some sort of logging function, where one can see what the firewall is blocking. Look for "UPnP" or ports 1900 and 2869 and refer the firewall's manual how to ublock.


•If the diagnostic tool is now still not reporting any UPnP devices, you should start considering more drastic actions like upgrading your router firmware, as many routers have UPnP implementation bugs.

If your router still fails the UPnP test follow the guide on Manual port forwarding to be able to use DC++ in active mode.

Initial content submitted by mgillespie

DC++ Change Log Related Entries:
0.68: No longer fallbacks to passive mode on failed UPnP.
0.670: Some UPnP fixes (thanks nils maier); Hopefully fixed an UPnP crash.
0.669: Hopefully fixed an UPnP crash
0.666: Fixed a crash in the upnp code
0.4033: Added UPnP support (thanks mark gillespie)

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
last modified: 2008-07-01 04:54:16

Outbound:

Inbound:

DC++ Change Log Related Entries:
0.668: Added option to use separate TCP and UDP ports.
0.20: A random free port between 1025 and 32000 is now used in active mode, unless a port has been specifically set. This port is changed on every restart to avoid problems with networks where traffic on certain ports is limited or banned.

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 JMGullett
last modified: 2007-01-30 10:32:08

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 JMGullett
last modified: 2007-01-30 10:33:43

Instructions:
To use another hub list, open up File -> Settings -> Downloads. Click on Configure Public Hub Lists.  Paste in another hub list and click Add.  DC++ will try each hub list listed, starting with the one at the top.

Here is a list of popular hub lists in use today:

Legacy DC++ (Pre 0.4033):
To use another hub list, open up File -> Settings ->.Downloads.  Replace the "Public hub list URL" at the bottom.  Place a semicolon between each hub list.

If none of these work in DC++, try pasting a link into your browser.  If a file does download, then you have some sort of firewall blocking DC++ specifically.  If nothing downloads, then a firewall is blocking all your internet traffic to that site or the list is down.

DC++ Changelog Related Entries:
0.704: Hub lists added to utilize Coral's distributed network (ullner); Fixed clicking in the header of the favorite hubs list view (poy)
0.700: [bug 1144] Added possibility to add many hub lists in one go (use ; as separator) (thanks poy)
0.699: [bug 1110] Added new adc hub list (thanks mafa_45); [bug 1091] Added new nmdc hub lists (thanks poy); [bug 446] Public hub lists are cached and downloaded only when user requests it (thanks poy)
0.695: Default hub lists updated
0.692: Added warning when someone tries to spam hublist.org or dcpp.net with your client
0.688: [bug 345] Fixed an xml listing parsing bug
0.685: Added advanced hublist filter (thanks trem)
0.667: Improved multiple hublist support (thanks garg)
0.4033:  Added (initial) support for hublist.org xml hublists
0.402:  Copy address to clipboard from public hub list (thanks joakim tosteberg)
0.305:  Really fixed hublist space trimming =).   Added accelerator for filtering in public hubs (thanks gargoyle)
0.304:  Fixed trimming of spaces for http downloads (hub list...)
0.26:  Default hub list now points to one that works
0.25:  Fixed public hub list mouse clicks and reopening (thanks todd)
0.241:  Fixed error reporting for hublist download
0.233:  Fixed another thing with hub lists being unnecessarily downloaded (thanks todd pederzani)
0.23:  Hublist is no longer loaded in the background by default when starting the application.  Fixed some proxy connection problems for the hublist (thanks Ondrea (or is it Ondra or Ondrej? =)).   Disabled automatic opening of the hublist.  
0.181:  Fixed a bug with bad hublist server names (empty ones, not starting with http://...)
0.174:  Fixed some minor hublist bugs
0.172:  Added support for bzip2-compressed hub list downloading
0.17:  Removed the public hublist multi-select feature
0.163:  Added public hublist filter.  Changed error messages in public hubs frame.   Added proxy support for downloading the hub list.  Fixed a crash when loading invalid hub lists
0.12:  Added right-button menu to Public Hubs
0.11:  Public hubs automatically appears on startup
0.03:  Hub list sorting.
0.01:  List hubs, connect to them and chat

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
last modified: 2009-01-26 19:24:43

Unfortunately, probably not. The majority of schools have moved over to a solution from Packeteer or a similar company. This software/hardware solution has the ability to look into a TCP packet, decode the application layer data and then throttle/block accordingly.

There could be a way to get around this, but it's no easy task. It would involve setting up a host off campus which is not influenced by the schools packet shaping. Then setting up a tunnel (socks, proxy, ssh, vpn, etc) and routing all your DC++ traffic through it. It will still be affected by the schools packet shaping, but there is a chance the tunnel you created has a higher priority/larger pipe than the P2P one.

Some schools might have their network behind a NAT, in which case you are SOL for an active connection. Furthermore, if this is the case, then they have full control over connections, and there isn’t anything you can do.  Try passive mode and cross your fingers.

A few schools just use simple port blocking. DC++ automatically uses a wide range of ports for outgoing traffic to help bypass port blocking.  If the school is smart enough to block port 411 outgoing connections, then you are pretty much SOL since that is the port most hubs use. One could try to connect to a hub that uses an alternative port (i.e. myhub.kicks-ass.net:2385). Once again, you could possibly set up a tunnel or port mapping, but those are complicated solutions that not many can achieve (and out of the scope of this FAQ).

A solution which might work is to use a proxy program/service to bypass their firewall, such as HTTP-tunnel or Hopster.

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 JMGullett
last modified: 2007-01-30 10:38:58