http://bugs.winehq.org/show_bug.cgi?id=20041
--- Comment #26 from Juan Lang juan_lang@yahoo.com 2010-09-14 14:04:42 CDT --- In the bad log, the adapters appear to be returned successfully, and sockets are created: trace:winsock:WS_socket af=2 type=2 protocol=0 trace:winsock:WSASocketA af=2 type=2 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=2 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 0174
But no operations are done on the created sockets.
In the good log, in contrast, sockets are created and bound to a local address: trace:winsock:WS_socket af=2 type=2 protocol=17 trace:winsock:WSASocketA af=2 type=2 protocol=17 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=2 protocol=17 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 0190 trace:winsock:WS_bind socket 0190, ptr 0x82be70c { family 2, address 192.168.2.12, port 58812 }, length 16
Apparently, the information returned by GetAdaptersAddresses is insufficient to make the app happy. There's a lot that GetAdaptersAddresses doesn't return yet, so we'll have to speculate which one will do the trick. I'll attach an easy patch first.