Network Communication Error: possible solutions

Thus spake Filip:

[This message has been edited.]

I believe private connections still go through the main server, due to
the same reasons I had to struggle with here[1] when trying to run my
own server. It was one of the first things I tested in Vassal 3.2, and
after blocking vassalengine.org in my system I’ve been getting similar
problems as with my earlier builds (either freezes or connection errors

  • unfortunately I don’t remember exact details after three months). So
    it seems like the only advantage of current private connection mode is
    that your game is not visible for everyone when you don’t want it to be,
    like when you’re hiding from trolls.

I suggest that somebody else blocks vassalengine.org and tests various
connection modes to verify that.

That’s the reason I’m still using my old private server hack based on
3.1.17. I’m currently waiting for 3.2.4 release to apply my workaround
hack while taking some advantage of new connection menus (I was just
about to start hacking 3.2.3 today, in fact, but it appears 3.2.3
suffers from some poetntially problematic bugs).

You might have better luck with 3.2.4-svn8623:

vassalengine.sourceforge.net/builds/

See here for why:

peer2peer / private server

J.