Confusing Problem.

[thefallingkeys]

I can't figure out why my server won't show up on the list.
I used the server tool posted and these are my results:

DP Resource Public Server Troubleshooter
Specified server information: 65.26.192.147:27910
RCON password provided? yes
Run at Tue, 25 Sep 2007 23:10:38 +0000

TEST PROCESS
===================
> Checking if 65.26.192.147:27910 can be connected to...
>    Writing to socket: '\xFF\xFF\xFF\xFFstatus\n'
>    Attempting to read, 3 second timeout...
>    Success: Strings 'Digital Paint' and/or 'DPPB2' found in server output (ping: 86ms)
> Connection SUCCESSFUL! Port forwarding and firewall settings correct.
> Checking server list...
> Getting server list from http://dplogin.com/serverlist.php
> 68 lines of server list data
> Processed 62 server lines, 20 different IPs
> No entries found on the server list
> public is set to 1

RECOMMENDATIONS
===================
* Run the command heartbeat in console, as it seems the server is public and it's on, but somehow it wasn't added to the list
* Or, is your server banned from the server list for some reason?


I tried the heartbeat command and nothing changed.  I also have never been banned from the server list.  Any suggestions?

Thanks

[lekky]

What have you set as the master list in the server cfg file? Should look something like this:

setmaster dplogin.com master0.gamespy.com

[thefallingkeys]

this is what i have, i used the default template from the server tutorial

setmaster dplogin.com
setmaster q2master.planetquake.com
setmaster master0.gamespy.com

not sure why there is three?

[lekky]

Try removing those 3 lines, and inserting my line in the same place, see if that works.

[thefallingkeys]

I replaced them with your line and now it says

DP Resource Public Server Troubleshooter
Specified server information: 65.26.192.147:27910
RCON password provided? yes
Run at Tue, 25 Sep 2007 23:40:27 +0000

TEST PROCESS
===================
> Checking if 65.26.192.147:27910 can be connected to...
>    Writing to socket: '\xFF\xFF\xFF\xFFstatus\n'
>    Attempting to read, 3 second timeout...
>    Success: Strings 'Digital Paint' and/or 'DPPB2' found in server output (ping: 84ms)
> Connection SUCCESSFUL! Port forwarding and firewall settings correct.
> Checking server list...
> Getting server list from http://dplogin.com/serverlist.php
> 67 lines of server list data
> Processed 61 server lines, 22 different IPs
> 1 entry/entries found in server list for your IP address:
>    65.26.192.147:14439
> None of the entries have the right port!
> public is set to 1

RECOMMENDATIONS
===================
* 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: 14439
* If you want to actually 'fix' the problem and use port 27910, then ask in the server help forum for help (copy the log at the bottom of this page)

So something changed, not sure exactly what though.

[XtremeBain]

What is your network setup?  Like what kind of router or hardware firewall are you using?

[thefallingkeys]

i have a linksys wrt54g router, and just windows firewall.  the problem finder thing says portsettings and firewall are correct, unless theres something else i need to change?

thanks

[XtremeBain]

There is a problem with your out-bound NAT.  A few things could be happenning here.

What is the port forward setting in your router (Found at Applications & Gaming > Port Range Forward)?  It should work fine with:
Application   Start   End     Protocol    IP Address    Enable
DP Server     27910   27910    Both       192.168.1.x     x

If that's how it's setup and it's still not working, make sure you take a look at your port triggerring settings and remove anything that conflicts with 27910.

If your router config looks fine, then the 27910 port might be stuck in the router's internal NAT table.  Unplug the router from the power for a few seconds to clear it's memory and plug it back in.  Once it's back online, restart your server and see if it starts heartbeating after 5mins or so.

I've got a few other possible scenarios, so just let me know how it goes with that and I'll start throwing you the highly unlikely solutions.

[KiLo]

You could try adding +port 27910 to the command line of your shortcut.

[XtremeBain]

You could try adding +port 27910 to the command line of your shortcut.

This is obviously not the problem since the server is being accessed correctly through the \xFF\xFF\xFF\xFFstatus command send out by the server troubleshooter, and people are able to connect to it using the default port.  His problem is that the server is not heartbeating correctly with the dplogin.com master server and so 95% of players have no idea it even exists.

> 1 entry/entries found in server list for your IP address:
>    65.26.192.147:14439
> None of the entries have the right port!

This right here means could indicate that he's running another server that's heartbeating fine on :14439, but since he's not then it means that when his server sends the heart beat request to dplogin.com, it is getting the wrong port number.  This is attributed to NAT and his router.  Here's a quick diagram:

                  <Windows Desktop>      <Linksys Router>     <dplogin.com>
Heartbeat Request
                    [PB2 Server]---:27910----->[NAT]---:14439--->[DPMaster]
Heartbeat Response
                    [PB2 Server]<--:27910------[NAT]<--:14439----[DPMaster]

The way NAT works on the router, is that it keeps in memory a table of active connections.  This list is pretty much the LAN IP, the LAN port, the destination IP, the destination port and the port it has decided it will use on the router to complete the transmission.  The first thing that your router will do when you try to establish a new connection is that it will check its table to see if this connection matches any of the existing connections.  If not then next it sees if it can reserve the LAN port to complete the transmission.  If there is another entry which has already reserved this port on the router, then it will make up a port.  The router's NAT does all the magic behind the scenes to convert 192.168.1.100:27910 to 65.26.192.147:14439 so that all the information reaches it's going.

The fact that his router's NAT is using :14439 (and other random ports) means that :27910 is still reserved.  Rebooting the router and making sure the port forwarding is correct will probably clean this up.

[thefallingkeys]

ok im going to try resetting my router, ill update you once its done.  also thanks for all the information, im starting to understand whats going on.

EDIT: Alright, I restarted the router and same problem occurs but its showing only one port instead of like 5.  I'm not sure if that was the reason. I checked for any conflicts and found none. I also skeptically tried adding the +port command thing and nothing happened also so it is definitely something with my NAT settings or whatever.  Any way to fix it?

[ViciouZ]

This is probably completely unrelated, but check your router has the latest firmware. It screwed my NAT over for 6 months before I upgraded.

[thefallingkeys]

actually viciouz i was reading some forums about my specific router and it seems that may be the problem. im going to upgrade its firmware and i'll let you know.  thanks.

[thefallingkeys]

first off please excuse the double post

but guess what guys, i updated the firmware and...

DP Resource Public Server Troubleshooter
Specified server information: 65.26.207.15:27910
RCON password provided? yes
Run at Sun, 30 Sep 2007 20:06:39 +0000

TEST PROCESS
===================
> Checking if 65.26.207.15:27910 can be connected to...
>    Writing to socket: '\xFF\xFF\xFF\xFFstatus\n'
>    Attempting to read, 3 second timeout...
>    Success: Strings 'Digital Paint' and/or 'DPPB2' found in server output (ping: 87ms)
> Connection SUCCESSFUL! Port forwarding and firewall settings correct.
> Checking server list...
> Getting server list from http://dplogin.com/serverlist.php
> 71 lines of server list data
> Processed 65 server lines, 26 different IPs
> 1 entry/entries found in server list for your IP address:
>    65.26.207.15:27910

RECOMMENDATIONS
===================
* Everything looks like it should work


thanks for the help everyone.