Hi Guillaume,
There was a bug in net6 which involved WSAGetLastError() twice when an
error occured, maybe this lead to a wrong error code. It will be fixed
with the release candidate 3 which will be released today.
However, your network configuration should work with Gobby.
Running on Windows this translates to some error handling involving
WSAEWOULDBLOCK returned during some operations. Could the problem happen
because the latency between client and master are very high?
The latency should not be the point, you should have received another
error message then (Something like 'Connection timed out').
-- armin
_______________________________________________
obby-users mailing list
[email protected]
http://draenor.its-toasted.org/mailman/listinfo/obby-users
