I was just using a single computer before and always connected to my bot via /DCC <botnick> CHAT. Now I have been networked to 3 other computers and am behind a hub that has a built in firewall and I can no longer connect to the partyline they way I used to. I have to connect via /ctcp <botnick> chat. This seems to be a slower connection and 'times out' or disconnects very often. After connecting this new way I try to connect the OLD way and while ON the partyline I see this:
You need to setup your dcc options in mirc if that is the client you are using. Setup 10 ports say 10010 - 10020 for instance and also forward those same ports in your router/hub to your pc's internal network IP. That way when you dcc chat a bot when the reply comes your router/hub knows where to send the packets.
Depending on the router some manufacturers call 'port forwarding' 'virtual server'
Hope this helps.
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born
try to "set protect-telnet 0" in the config file.
however, basically you will get the same connection at the end, because the only diffrenze is the side that has initialized it. if you are experience any timeouts it more likely a general internet connection issue. The only option i could think of in which case it could be more usefull for your bot to initialize the connecion would be, if any of yours or the bots ISP throttles spezified port (ranges).