DCC problem

[Enlil]

Well, on my server the DCC doens't work at all! When I want to send something or start a DCC chat, I get a:

-
*** Unable to resolve local host for DCC Send
-

error :/ What do I have to do? Do I have to change something in my conf?

Well, thanks in advance

[Ping]

connect with you real ip not use /server 127.0.0.1 or similar

[Enlil]

well, the server is on a shell so I have to use his real adress (and so 127.0.0.1 doesn't work ^^), and it has only one adress.

Actually, I need it for giving orders to mu eggdrop. The eggdrop is on a shell, and the server on another shell, and me, on my computer, I connect to the server .

well, I hope those new informations will help you to help me :p

[Ping]

i think the problem is not the unrealircd is you eggdrop configuration, because de error message is not common for unrealircd. If i´m wrong please correct me.

[Enlil]

Well, I think you're wrong because the DCC doesn't work at all: if I want to send something to somebody, I get the same error (as a notice, in teh status window) :/ And I'm not the only one to have that problem on the server, so the problem comes from the server itself

[w00t]

Somewhere, something can't do DNS properly :p. Looks like a client side problem, since Unreal doesn't actually have anything to do with DCC - that's handled entirely by clients.

[Enlil]

lol ^^

But maybe unreal makes something wrong with the hosts and so the DCC can't work beacause of "another-world-hosts" :p?

[Dukat]

Simple question:
Does DCC work for you on other networks?

[Enlil]

Yes, it works for me on other networks

and by the way, I'm not the only one to have DCC problems on my network, so it doesn't come from me

[w00t]

Is DNS resolution working ok? (check various /whois, etc)

[Enlil]

Well I think so but I'll check.

Ping told me that maybe it comes from the fact that I have no 6667 port, I use weird one (8527). What do you think about that?
Anyway, I'll soo change my daemon of server and I'll have a good old 6667

[Syzop]

If you have a router/gateway, it - normally - needs to "intercept" the DCC request so it can forward the port stuff etc. Hence, if you use an uncommon port, or are SSL connected, it won't be able to intercept and fail.

(Sidenote: if you use DMZ with [nearly] no firewall, your DCC would probably work a lot more often, but this is not a recommended configuration)

So yeah, possibly changing the port is the way to go ;).
That said, the unable to resolve local host msg is weird, did you check if you got that on networks you can dcc at as well? It might be unrelated.

**

If you configure mIRC entirely different than the default settings then you can make it 'so it always works'. That's what I did, because I'm behind a router/gateway, and I'm constantly using SSL on IRC.

In case anyone wonders what that configuration is (though, I'm sure others have done the same).

NEAR-ALWAYS WORKING DCC 1:
1. connect -> localinfo: lookup method = server [get localhost=on, get ip=on]
2. forward a few ports (say, 10 or 100) from the router to your pc
3. enter this portrange in mIRC in connect->options->advanced: 'port range for connections' [dcc=on], first=<start of your range>, last=<end of your range>, rest is off (though 'use random ports' can be turned on, which can be a good idea).

Still, that configuration would not work for people hosting their ircd locally on the LAN. That's why I'm using even another configuration (for years now):

NEAR-ALWAYS WORKING DCC 2 (especially for people running ircds at home!):
1. I'm assuming you have a dyndns or getip host that is automatically updated (you probably have, since you run an ircd) if you have dynamic ip, otherwise.. use whatever your static host is.
2. connect -> localinfo: lookup method = server [get localhost=OFF, get ip=ON]. Local host: fill in your dyndns name (eg: blah.dyndns.org), ip address: remove what it currently says (just to be sure, it will be resolved next reconnect).
[rest is same as with the previous configuration..]
2. forward a few ports (say, 10 or 100) from the router to your pc
3. enter this portrange in mIRC in connect->options->advanced: 'port range for connections' [dcc=on], first=<start of your range>, last=<end of your range>, rest is off (though 'use random ports' can be turned on, which can be a good idea).

This will "always" work. I put in quotes because:
1) Naturally only YOUR dcc's will work
2) If you got a dynamic ip (which I assumed btw), and your ip changes, then you will need to reconnect to your lan ircd for the dcc to work again [this sounds unlogical, huh?], this is so your dyndns.org host is resolved again (though sure, you can fill it in by yourself or a script ;p), otherwise it would be using your OLD ip.
3) Taking 1 and 2 into account, and assuming you forwarded stuff correctly, there can be no error on your part now anymore ;p.

**

I know all this because I know all components involved that can make DCC fail (many indeed, some even unmentioned), so a non-working DCC is not mysterious at all for me.

I don't know why these (relatively simple) instructions are not a bit more widely known, because they can be very useful.

[Jason]

Ping told me that maybe it comes from the fact that I have no 6667 port, I use weird one (8527). What do you think about that?

Thats wrong.

[w00t]

NEAR-ALWAYS WORKING DCC 1:

...

I don't know why these (relatively simple) instructions are not a bit more widely known, because they can be very useful.

Should that be stickied sometime? :p

[Syzop]

Perhaps that would be a good idea ;).

Especially the "I got my own ircd server on LAN and now no dcc works anymore" (2nd solution) thing is not a clearly documented problem (eh.. solution).