http://bugs.winehq.org/show_bug.cgi?id=19827
--- Comment #2 from Juan Lang juan_lang@yahoo.com 2009-08-23 18:35:56 --- (In reply to comment #1)
there's a repeated warning warn:winsock:WSARecvFrom -> ERROR 10035, maybe that might give a clue?
10035 is WSAEWOULDBLOCK, which is usually given when an application is expecting to receive data but isn't. Here's one of the timeouts:
trace:winsock:WSARecvFrom socket 0194, wsabuf 0x104e884, nbufs 1, flags 2, from (nil), fromlen -1, ovl (nil), func (nil) trace:winsock:WSARecvFrom fd=84, options=0 warn:winsock:WSARecvFrom -> ERROR 10035
Socket 0194 was connected here: trace:winsock:WS_connect socket 0194, ptr 0x1639bf8 { family AF_INET, address 74.125.79.106, port 80 }, length 16
Thus, it's making an HTTP connection to IP address 74.125.79.106. The other timeouts I looked at were similar.
As to why it's not receiving any data: who knows? You'd probably have to examine wireshark traces from a Windows client and from this one to see what the difference is, then try figure out what's causing it.