PDA

View Full Version : Direct Connect hasnt connected me yet


NDGAARONDI
December 28th, 2002, 05:56 PM
I'm having trouble connecting and I've configured it right.

Does it work when you have a firewall active (to prevent DoS etc.)?

Anyone uses/used it so they can help me please?

Hope some1 can help.
Rickio
December 28th, 2002, 06:01 PM
Originally posted by NDGAARONDI
I'm having trouble connecting and I've configured it right.

Does it work when you have a firewall active (to prevent DoS etc.)?

Anyone uses/used it so they can help me please?

Hope some1 can help.

any p2p you use must be allowed through the firewall.

so give it permission.

peace
InspectorGadget
December 28th, 2002, 06:21 PM
direct connect requires by default tcp port 412 and udp port 412 for file transfers and searches (1412 tcp and udp for dc++) and I believe the actual connection to the hubs is done over port 411 tcp on both clients

on the other hand if you're completely new to dc it's not a network that "just connects" like kazaa, you have to manually select servers to connect to from the list you download when opening dc
Wolfie
December 28th, 2002, 06:21 PM
You can still connect to DC with firewall but it's passive connection which means you can't connect to another person on DC that are behind themselves. For that
What you need to do is figure out what ports the program is using and open those ports on your firewall. Check out the FAQ on this link:

http://www.neo-modus.com/?page=Help
notbob
December 28th, 2002, 06:42 PM
you can use dc on any port you want--412 is the default, but 21 is pretty foolproof, the new dc++ have it set to any random port

411 needs to be open in the firewall for hub related stuff i think
Wolfie
December 28th, 2002, 06:50 PM
Yep, DC++ needs the 411 port. I had set that up last week on my router firewall.
NDGAARONDI
December 28th, 2002, 06:54 PM
Thanks, I'm new to DC but not others like AG and Kazaa.

I gave my firewall permission to allow DC to connect though
method
December 28th, 2002, 07:33 PM
it's a shame there aren't more hubs on ports 21, 80, 443, and 8080... it'd help a lot of harshly firewalled users..

and here it is ... i'm gonna spill the fukin beans...

Using port 443 for connections is one of the two ways to get around PacketShaper... and that IS hot info for packetshaper people... i'm saying no more.

Peace!!