http://bugs.winehq.org/show_bug.cgi?id=30020
--- Comment #9 from Bruno Jesus 00cpxxx@gmail.com 2012-04-19 10:25:56 CDT --- It's common practice to bind to 0.0.0.0, does it start any other process that opens port 17729? Please attach the +winsock log. Look for gethostbyname calls to see if it's trying to resolve a server address. Why would it connect to 127.0.0.1?
This is certainly interesting but may not be the direct cause: trace:winsock:WS_setsockopt socket: 029c, level 0xffff, name 0x80, ptr 0x2a2e914, len 4 warn:winsock:wsaErrno errno 22, (Invalid argument).