Somebody please help me server isnt showing up

[wildchild22]

ok i know that there are millions of these topics but i cant seem to figure this out. I have checked to make sure my server is dedicated and public, also i have shut down my firewall. But the port forwarding thing is kinda confusing me. I have a netgear router and in the port forwarding/port triggering section. I go to port forwarding and it tells me to give a starting port and an ending port. Are both of these the same as my server. What i mean is if i want my server to be on port 55055 then i put 55055 in the starting and ending port? Oh also whats confusing me is in the black box is says the sending heartbeat ......... and then heartbeat accknowledged from .......... you know

[KnacK]

make sure that the ports are for UDP and not TCP.

Forward the ports from the internal ip aaddress of your server to the external side of your router.

If you are gettign a response on your heartbeat then it is talkign with the master server - which is a good thing as it means it will show up on server lists.

[sk89q]

First: http://digitalpaint.therisenrealm.com/tools/servertroubleshooter

What your router means by starting and ending port is the range of ports to map. It lets you map ports 32433, 32434, 32435, 32436, etc. by entering a range with a start and an end. What you set on your router does not set it on the the Paintball server (you typically do that in the server's configuration file). The default port for a Paintball server is 27910. Put 27910 for both starting and ending ports, and make sure the protocol is UDP.

Heartbeats are pings to the official public server list. When the server sends a heartbeat, it tells the server list that it is running a public server. It has to do this occasionally, or the server list will assume the server has died.

[wildchild22]

thank you for clarifying everything ill try to see what i can do and check the serverlist again

[KnacK]

The server troubleshooter is your best friend in this case.
+10 sk89q

[wildchild22]

this is what the server troubleshooter said


Checking if 71.197.221.104:27910 can be connected to...
> Connection SUCCESSFUL! Port forwarding and firewall settings correct.
> Checking server list...
> 11 entry/entries found in server list for your IP address:
>    71.197.221.104:2402
>    71.197.221.104:2956
>    71.197.221.104:3035
>    71.197.221.104:3180
>    71.197.221.104:3259
>    71.197.221.104:3411
>    71.197.221.104:3413
>    71.197.221.104:3490
>    71.197.221.104:3493
>    71.197.221.104:3648
>    71.197.221.104:2405
> None of the entries have the right port!
> public is set to 1


You have encountered a problem that we are not aware of a 'correct' solution for. However, as the server list does list some of your ports (even if they're not 27910), you can set your server port to one of those: 2402, 2956, 3035, 3180, 3259, 3411, 3413, 3490, 3493, 3648, 2405


so now what do i do cause it still isnt showing up.

[sk89q]

Ugh, that problem. Let's fix it the cheapy way.

When you start up your server, what .cfg file do you run (like +exec server.cfg)?

Whatever file it is, open it in Notepad. It's in pball\configs\. Run the troubleshooter again. Find "port" in there. Change the number to one of those listed after "you can set your server port to one of those" on that troubleshooter page. If port isn't in there, add port # on a new line, where # is one of those numbers. Restart the server, and tada!

[KiLo]

Or you can do +set port <#> in the command line.

[sk89q]

Pfft. That's for lazy people D:

[XtremeBain]

Ugh, that problem. Let's fix it the cheapy way.

When you start up your server, what .cfg file do you run (like +exec server.cfg)?

Whatever file it is, open it in Notepad. It's in pball\configs\. Run the troubleshooter again. Find "port" in there. Change the number to one of those listed after "you can set your server port to one of those" on that troubleshooter page. If port isn't in there, add port # on a new line, where # is one of those numbers. Restart the server, and tada!

That will not fix the problem.  You can find the (or my) explanation of this issue here and here.  It all boils down to the port forwarding not being setup properly, and NAT doing it's magic so that the server can communicate with the dplogin.com master server.

To resolve this issue, you need to ensure that you have 27910 UDP forwarded properly to the local IP address of the computer you have running the server behind your router (or firewall).  In order for this to be effective, I would recommend that your 'server' computer have a static IP configuration, or setup your router so that the computer has a static DHCP entry (MAC or hostname based).

I really like the troubleshooting utility, but how about allowing people to adjust the IP address (throttled at one test per 5mins per IP) so that people can troubleshoot their real dedicated servers.  It would also be worthwhile to implement a detection for the NAT incremental port issue that more and more people seem to be experiencing.

[sk89q]

That will not fix the problem.  You can find the (or my) explanation of this issue here and here.  It all boils down to the port forwarding not being setup properly, and NAT doing it's magic so that the server can communicate with the dplogin.com master server.

To resolve this issue, you need to ensure that you have 27910 UDP forwarded properly to the local IP address of the computer you have running the server behind your router (or firewall).  In order for this to be effective, I would recommend that your 'server' computer have a static IP configuration, or setup your router so that the computer has a static DHCP entry (MAC or hostname based).

I'd have to disagree. Why then, can others connect to the server, if port forwarding was set up incorrectly? Mind you, one of my friend's behind-a-router server has been subsisting like this for over half a year now. It explodes on the server list, but we can connect and play without a hitch.

When I was testing the server troubleshooter, I had the same problem, although it wasn't so permanent. It later worked fine too, oddly. My computer is on a static IP inside my network.

I really like the troubleshooting utility, but how about allowing people to adjust the IP address (throttled at one test per 5mins per IP) so that people can troubleshoot their real dedicated servers.  It would also be worthwhile to implement a detection for the NAT incremental port issue that more and more people seem to be experiencing.

Since there have been quite a few people suggesting that, I'm thinking about allowing that.

As for the incremental port issue, I was originally planning to implement it, but as most of the solutions suggest checking port forwarding settings anyway, I didn't bother.