http://bugs.winehq.org/show_bug.cgi?id=29168
--- Comment #75 from Sebastiaan Blommers sebastiaan.blommers@gmail.com 2012-01-04 05:32:42 CST --- Hi, I just looked at the code in latest git (socket.c). I don't know if it helps but the code is pretty clear about what it does with the status codes (found in ntstatus.h).
The code switches on STATUS_ALERTED (0x00000101)) and STATUS_PENDING (0x00000103) else it would just return itself.
My conclusion is that the first connection try is false. The socket just won't connect and pops up with wrong statusses (at least, cannot be processed by async logically).
From the log from Xolotl:
trace:winsock:WS2_recv_base socket 03e8 -> WS2_recv returned -1 bytes, errno 11 trace:winsock:WS2_recv_base socket 03e8 -> returning SOCKET_ERROR, wsaErrno 259 trace:winsock:WS2_async_recv socket 03e8, status 257
SOCKET_ERROR pops status 257 which is: #define STATUS_PATH_NOT_COVERED ((NTSTATUS) 0xC0000257). Maybe a path/link/port or credential is missing/incomplete/incorrect?
My question: is STATUS_PATH_NOT_COVERED == code 257 (because of 0xC0000257)
Sebastiaan