http://bugs.winehq.org/show_bug.cgi?id=5240
--- Comment #17 from Erich Hoover ehoover@mines.edu 2012-04-18 07:58:43 CDT --- (In reply to comment #16)
... After receiving it's own broadcast it closes the socket (0.0.0.0:950) and opens a new socket using the received address, let's suppose 192.168.0.1:950. It again sets SO_BROADCAST in this new socket and sends a new broadcast, now to 192.168.0.255:950 expecting it to arrive to itself again. But this second messages never arrives... It keeps sending this message in a regular interval but as it does not receive it the program does not behave correctly.
Maybe I'm misreading this, but it sounds like Bug #7929. If it's binding to a specific IP and looking for broadcast packets on that socket then that won't work unless you've patched Wine with one of my attempts to fix that issue.