This is probably a function of the new DCC Send behavior. mIRC apparently grabs the first available port in the DCC range instead of a random one, so it's much more likely to choose the same port twice in a row. Having the sender check the 'random ports' option would help fix this issue.
