Digital Paint Discussion Board

Paintball 2: The Game => Server Discussion => Topic started by: the-elementalist on August 25, 2007, 11:49:25 PM

Title: Killing a server
Post by: the-elementalist on August 25, 2007, 11:49:25 PM
I've noticed that there a lot of servers on Paintball that come on the server list for a few hours at max and then drop of the list.

Most of these are Australian servers, and I have the capability to run a small, say 8 player server from my computer, my only concern is that I don't want it running forever. I want to be able to shut it off when I'm not at home.

In short; After I've made my server, how can I get it off the web. Also, is it the same process to get it back up?

FYI: I have read the server guide.

EDIT: Sorry, one last thing, server player limit, where do I put that in?
Title: Re: Killing a server
Post by: BuLLzEyE on August 26, 2007, 12:36:59 AM
all you have to do is exit out of your server (the black box) when ur done with it    ;D
Title: Re: Killing a server
Post by: BuLLzEyE on August 26, 2007, 12:38:03 AM
and for your player limit, i just set mine under "start new game" and it works on my dedicated server
Title: Re: Killing a server
Post by: the-elementalist on August 26, 2007, 02:08:56 AM
Cheers Bullzeye, ill give it a shot 2morrow, for now my eyes are about to sh-
Title: Re: Killing a server
Post by: KiLo on August 26, 2007, 09:05:56 AM
and for your player limit, i just set mine under "start new game" and it works on my dedicated server

Strange but there is actually  a place to set the player limit in the server.cfg file.
Title: Re: Killing a server
Post by: the-elementalist on August 29, 2007, 02:50:33 AM
Okay, here's something fun for you guys to try and work out.

I've been to IP chicken, and got my I.P address, and that appears on the dp serverlist but for some bizzare reason my server will not appear on the server browser.

I have the public setting in server.cfg set to 1, I have that 'black box' up, and it the server will appear when I load the game normally, however i got a friend of mine to try and connect, yet it would not appear anywhere.

Please help.
Title: Re: Killing a server
Post by: cusoman on August 29, 2007, 11:33:27 AM
Well whenever i host a server it usually takes about 10 mins or so for it to show up on the list. Also sometimes you cant see your own server on the list. In some instances my server never showed up on the list untill another one started up because sometimes,at least my server list, never shows the bottom server.
Title: Re: Killing a server
Post by: FlaMe on August 29, 2007, 11:36:58 AM
it doesnt show up until the server sends a heartbeat.
 
Open port 27910 on your firewall and router and youre in business
Title: Re: Killing a server
Post by: KiLo on August 29, 2007, 11:39:51 AM
it doesnt show up until the server sends a heartbeat.

Wrong it shows up once it sends a ping to the master server at dplogin.com.

Elementalist when you open your server try typing exec myserver.cfg or whatever you named you server.cfg file. That should fix the problem.
Title: Re: Killing a server
Post by: FlaMe on August 29, 2007, 11:55:42 AM
Wrong it shows up once it sends a ping to the master server at dplogin.com.

Elementalist when you open your server try typing exec myserver.cfg or whatever you named you server.cfg file. That should fix the problem.

Kilo shut up, Hearbeats send the pings. And that is deff not the problem. The black cmd box is up and the other IP hes getting in game is probably his local ip ie. 192.168.1.1 or something. He needs to open the ports on his firewall and router and than allow paintball2.0 through the ports.

gg
Title: Re: Killing a server
Post by: KiLo on August 29, 2007, 12:03:28 PM
Flame how many servers have I helped set up for people? Too many is how many so I know what I am talking about, so go to your corner and be quiet.
Title: Re: Killing a server
Post by: jitspoe on August 29, 2007, 02:44:01 PM
Flame is correct on this matter.  The server shows up on the list when it sends a heartbeat, which contains more info than just a ping.

the-elementalist: Is the port on the server list correct or is it some random number?  If it's random, you need to forward your ports correctly on the router.  If it's correct, you may need to adjust your firewall settings.
Title: Re: Killing a server
Post by: FlaMe on August 29, 2007, 08:23:16 PM
Flame is correct on this matter.  The server shows up on the list when it sends a heartbeat, which contains more info than just a ping.


Burnt KiLo... Score 1 for the FlaMe

Go back to under your bridge, troll =P
Title: Re: Killing a server
Post by: the-elementalist on August 30, 2007, 02:31:55 AM
Okay time to admit I had no idea what was going on during that argument(?) with Kilo and Flame and they kinda lost me. I don't mean to sound pathetic, but baby steps would be nice.

Now, I got the stuff about sending heartbeats, I saw that happen and im pretty sure it still didn't work at that point.

So jits, I'm gonna go through what you said bit by bit.
a)My firewall is disabled.
b)Port number on the server list?? And what was that flame went on about 27910? The only thing im sure about is my ip address and that's about it.

It might be easier to communicate on that IRC thing... if that's possible I've only looked at it once, so you guys tell me what's best.
Title: Re: Killing a server
Post by: FlaMe on August 30, 2007, 09:56:01 AM
in all honesty IRC will make your life easier.

Go to www.portforward.com and look for your router. I'm assuming you have one. Follow the steps neccessary to allow UDP packets to flow in and out of ports 27910.
 
The firewall, dont disable it just because you don't know what kinds of viruses you could be allowing in. Look to see if you can allow ports 27910 to be open for UDP exchange.
 
Any questions look for me in #paintball or #apoboc on IRC
Title: Re: Killing a server
Post by: KiLo on August 30, 2007, 11:10:57 AM
I am still saying that it may be as simple as just typing "exec myserver.cfg" in the black box.
Title: Re: Killing a server
Post by: FlaMe on August 30, 2007, 11:47:30 AM
he'd be getting an error in there like unable to exec "myserver.cfg or server.cfg" in the box though. and he said he could play on it but his friends can't...
 
Deff not the prob kilo.
Title: Re: Killing a server
Post by: KiLo on August 30, 2007, 12:04:56 PM
he'd be getting an error in there like unable to exec "myserver.cfg or server.cfg" in the box though. and he said he could play on it but his friends can't...
 
Deff not the prob kilo.

Flame quit talking. It could be the problem. I have had my server heartbeat and not be on the list. And when I put exec myserver.cfg it magically appears on the list. My thoughts are that putting exec myserver.cfg is sort of like a reset function.

You may also want to try typing setmaster dplogin.com directly into the black box.

Elementalist out of curiousity what is the name of your server so I can look for it and see if it is up.
Title: Re: Killing a server
Post by: FlaMe on August 30, 2007, 12:11:02 PM
he can tell himself if his server is up by seeing if its on the serverbrowser list. Locals dont show up there.
 
I'm telling you based off what he's told us, he doesnt have his ports forwarded correctly
Title: Re: Killing a server
Post by: jitspoe on August 30, 2007, 09:57:45 PM
If you look at the serverlist.php, you should have <your ip>:27910.  If you have <your ip>:<random number> your port isn't forwarded correctly.
Title: Re: Killing a server
Post by: the-elementalist on August 31, 2007, 04:39:07 AM
Flame, I am in your debt  :D!

The site is now on sever browser! I'm currently bugging the living heck out of my mate to try and connect but so far all seems good.

Kilo, as for what you said, that helps me get my severs heartbeat going, so although you helped (which I'm also thankful for), Flame really was right.

For the record, the sever name is [{AAA}] Clan Sever Public but since i come from the land down under, odds are I'll never have the server up when you're on  ;)

EDIT: Okay... what the hell?
Without doing anything to that black box, my sever was on serverbrowser for a while, then I closed severbrowser and when I came back it was gone... help?
Title: Re: Killing a server
Post by: FlaMe on August 31, 2007, 07:02:13 AM
yo elementalist. Get me on IRC and ill help you because forums are a little harder. Maybe you need to disable DHCP or something because you have a dynamic IP or something. I'm not sure.
Title: Re: Killing a server
Post by: Eiii on August 31, 2007, 07:04:51 AM
Disabling DHCP all together would be a bad idea, in my opinion, and would screw with the network for other computers. If your router doesn't support reserving IP addresses, then you should just shrink the IP range it assigns some and get the computer to use a static IP.
Title: Re: Killing a server
Post by: FlaMe on August 31, 2007, 07:06:35 AM
Eii that sounds good. I wasn't sure. When I tried to set up my router for port forwarding it told me to give the comp a Static and disable my DHCP so I went with that but a static is probably his best bet. Or maybe his config file is screwed up a little.
Title: Re: Killing a server
Post by: KiLo on August 31, 2007, 09:00:13 AM
EDIT: Okay... what the hell?
Without doing anything to that black box, my sever was on serverbrowser for a while, then I closed severbrowser and when I came back it was gone... help?

And I reiterate typing setmaster dplogin.com in the black box. For some reason the server will stop sending info to the server sometimes and this just usually restarts that process.