[03:51] -mhm- Failed to connect (Connection refused)

divine · Post by **divine** » Fri Apr 11, 2003 8:59 pm

hello
i know that this quesition has been answered long ago but i tried everything and i can't deal with the problem.

the eggy is runnin on an openbsd box with a NAT:

external ip -> 217.18.246.224
local ip -> 10.10.10.1
i'm commin from -> 10.10.10.10

i've set:
my-ip -> 10.10.10.1
nat-ip -> 217.18.246.224

i can connect with the bot over telnet but when i try to connect using /dcc chat mhm ( botnick = mhm) i get a notice :

[03:51] -mhm- Failed to connect (Connection refused)

and in the partyline (telnet) i get:

Code: Select all

[03:51] <mhm> [03:52] DCC connection failed: CHAT (Divine!~2lam34u@217-18-246-224.cablebg.net)
[03:51] <mhm> [03:52]     (Connection refused)
[03:51] <mhm> [03:52] CTCP DCC: CHAT chat 3641898720 4456 from Divine (~2lam34u@217-18-246-224.cablebg.net)

i'll be glad if anyone can help me

ppslim · Post by **ppslim** » Sat Apr 12, 2003 8:19 am

When you send a DCC chat to sombody, it is that person that makes the network connection to you, and not you to them.

As such, are you running any sort of firewall ont eh machine that would block this connection?

Other wse use "/ctcp <bot> chat" replacing <bot> as needed. These commands are there to get around the very limitations DCC induces.

divine · Post by **divine** » Sat Apr 12, 2003 12:55 pm

firstly thanks for the help...

well i don't have any kind of firewall
that could block the DCC it must be something else

as i said "/ctcp <bot> chat" works perfectly but this is a sort of telnet
(such as a telnet connection to the bot @ port 3333)

i want to be able to initiate DCC chat with the bot via the "/dcc chat <bot>"
command

P.S. in addition earlier that day i was able to use this command ("/dcc chat <bot>")

ppslim · Post by **ppslim** » Sat Apr 12, 2003 1:49 pm

The you will need to look at exactly what was changed between it wokring, and when it stopped.

"/dcc chat <bot>" and "/ctcp <bot> chat" are allmost the same.

The only differances are

1: You also need to type the useranme on one of them

2: Telnet codes are sent to you. These can be fixed using ".fixcodes".

If you can tell me any serious differances that require that you have to use "/dcc chat", these would be looked into.

But the fact remains, DCC connections have limitations in NAT environments, and command shave been created to get around it.