Page 1 of 1

Red Eclipse server giving me weird issues

PostPosted: 07 Oct 2012, 00:39
by lolpants
I used to always host a Red Eclipse server and it would always work perfectly, but ever since I updated to version 3.1 of the game, I haven't been able to run the server, and I keep getting this message every time I try: master server reply: ping attempts failed, your server will not be listed... I'm trying to start a clan server now and I really need to get a map up and running so we can get our name out and put our maps we have worked on on the server. I've looked online, and on the wiki and I can't find anyone else having the same problem so I'm wondering if someone else here on these forums might know of a solution.

Re: Red Eclipse server giving me weird issues

PostPosted: 07 Oct 2012, 01:21
by qreeves
If the server fails pinging, then your firewall is blocking attempts to contact it. You need to open ports 28801 and 28802 UDP.

Re: Red Eclipse server giving me weird issues

PostPosted: 07 Oct 2012, 06:10
by ZeroKnight
qreeves {l Wrote}:If the server fails pinging, then your firewall is blocking attempts to contact it. You need to open ports 28801 and 28802 UDP.

Or, if you used a custom port, you need to allow that port, and ( port + 1 ).

Re: Red Eclipse server giving me weird issues

PostPosted: 07 Oct 2012, 15:48
by lolpants
ah haha, I had an un-needed if statement: "if (= $rehashing 0)" on the older versions it didn't matter that I was checking this, but on the new version It doesn't pass as true, so the port is never set.

Re: Red Eclipse server giving me weird issues

PostPosted: 07 Oct 2012, 15:53
by lolpants
but, wait, I'm getting the same error when I run my server while it's using wired internet, but when I use wireless it seems to work just fine. How do I fix that problem?

Re: Red Eclipse server giving me weird issues

PostPosted: 07 Oct 2012, 21:41
by ZeroKnight
My guess would be that DHCP is allocating an internal IP that's different from your wireless one when you connect via ethernet, thus causing the forwarded ports to forward to the wrong address.
Worth a shot to double check on that :)