aspectacle

If either of you are running XP make sure that you're patched up to SP3. That prevented me from creating or accepting LAN connections in demigod.

I had a similar problem. My solution was to ensure I had XP sp3 patch installed. I also completely disabled my personal firewall and restarted.

Success. Note folks, make sure that you have XP sp3. Uninstall your firewall, especially if it's Comodo, disabling it might not work.

More info now. One machine is Vista64, the other XP32. The XP machine is not responding to packets, whereas the Vista one is. I conclude that something is wrong on the XP machine. The XP machine seems to be listening on all the right ports (netstat -a reports 15000 and 6073 in the listen state). We're currently uninstalling the firewall, since disabling it doesn't seem to work (it doesn't report that it's blocking anything, but who knows).

Changing the port ranges didn't have the desired effect. All firewalls are off and messages are obviously getting through the router. Changing who is host and who is joining doesn't fix the problem. Is there any debug I can look for or turn on in Demigod to see why the joining client is ignoring the packets it is receiving from the host? Should I raise a ticket for this issue? Is there any information I can provide to help troubleshoot?

Same problem here. Ran wireshark on both machines. Client is sending UDP broadcast from port 1075 to 15000. Server is responding directly (15000 to 1075). Packets back and forth continuously. Nothing comes up on the screen. The only possible problem is that the server response is fragmented. But then you'd already be handling that, since at 1800 bytes, it's bigger than a standard Ethernet frame. Nice text-based protocol btw, all the server details are there in the clear.