Greetings everyone:
I've exhausted my resources. I've compiled a few eggdrops before and set them up but I've never ran into a problem like this. I'm setting up an eggdrop for a friend, and the bot will simply not chat with him. Here's the kicker: He can accept chats from other users, issue chats to other users, send and receive files. The bot simply will not acknowledge him.
I can chat to the bot just fine, as well as anyone else. The only person who's having the problem is the owner. I've setup his HOST mask in the eggdrop.user file to match him from any IP with Name!*@*
Here's a sample from the eggdrop party line:
<Lidocaine> [04:16] -Atropine (~xtreme@CB56696.5703A89B.FFF7862C.IP)- DCC Chat (70.40.1.76)
<Lidocaine> [04:16] CTCP DCC: CHAT chat 1177026892 9156 from Atropine (~xtreme@CB56696.5703A89B.FFF7862C.IP)
<Lidocaine> [04:16] DCC connection: CHAT (Atropine!~xtreme@CB56696.5703A89B.FFF7862C.IP)
<Lidocaine> [04:19] Password timeout on dcc chat: [Atropine]~xtreme@CB56696.5703A89B.FFF7862C.IP
I can't figure out what's going on. Hopefully someone here has ran across this problem before and knows exactly my troubles.
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
CHAT request not being accepted by owner
He could just send the password by dcc /msg =botnick without waiting for the prompt.
I've seen some problems with certain versions of mirc where /msg does not work. Donno what the problem is specifically, i've just had users with that problem and had to get them to use an alias for /raw PRIVMSG for things like authenticating on undernet by /msg x@channels.undernet.org (I don't use mirc/windows myself so I can't tell if this is purely user error, or a real bug in mirc. I've had several users report this problem.)
I've seen some problems with certain versions of mirc where /msg does not work. Donno what the problem is specifically, i've just had users with that problem and had to get them to use an alias for /raw PRIVMSG for things like authenticating on undernet by /msg x@channels.undernet.org (I don't use mirc/windows myself so I can't tell if this is purely user error, or a real bug in mirc. I've had several users report this problem.)
Well... I'm honestly thinking he's having a port issue here. Everyone else can work it just fine. I'm definitely at my wit's end on this one. I've been up for far too long.
If I make any headway on it I'll be sure to come back and make an update. Thanks for the time.
*Update*: Had a friend become a new user to the bot and it went through like clockwork. Whatever's preventing the owner from becoming acknowledged is positively on his side. The bot is configured just fine.
*Update #2*: Was able to finally get him to log in using /ctcp botnick CHAT (the whole telnet port thing) I have some slight insight as to what might be causing this problem.
The machine that his bot is on, is setup as a DMZ host. He is routed through NAT (192.X) and when the bot recieves a chat request, it sees the WAN IP. I think the bot, or the router one, is getting confused and not sending the information to the right place. (Ie the router is looping back the chat request to the bot, due to it being a DMZ).
I think if he were to correctly setup his port forwarding he would not have this problem. So anyone who is experiencing something this similar, you might want to check out your port forwarding settings.
If I make any headway on it I'll be sure to come back and make an update. Thanks for the time.
*Update*: Had a friend become a new user to the bot and it went through like clockwork. Whatever's preventing the owner from becoming acknowledged is positively on his side. The bot is configured just fine.
*Update #2*: Was able to finally get him to log in using /ctcp botnick CHAT (the whole telnet port thing) I have some slight insight as to what might be causing this problem.
The machine that his bot is on, is setup as a DMZ host. He is routed through NAT (192.X) and when the bot recieves a chat request, it sees the WAN IP. I think the bot, or the router one, is getting confused and not sending the information to the right place. (Ie the router is looping back the chat request to the bot, due to it being a DMZ).
I think if he were to correctly setup his port forwarding he would not have this problem. So anyone who is experiencing something this similar, you might want to check out your port forwarding settings.