Digital Paint Discussion Board
Paintball 2: The Game => Server Discussion => Topic started by: SpitFire on August 27, 2007, 06:12:46 PM
-
my server works i can get into it but nobody can join my server and nobody sees it so can someone plz help me in anyway possible
SpitFire
i have mIRC so u can talk to me their my name is [aB-t]SpitFire so talk to me or reply to it
-
A couple things for you to try/check ...
1. Does your server config have public set to 1
2. Try typing in exec myserver.cfg or whatever you saved your server config as.
3. Check your IP at ipchicken.com then look if it shows up on the serverlist here http://dplogin.com/serverlist.php
-
i checked my ip at ipchicken.com and then looked for it in dplogin.com/serverlist.php and theres like 12 of them. And nobody can see my server still
-
what is your ip address and the port that you are using
-
i checked my ip at ipchicken.com and then looked for it in dplogin.com/serverlist.php and theres like 12 of them. And nobody can see my server still
I think that jitspoe's heatbeat script should query the servers to see if they get anything before foolishly adding another ip/port to the list. These days there's usually 30 garbage servers on the list from people who cannot setup their router properly.
-
I think that jitspoe's heatbeat script should query the servers to see if they get anything before foolishly adding another ip/port to the list. These days there's usually 30 garbage servers on the list from people who cannot setup their router properly.
Agreed.
This sounds like a port forwarding problem to me.
-
/me is guilty of that right now
/me scratches his head wondering why his server still isn't working.....
-
I think that jitspoe's heatbeat script should query the servers to see if they get anything before foolishly adding another ip/port to the list. These days there's usually 30 garbage servers on the list from people who cannot setup their router properly.
Problem is, when the server sends a heartbeat to the server on whatever particular random port it may be, that port will be open for responses, so if I query it, chances are, it will all work OK. I've considered restricting allowed port ranges to like 279XX, but some existing servers run on crazy port numbers.
-
Problem is, when the server sends a heartbeat to the server on whatever particular random port it may be, that port will be open for responses, so if I query it, chances are, it will all work OK. I've considered restricting allowed port ranges to like 279XX, but some existing servers run on crazy port numbers.
Yeah, I understand, but maybe removing stale servers a little quicker would be better.