http://bugs.winehq.org/show_bug.cgi?id=26031
--- Comment #19 from Artem S. Tashkinov t.artem@mailcity.com 2011-10-29 01:49:57 CDT --- (In reply to comment #18)
In this case it appears to be a difference in kernel implementation of sockets, which we tend to treat as invalid, as it'd have to be fixed upstream (and won't be, realistically.)
Wine should mimic Windows sockets behaviour, shouldn't it? So if sockets work differently between the Unix/Posix world and the Windows world Wine should strive to provide maximum Windows compatibility.
Besides, as far as I can understand adding SO_REUSEADDR to socket() invocation just cannot hurt, so if it helps to solve this issue, I think it would be best to change the default Wine behaviour in regard to listening sockets.