Hallo VonEssen, John,
am Mittwoch, 8. Oktober 2003, 20:09:39, schriebst Du:
> 3. Run /your/path/to/cdcc 'info' and make sure it returns a list of
this is the result:
# 10/08/03 20:45:13 CEST /var/dcc/map
# Re-resolve names after 22:19:23
# 196.24 ms threshold, 168.70 ms average12 total, 11
At 01:12 PM 10/8/2003, Jim Knuth wrote:
I wont to know, why DCC not working.
I`ve just installed on my system. ( Debian 3.0 )
The output is:
You won't be able to tell anything about DCC by looking at message headers.
It could just be that the message in question was listed in razor and
pyzor, but
Hallo Matt Kettler,
am Mittwoch, 8. Oktober 2003, 20:13:24, schriebst Du:
> At 01:12 PM 10/8/2003, Jim Knuth wrote:
>>
>>I wont to know, why DCC not working.
>>I`ve just installed on my system. ( Debian 3.0 )
>>The output is:
> You won't be able to tell anything about DCC by looking at message h
Jim,
The obvious things to do are:
1. If you are behind a firewall, make sure proper settings are in place to allow the
DCC communications inbound/outbound on UDP port 6277. There are previous posts about
this as it is extremely important. Incorrect firewall settings cause excessive load on
th