Forums Bug Reports bug with /dcc chat ?

i think that i found a bug in /dcc chat, that happened in mirc 6.14

when i open a dcc chat with a clone using the ip (/dcc chat 127.0.0.1), this clone and i using mirc 6.14, it opens normally, but if i close this chat and type /dcc chat 127.0.0.1, i receive the message "Unable to connect".
and when i request a dcc chat by a command (it's a bot, and when i type !nmud it sends a dcc chat to me) it opens normally, but if i close this chat and type !nmud again, i receive the message "Unable to connect" too.

if i wait some minutes and try again, the dcc chat opens normally; but if i try again, the "unable to connect" appears.

this does not occur in version 6.12. (even if the bot is using mirc 6.12 and i am using mirc 6.14)

sorry for my bad english

Hi,

Maybe the port range you're using (and eventually the xdcc bot) is too short (only 1 port? 4000 to 4000?) So when you close the connection, this port remains open for a few seconds, don't know why (here could be the bug).
Try using a large port range.

where can i view/set the port range?
i did not found in the dcc options

Alt+O -> Connect -> Options -> Advanced...

thanks hammer!

the port range is 1024-5000.
but fxmakers could be right, since after a few minutes later the dcc chat could be opened again

this post touched on the same topic. I am not sure what causes it but that possibility of the port lingering in use for a minute could be the culprit.

And this post offers a solution

I am well aware of the "random port" option. Obviously if the sender could use enough ports for that to work more reliably than a sequential port selection, they would not need to fix anything because it would always use different ports.

Your "solution" actually makes things worse for people who have a very limited port range.

This is only a solution for non port-specific situations, like a normal dcc send between 2 completely unrestricted clients. In a perfect world, we could all use any port. Realistically, this is not the case.