http://bugs.winehq.org/show_bug.cgi?id=10229
Tobias Jakobi liquid.acid@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |liquid.acid@gmx.net Version|0.9.47. |0.9.55.
--- Comment #4 from Tobias Jakobi liquid.acid@gmx.net 2008-02-20 08:16:23 --- Hi there,
sorry it took so long. Me and my colleagues had a "serious" gaming session yesterday and we rechecked the winsock problem there.
Machines in the network: 1) Win XP machine (192.168.0.7) 2) Win XP machine (192.168.0.122) 3) Windows Vista machine (192.168.0.243) 4) Gentoo Linux machine (192.168.0.8) <--- ME 5) Gentoo Linux machine (192.168.0.22)
All machines had Serious Sam TSE 1.07 installed, no copy protection fix was applied (optical disc emulators on every system).
I bumped the wine version to 0.9.55, that's the version that was installed on both machine 4 and 5.
The bug still appears and I made some logs with different configurations.
However we managed to get connecting working between the two gentoo machines. As I was making the logs we produced one log with ME being the server and machine 5 the connecting client, and one log with machine 5 being server and ME connecting.
We also tried the config "windows machine to linux server", "linux client to windows machine", etc.
I'm going to attach the logs and maybe some further informations this evening.
Like I said connecting from linux to linux works, so there seems to be some incompatibility between the winsock implementations.
Greets, Tobias