PDA

View Full Version : DEDICATED SERVER CAN BE SEEN ON MOHAA BUT CAN NOT JOIN


Green_Falcon
12-31-2002, 03:08 AM
hey all i am running a dedicated server from my comp, as a test, i have been able to get it to show up on mohaa but it is always full, i am experienced with the cfg files and that is not the problem, the same cfg file runes fine for my other server, could this mean that my firewall is not allowing info in or out, but just allowing people to see my server??

SNYPE
12-31-2002, 12:08 PM
Acouple of questions:

You say that its full? What is the exact statement you get when trying to connect.
You get it to "show up on Mohaa", what do you mean? the ingame browser, GSpy??
What is the network that you are running the server and the client on, are they both on the same lan or?
Can anyone else connect to it?

Green_Falcon
12-31-2002, 02:39 PM
i saw it on the ingame browser and on the all seeing eye. I had this working a month ago but forgot how to do it, when i look at the game it shows that all slots are full and when you connect it says server full. I know it is not full, and i do not have any private clients in my cfg file

Kokkor
01-01-2003, 11:45 PM
Server is full? The number of private slots is equal than max clients? In this way alwais need password to connect.

Server is full? El numero de slots privados es igual que el de maximos clientes? En ese caso, siempre necesitaras poner el password para conectar.

Floyd
01-02-2003, 12:14 AM
Have you tried "restart"......just a thought.

Green_Falcon
01-02-2003, 02:14 PM
Yeh ive tried a restart, it has to be my firewall.

FiTs
01-04-2003, 04:59 AM
i think it might be the fire wall. i tryed to asign a port for moh but couldnt. i have to go to dmz and open the port all the way.

SNYPE
01-04-2003, 01:25 PM
Green Falcon, I went back to the post you made about your map problem before you changed providers and your cfg file has this in it:
seta sv_maxclients "16"
seta sv_privateClients "16"

If you are still using that cfg, it will always be full unless you connect using the privateClient password.