How do you set up a configured dedicated server in ArmA2 ???

[laggy]

Hi all,

Basic stuff here... embarrassed to ask, but here it goes:

In my own beta testing I want to try MP missions on a dedicated server.
This I can do, but I can't seem to make the config file work.
I searched around, but couldn't find an answer to my problems.

In my ArmA2server.exe shortcut properties:

Code: [Select]

"C:\BISgames\Bohemia Interactive\ArmA2Server.exe" -config=C:\BISgames\Bohemia Interactive\arma2server.cfg -mod=@Eng102

In my arma2server.cfg (a .txt document placed in my ArmA2 main directory - the path above):

Code: [Select]

passwordAdmin = "whatever"; // password to protect admin access
password= "whatever";
hostname="[Laggy's Beta Dedi]";
motd[]=
{
"You've reached Laggy's Beta Testing Server.",
};
motdInterval=1;
voteThreshold=0.33;
voteMissionPlayers=1;
checkfiles[]={};
kickduplicate=1;
equalModRequired=0;
persistent=1;
aikills="true";
class missions {};
disableVoN=1;
logFile="myLogFile";
battleye=0;
reportingIP="";

However, this config is not read, the server is called my original PC name, and you don't get a greetings message. You don't need a password to join and I can't log in as administrator at all, never get that option.

What am I doing wrong? I fear that I have created the .cfg in a bad way, writing a .txt document and naming it .cfg. When I look at the properties it is called arma2server.cfg.txt. What kind of file is needed for a server config?

I would like to limit the server so that only I can access it. When you beta test you don't want anyone coming in and screw up the test. Yesterday, when beta testing, I had internet people joining, even though I only saw my server on LAN. I want to be "left alone" when beta testing.

Is there any way to skip the annoying 60 sec wait before the voting part is over?

When I disconnect from the server, the ArmA2 client crashes, but the server stays up. If I shut down the server, the client crashes.

I run the server on the same machine as client (parallel) and my OS is Vista. Read somewhere that only XP should be used for a dedi. Is that true?


Grateful for advice my dear OFPEC friends,

Laggy

[i0n0s]

Code: [Select]

-config=arma2server.cfguse relative paths.

[laggy]

Thanks,

But I don't understand, what do you mean I have to do?

I tried:

Code: [Select]

"C:\BISgames\Bohemia Interactive\ArmA2Server.exe" -config=arma2server.cfg -mod=@Eng102Still no change.

EDIT:

Now got it to work with name and password, but as soon as I fill in the password, ArmA2 client crashes. The client freezes during the "Wait for host" screen.

Code: [Select]

"C:\BISgames\Bohemia Interactive\ArmA2Server.exe" -config=arma2server.cfg -mod=@Eng102

Code: [Select]

passwordAdmin = "xyz"; // password to protect admin access
password= "xyz";
hostname="Laggy's Beta Dedi";
motd[]=
{
"Welcome to Laggy's Beta Testing Server.",
};
motdInterval=1;
voteThreshold=0.33;
voteMissionPlayers=1;
checkfiles[]={};
kickduplicate=0;
equalModRequired=0;
persistent=1;
aikills="true";
class missions {};
disableVoN=1;
logFile="";
battleye=0;
reportingIP="";

Laggy

[hoz]

Make sure you are running the same version of server and arma2.exe client.  I know this was crashing me when I joined.

[laggy]

Thx,

But it works when non configured as in my first post, when I had screwed up the .cfg file, so it was never read. Both server and client are 1.03 (no beta).

The crash only seems to happen when a .cfg file is read.

Is Vista not working with a dedi, as written on the wiki?

Laggy

[hoz]

Hmm I also had a similar problem with the config file not being read. I thought I determined that the spaces in the folder names might be causing an issue. This was back in arma1  so I just followed the same method.
here are my settings.. notice how I've removed the spaces to the folders...

Code: [Select]

c:\bi\arma2\beta\ArmA2server.exe  -config=c:\bi\ArmA2\armaserver.cfg -mod=beta;mods\english

Code: [Select]

passwordAdmin = "zzz"; // password to protect admin access
password= "zzz";
hostname="[Uber Server]";
motd[]=
{
"You've reached the [UbEr] Server.",
};
motdInterval=1;
voteThreshold=0.33;
voteMissionPlayers=1;
checkfiles[]={};
kickduplicate=1;
equalModRequired=0;
persistent=1;
aikills="true";
class missions {};
disableVoN=1;
logFile="myLogFile";
battleye=0;


[laggy]

Well,

To clarify:

-When the .cfg file is read, server name and password working, the client freezes/crashes at the "wait for host" screen.

-When the .cfg file is NOT read, server name = my PC and no password needed, you can actually play, but anyone can also connect to your server.

I am also using VISTA.

Laggy

[hoz]

I don't see where on the biki that the server doesnt run under vista. You could also try using the arma2.exe -server  option which runs much like the dedicated server except it requires the dvd on startup(except in the betas). If you're running it on the same machine you should be ok.

[laggy]

Arma 2: You need a Microsoft Windows XP computer to run an Arma 2 dedicated server.

Here is the link to that wiki page, which talks about XP only for ArmA2 dedicated server:

http://community.bistudio.com/wiki/ArmA:_Dedicated_Server


However, it seems there is a discrepancy in the official server version and the official client version.

Client: v1.03.58627
Server: v1.03.58659

They are not coordinated exactly, even though they are both v1.03. Could this be the reason?

Thanks,

Laggy