http://bugs.winehq.org/show_bug.cgi?id=8533
------- Additional Comments From damjan.jov@gmail.com 2007-12-06 01:06 ------- Here's the problem:
Socket 00dc binds to 127.0.0.1: trace:winsock:WS_bind socket 00dc, ptr 0x34f6f0 { family 2, address 127.0.1.1, port 0 }, length 16
Then the same socket tries to connect to an IP that's unreachable from the lo interface: trace:winsock:WS_connect socket 00dc, ptr 0x34f480 { family 2, address 208.109.235.57, port 80 }, length 16
On Linux that fails with EINVAL. But does it work on Windows? I'll run some tests and see exactly what happens.