vexed commented

We don't support hamachi at all.

As for LAN play, it works for me, did you do anything special ?

(note, it is better to upload the log files directly to the ticket, not used a 3rd party host.)

Siber uploaded file Hamachi_netplay-20120320_150714.log (4.8 KiB)

.log file of Hamachi hosting attempt.

Siber uploaded file Hamachi_WZlog-0320_150714.txt (1.1 KiB)

other log file of hamachi hosting attempt.

Siber uploaded file LAN_netplay-20120320_151356.log (22.8 KiB)

.log file of LAN hosting attempt.

Siber uploaded file LAN_WZlog-0320_151356.txt (1.5 KiB)

other log file of LAN hosting attempt.

Siber commented

Replying to Warzone2100/old-trac-import#3347 (comment:1):

We don't support hamachi at all.
Understandable, though if my understanding of its operation is correct a Hamachi game should be roughly equivalent to a LAN game.

As for LAN play, it works for me, did you do anything special ?
Not to my knowledge. It's possible there is some oddity to the network that I'm unaware of or have forgotten, but 2.3.9 works with both the LAN and with Hamachi play with the same participants that were attempting to play the beta.

(note, it is better to upload the log files directly to the ticket, not used a 3rd party host.)
Attatched the log files directly.

vexed commented

Replying to Warzone2100/old-trac-import#3347 (comment:2):

Replying to Warzone2100/old-trac-import#3347 (comment:1):

We don't support hamachi at all.
Understandable, though if my understanding of its operation is correct a Hamachi game should be roughly equivalent to a LAN game.

I was just trying to remove a possible cause of the fault, since nobody that I know uses that program.

As for LAN play, it works for me, did you do anything special ?
Not to my knowledge. It's possible there is some oddity to the network that I'm unaware of or have forgotten, but 2.3.9 works with both the LAN and with Hamachi play with the same participants that were attempting to play the beta.

Are you hosting the game on the LAN, then joining via direct IP, and not from the lobby server ?
If you can, have the host do --debug=net and try hosting again, and post the WZlog file from that.

(note, it is better to upload the log files directly to the ticket, not used a 3rd party host.)
Attatched the log files directly.

Thanks.

Siber uploaded file WZlog-0320_192513.txt (31.2 KiB)

Log of LAN hosting attempt with --debug=net

Siber commented

Replying to Warzone2100/old-trac-import#3347 (comment:3):

Are you hosting the game on the LAN, then joining via direct IP, and not from the lobby server ?
If you can, have the host do --debug=net and try hosting again, and post the WZlog file from that.

Yes, hosting on LAN and joining by direct IP. Just did as you requested and attached the log file to the ticket. Also noticed very choppy menu response after hosting but before a player joins, followed by complete game freeze after join. Joining player reported being able to change player name but not color.

vexed commented

OK, I can see where it tries to connect to the lobby server and times out (which is ok), but on connection from client, you are getting socket errors (Invalid socket (EBADF)), and I have no idea why you are getting those.

Do you have any anti-virus type programs running, or a firewall installed ? Something is interfering with the socket. I assume that port 2100 is open on the LAN host, and no firewall is blocking that TCP port ?

Siber commented

Replying to Warzone2100/old-trac-import#3347 (comment:5):

OK, I can see where it tries to connect to the lobby server and times out (which is ok), but on connection from client, you are getting socket errors (Invalid socket (EBADF)), and I have no idea why you are getting those.

Do you have any anti-virus type programs running, or a firewall installed ? Something is interfering with the socket. I assume that port 2100 is open on the LAN host, and no firewall is blocking that TCP port ?

Windows Firewall and Microsoft Security Essentials, set to let Warzone through, and not interfering with any other multiplayer games, WZ 2.3.9 included.

vexed commented

Well, I tried to replicate, and I can't, so something is interfering with the ports or program.

If you still want to test, then turn off the firewall, and MSE, and see if it still does it.

vexed changed status from new to closed

vexed changed resolution from `` to needinfo

Siber uploaded file netplay-20120331_155838.log (23.7 KiB)

Netplay log file of a succesfull host through hamachi after opening port 2100

Siber uploaded file WZlog-0331_155838.txt (10.5 KiB)

WZlog file of a succesfull host through hamachi after opening port 2100

Siber commented

I got port 2100 succesfully forwarded to my machine and was subsequently able to host without trouble, without change any other variables. Is it possible that failed attempts to report the new gamestate to the lobby server when the lobby server isn't available are hanging the game?