Warzone : No Connection

[Malkiah]

Ok so for 2 weeks now everything has worked fine and dandy. And everything is still the same, nothing but the actual world has changed in terms of "Changes". Yet out of nowhere it starts doing this crap again, saying its not connected, yet the server menu shows me its connected to the galaxy. My router says the app is send/receiving properly. If I close the server, change the name in the config, then run it. The galaxy shows the name change, so to me its getting something?! I have the reroute.txt and everything setup(YET IVE NEVER NEEDED IT....), still it effin refuses, and im about to become a very barbaric monkey soon....



Ive thought back and I know this sounds ludacris and what not, but this happens when I seem to change the map file used.....i know, it shouldnt be connected on a technical level....but this is when crap gets funky and haywire with establishing a connection. There has got to be some radical bug involved.

-Malk

[Fooli]

Right now, this minute, the galaxy thinks it isn't connected. More than that I cannot say. Except that there is usually a difference between you being able to see (and connect) to your own world, and other people being able to. Is it just a problem for you, or for everyone?

f

[Malkiah]

Ok im going to run the server, Galaxy usually throws it in M-209, Warzone. See if you can see it connected, like I said if I alter the name of the planet, the galaxy updates this, which means something made it from MY COMPUTER to the GALAXY and updated persistently speaking.

*galreconnect did nothing, rebooted computer, rebooted gateway, nothing. Changed ports, changed app name in firewall, ect. Im at my wits ends. I am 99.9% sure I have everything correct on my end. Im sticking to my theory of the map causing something funky, this is the universal and we have all witnessed some funky stuff take place.

So just get back to me anyone who reads this, if they can see Warzone connected.

-Malk

[Fooli]

Okidoki.

First off, whenever you reboot the server, make changes to serverconfig etc, you basically restart the whole process of getting the world connected to the galaxy and broadcast to anyone wanting to see it. So don't keep rebooting it unless absolutely necessary.

Next up.. now I know it's running things are a bit different. The gal shows it as no connection but my special !planetinfo command tells me it's there and gives me what looks like a reasonably sensible IP address. I've no idea whether port 8088 is a good one to use but anyway that's wot the gal sees.

I can ping your ip no problem, so you don't have an external firewall stopping me connecting to the world.

All that remains, then, is your internal routing config... it's a NAT problem, and/or a reroute.txt problem (always try everything else before using reroute - it's only needed, normally, if you run the world and a game client on different PCs on the same LAN behind the same external IP address)

That's as much as I can say/see for now.
f

[Malkiah]

So I went back into the firewall on the gateway and checked again...

Your observation is correct, and by all means should have fixed the problem....

The NAT was recomputing the UDP and sending it to the computer upstairs....

so I made that modification to rerouted to this computer, perhaps something defaulted after the reboot, but none the less I fixed that tid bit.


Still.....no connection, no ticky ticky....

NAT Resolution on System Menu still states Not Available

Fooli if could send me a PM or a email to shattereduniverse [at] gmail [dot] com with the IP your seeing please, would help to check on my end. Perhaps something is truly funky with the gateway.

-Malk

[UPDATE}
I final reboot of the server, and everything is back. Its connected as far as I can see in the galaxy. So ill say Fooli nailed it with reminding of NAT. Fooli please verify if you can see it connected as well. Thanks

[Fooli]

Same IP you just posted from
f

[Fooli]

Yup, works for me now.
f

[zaroba]

judgeing by what happened, i'm guessing that sometime along the way your network went down (maybe a router reboot) and when it came back up, your upstairs pc asked for an ip before the server pc (or vice versa) resulting in the server's lan ip being different which broke the port forwarding.

setting up the server pc to use a static ip outside of the routers dhcp range will avoid that problem.

for example,
my routers dhcp setup starts at 192.168.1.100. so my gaming pc and the other pcs have ips from there and higher. my server pc is set to use the static ip of 192.168.1.50. so regardless of what happens on the network, the port forwarding wont break. nor will my reroute file unless my external ip changes.