TASClient on a LAN=OK, springlobby on a LAN=no good

[MadRabbit]

OK here's the problem I'm having.

With TASClient, I can log in the the lobby server, host a game, my son can join, and we can play. No problem. His computer and mine are both in the same house, behind an internet gateway/firewall computer, and they have IP addresses like 10.x.x.x

Now I am trying out springlobby (due to the imminent demise of TASClient) and it is not working.

We can both join the lobby server, both get to the battle window, everything looks OK there. But when we start the game, whoever is not hosting hangs on the "connecting to server" screen. The IP address on the "connecting to server" screen is the external IP address of the internet gateway computer eg 207.x.x.x:8452

so bottom line, TASClient we can still play, springlobby we can't.

Any ideas how I can get springlobby working for this setup??

Oh BTW hosting the game with "NAT hole punching" doesn't help

[Argh]

I've had the same problem with Eman. We can get it working with TASClient, but never with SpringLobby. Which is a pity, because it's nicer in many other ways.

[BrainDamage]

found why, will take me a while to fix it