Server Box troubles
- Thread starter groupie
- Start date
I would assume if you have not gotten a reply to help you with the issue you're having, those that have viewed this thread do not know how to resolve your issue or don't have enough experience on the matter to assist. It is better to not give advice than to give bad advice if you get my drift. 
It might be worth tracking down who does the server management of eGO servers and see if they can assist you. Before you do that I would check for stickies that might be able to help you with this. Here is the link to the sticky in this tech help forum: Create your own server. I've never done this before but I hope that at least gets you going in the right direction. :thumbup:
It might be worth tracking down who does the server management of eGO servers and see if they can assist you. Before you do that I would check for stickies that might be able to help you with this. Here is the link to the sticky in this tech help forum: Create your own server. I've never done this before but I hope that at least gets you going in the right direction. :thumbup:
I haven't personally ran a CS:S server, however I have built a CentOS 6 based Cod4 server. The primary thing you need to determine is how are users going to connect to this second server? Are you going to bring up a second static IP, or are you going to utilize the same IP? If you are using the same server IP as your existing server, then you need to configure your new server to use a different port. ( Example for cod4: IP:28960; IP:28961; IP:28962; etc. for each server )
Ensure your iptables rules ( firewall ) allow traffic to flow on your newly assigned ports. Start your second daemonized server process with the new configuration, and you should be golden.
If your having issues starting a second server process, that's where I can't help you. In the call of duty world, each server has a "game folder" that contains the mods, configs, game files, etc. You just duplicate it, execute the same dedicated server program with the newly modified command line and your set.
Ensure your iptables rules ( firewall ) allow traffic to flow on your newly assigned ports. Start your second daemonized server process with the new configuration, and you should be golden.
If your having issues starting a second server process, that's where I can't help you. In the call of duty world, each server has a "game folder" that contains the mods, configs, game files, etc. You just duplicate it, execute the same dedicated server program with the newly modified command line and your set.
Thanks very helpful!:thumbup:
Like I said before, I haven't started a CS:S specific server before... If they have a consistent port convention, you may need to spend some time on google
The port you choose really shouldn't matter, as long as it's not mainstream ( 80, 8080, 22, etc. etc. )
Open up 27016 UDP/TCP via iptables ( firewall )
Start a second server daemon with the port config 27016, and see what happens...
You have to think of it as a "Server <----> Client" type setup, you specify which port your server listens on and as long as each client is told to connect with that port... the same connection information should be transferred to the listener. ( This is assuming your firewall is configured correctly )
The port you choose really shouldn't matter, as long as it's not mainstream ( 80, 8080, 22, etc. etc. )
Open up 27016 UDP/TCP via iptables ( firewall )
Start a second server daemon with the port config 27016, and see what happens...
You have to think of it as a "Server <----> Client" type setup, you specify which port your server listens on and as long as each client is told to connect with that port... the same connection information should be transferred to the listener. ( This is assuming your firewall is configured correctly )
theres bound to be some relevant information in there 
Did exactly what you said, hmmm.
