Hm, i suppose your channels are set to +share, and the bot flags are set +s and +hp.
Are you on dalnet? They have severe problems with some ddos lately, I know from my own experiance this will abort a userfile transfer there sometimes.
Are you by chance behind a NAT or is the bot you are connecting to?? i recently had a similar problem trying to connect to bots on NAT for a share...I solved it by commenting the my-ip and my-hostname lines and using only nat-ip(outside ip) like the conf suggests... Then forwarded the appropriate ports .. (you can get these with a .dcc as your bot tries to send the userfile)
When i first did this i had DEADFOOD or something or other in my .dcc so if you see that its prolly something similar
Thanks for the suggestions, I have tried increasing timeouts on just about every setting..
And yes my bot(s) are being NAT, i have tried setting the my-ip setting but not both the my-ip and my-hostname at the same time, i'll give that a shot tried just about everything else
Also i have DMZ'd all the ports to the computer running the bot(s).
If so - I had this exact problem. I think it was because I had a default policy of DROP on pre-routing. I also set both bots address to the INTERNAL IP (i.e 192.168.0.1:Port)
Also try turning on debug console - it can tell you an awful lot more about why the connection was dropped (.help console for more on this) - not if its a firewall problem, but...
If they're not on the same machine, then its usually just a matter of making the pre-requisate ports open.
Oh - one more thing - if they are on the same machine - dont use the same port for both of them!!! (stating the obvious, but...)
one more thing - you can test what is going on by attempting to telnet into the bot from the machine the other bot is on. (assuming your bot is lsitening on the same port for all). If it accepts telnets, but wont share user file, then you have a problem in the bot. Otherwise its a firewall thing.
I have a hub-bot on a non-nat connection and a slave-bot on a nat connection. I've set nat-ip to the right ip.
botattr is +ghp and +ghs.
On the both bots I've specified transfer-ports.
And yes I can telnet to the bot with the nat connection.