http://bugs.winehq.org/show_bug.cgi?id=30020
--- Comment #8 from thanoulas thanoulas@gmail.com 2012-04-19 10:17:22 CDT --- I ruled out RAS as well, I used a native override for rasapi32, the messages went away again, but same results. I am going through a +winsock trace for both the service and the client, and stumbled on something interesting:
trace:winsock:WS_bind socket 02a4, ptr 0x8aa630 { family AF_INET, address 0.0.0.0, port 17729 }, length 16 this is the binding that the service does,
and then the client calls: trace:winsock:WS_connect socket 0254, ptr 0x9d4250 { family AF_INET, address 127.0.0.1, port 17729 }, length 16 warn:winsock:wsaErrno errno 36, (Operation now in progress).
do_connect also fails. This repeats for a while, until: trace:winsock:DllMain 0x44d00000 0x2 0x0 trace:winsock:WS_setsockopt socket: 029c, level 0xffff, name 0x80, ptr 0x2a2e914, len 4 warn:winsock:wsaErrno errno 22, (Invalid argument). trace:winsock:WS_setsockopt Setting socket error, 10022 warn:winsock:wsaErrno errno 22, (Invalid argument). trace:winsock:WS_closesocket socket 029c
(notice that the bind is on 0.0.0.0 and the connect on 127.0.0.1). Any chance the 0.0.0.0 address is not equivalent to 127.0.0.1 in wine for some reason and that's why it fails?