I have no idea what you're all on about. His proxy obviously doesn't relay to the bot. Which isn't a problem at all because you can obviously make the bot dcc chat you via ctcp, because the proxy does allow to connect, which is made apparent by the fact that the bot is connected to the server...
nsignific, you obviously do not know how the DCC initiation sequence works, do you. If you did, comments in your previous posts would nbot have been made.
If I where to type "/dcc chat nsignific" in my cleint, my client would open a local port, and send you a ctcp message notifying you of my IP and port. Your client would them make the connection to my computer.
So if you computer is the one running eggdrop, and it is able to connect to a server, why can't it connect to my computer (given as example by the problem above).
It is true, eggdrop is able to connect to the IRC server, but it is faulse that there are no problems, because the bot is unable to make that network connection.
As for the problem itself. There are many guides on the internet to setting up a network with mirc, and being able to DCC send, chat and receive files. You will have to find one of these and follow it's instructions, as this problem is firewall & cleint related, not eggdrop.
no it isnt. /dcc bot chat makes you the passive party (ie, you open the port for the bot to connect to), /ctcp bot chat makes the bot open the port for you to connect to.