Launch ET server but can not connect to it and then dies


(Snow_death) #1

I run
“C:\Program Files\Wolfenstein - Enemy Territory\ETDED.exe” +set net_port 27960 +set dedicated 2 +exec server.cfg

I then get Also I am trying to connect from a internal IP I have tired Dedicated 1 and 2 I can RDP to this Windows 2003 machine so I know it’s not a network / routing issue.

ET 2.60 win-x86 Mar 10 2005
----- FS_Startup -----
Current search path:
C:\Program Files\Wolfenstein - Enemy Territory\etmain\pak2.pk3 (22 files)
C:\Program Files\Wolfenstein - Enemy Territory\etmain\pak1.pk3 (10 files)
C:\Program Files\Wolfenstein - Enemy Territory\etmain\pak0.pk3 (3725 files)
C:\Program Files\Wolfenstein - Enemy Territory\etmain\mp_bin.pk3 (6 files)
C:\Program Files\Wolfenstein - Enemy Territory/etmain


3763 files in pk3 files
execing default.cfg
couldn’t exec language.cfg
couldn’t exec autoexec.cfg
Hunk_Clear: reset the hunk ok
…detecting CPU, found Intel Pentium III
Bypassing CD checks
Found high quality video and fast CPU
— Common Initialization Complete —
Winsock Initialized
Opening IP socket: localhost:27960
Hostname: server-cln-01
IP: 172.16.4.118
Working directory: C:\Program Files\Wolfenstein - Enemy Territory
execing server.cfg
dedicated is read only.
sv_maxclients will be changed upon restarting.
execing preset_high.cfg
PunkBuster Server: pb_sv_SsNext = 893285 (0 to 999999)
PunkBuster Server: pb_sv_LogNext = 3 (1 to 999999)
PunkBuster Server: 0 Power Players loaded from C:\Program Files\Wolfenstein - Enemy Territory\pb\pbpower.dat
PunkBuster Server: 0 PB Rcon Filters loaded from C:\Program Files\Wolfenstein - Enemy Territory\pb\pbrcon.dat
PunkBuster Server: 0 Map lines loaded from C:\Program Files\Wolfenstein - Enemy Territory\pb\pbsvmaps.cfg
PunkBuster Server: Attempting to resolve master6.evenbalance.com
PunkBuster Server: Resolved to [69.59.149.240]
PunkBuster Server: Received Master Security Information
PunkBuster Server: PunkBuster Server (v1.250 | A1364 C1.274) Enabled
PunkBuster Server: PunkBuster Server (v1.250 | A1364 C1.274) Enabled
Hitch warning: 534 msec frame time
PunkBuster Server: Game Version [ET 2.60 win-x86 Mar 10 2005]
Hitch warning: 786 msec frame time

it sits there for about 2 minutes and the screen goes away.

MY ET server.cfg follows
//Enemy Territory Server Config

//General Settings
set sv_hostname “^1S^7now^1D^7eath ET PUB XP SAVE - org Map’s”
set dedicated “2”
set sv_maxclients “26”
set g_password “”
set sv_privateclients “4”
set sv_privatepassword “privpass”
set rconpassword “"
set refereePassword "

set server_motd0 “--------------------------------------”
set server_motd1 “^1W^7elcome ^1T^7o”
set server_motd2 “^1S^7now_^1D^7eath’s”
set server_motd3 “Dedicated XP PUB server”
set server_motd4 “--------------------------------------”
set server_motd5 “20Mbit - 2.4Ghz / 1.5Gb Ram / ^1For Rent”
set sv_maxRate “0”
set sv_dl_maxRate “42000”
set sv_allowDownload “1”
set sv_wwwDownload “0”
set sv_wwwBaseURL “”
set sv_wwwDlDisconnected “0”
set sv_wwwFallbackURL “”
set sv_pure “1”
set developer “0”
set g_gametype “4”
set net_ip “localhost”
set net_port “27960”

//Last Man Standing Settings
set g_lms_teamForceBalance “1”
set g_lms_roundlimit “3”
set g_lms_matchlimit “2”
set g_lms_followTeamOnly “1”
set g_lms_lockTeams “0”

//Vote Settings
set g_allowVote “1”
set vote_limit “5”
set vote_percent “51”
set vote_allow_comp “0”
set vote_allow_pub “0”
set vote_allow_kick “1”
set vote_allow_map “1”
set vote_allow_matchreset “1”
set vote_allow_mutespecs “1”
set vote_allow_nextmap “1”
set vote_allow_referee “0”
set vote_allow_shuffleteams “1”
set vote_allow_swapteams “1”
set vote_allow_friendlyfire “0”
set vote_allow_timelimit “0”
set vote_allow_warmupdamage “0”
set vote_allow_antilag “0”
set vote_allow_balancedteams “0”
set vote_allow_muting “1”

//Misc Settings
set g_heavyWeaponRestriction “50”
set g_antilag “1”
set g_altStopwatchMode “0”
set g_autofireteams “1”
set g_complaintlimit “6”
set g_ipcomplaintlimit “3”
set g_fastres “1”
set g_friendlyFire “1”
set g_minGameClients “2”
set g_maxlives “0”
set g_alliedmaxlives “0”
set g_axismaxlives “0”
set g_teamforcebalance “1”
set g_noTeamSwitching “0”
set g_voiceChatsAllowed “4”
set g_doWarmup “1”
set g_warmup “22”
set g_spectatorInactivity “0”
set sv_floodProtect “1”
set sv_minping “0”
set sv_maxping “320”
set match_latejoin “1”
set match_minplayers “2”
set match_mutespecs “0”
set match_readypercent “75”
set match_timeoutcount “1”
set match_warmupDamage “1”
set team_maxplayers “0”
set team_nocontrols “0”
set com_watchdog “60”
set com_watchdog_cmd “”
set g_useralliedrespawntime “”
set g_useraxisrespawntime “”
set g_covertopsChargeTime “”
set g_engineerChargeTime “”
set g_LTChargeTime “”
set g_soldierChargeTime “”
set g_medicChargeTime “”
set g_disableComplaints “7”
set g_gravity “800”
set g_inactivity “0”
set g_knifeonly “0”
set g_log “SnowD”
set g_speed “320”

//PunkBuster Settings
pb_sv_enable
set PB_SV_MsgPrefix “^3De-Punker”
set PB_SV_Sleep “60”
set PB_SV_KickLen “2”
set PB_SV_CvarFreq “6”
set PB_SV_MinName “0”
set PB_SV_MaxDlRate “1”
set PB_SV_MaxConDls “3”
set PB_SV_AutoSs “0”
set PB_SV_AutoSsFrom “60”
set PB_SV_AutoSsTo “1200”
set PB_SV_CQC “1”
set PB_SV_ScoreKick “0”


(Snow_death) #2

The last message that shows up says Watch dog will be enabled in 4 seconds and then ET console colses


(Ragnar_40k) #3

You need to specify a valid map/campaign to run, either in the server config or via command line.

dedicated is read only.

The dedicated cvar has to be set via command line.

http://rtcw.jolt.co.uk/content/enemy_territory/server_guide/index.html


(nUllSkillZ) #4

As far as I can see there isn’t a campaign or map specified in the server.cfg.


(Snow_death) #5

Here is the latest message when I just click ETDED.exe… it closes after 4 seconds

ET 2.60 win-x86 Mar 10 2005
----- FS_Startup -----
Current search path:
C:\Program Files\Wolfenstein - Enemy Territory\etmain\pak2.pk3 (22 files)
C:\Program Files\Wolfenstein - Enemy Territory\etmain\pak1.pk3 (10 files)
C:\Program Files\Wolfenstein - Enemy Territory\etmain\pak0.pk3 (3725 files)
C:\Program Files\Wolfenstein - Enemy Territory\etmain\mp_bin.pk3 (6 files)
C:\Program Files\Wolfenstein - Enemy Territory/etmain


3763 files in pk3 files
execing default.cfg
couldn’t exec language.cfg
execing profiles/SnowD/etconfig.cfg
couldn’t exec autoexec.cfg
Hunk_Clear: reset the hunk ok
…detecting CPU, found Intel Pentium III
Bypassing CD checks
— Common Initialization Complete —
Winsock Initialized
Opening IP socket: localhost:27960
Hostname: server-cln-01
IP: 172.16.4.118
Working directory: C:\Program Files\Wolfenstein - Enemy Territory
PunkBuster Server: pb_sv_SsNext = 893285 (0 to 999999)
PunkBuster Server: pb_sv_LogNext = 7 (1 to 999999)
PunkBuster Server: 0 Power Players loaded from C:\Program Files\Wolfenstein - Enemy Territory\pb\pbpower.dat
PunkBuster Server: 0 PB Rcon Filters loaded from C:\Program Files\Wolfenstein - Enemy Territory\pb\pbrcon.dat
PunkBuster Server: 0 Map lines loaded from C:\Program Files\Wolfenstein - Enemy Territory\pb\pbsvmaps.cfg
PunkBuster Server: Attempting to resolve master7.evenbalance.com
PunkBuster Server: Resolved to [216.240.146.139]
PunkBuster Server: PunkBuster Server (v1.250 | A1364 C1.274) Enabled
PunkBuster Server: Game Version [ET 2.60 win-x86 Mar 10 2005]
Hitch warning: 1085 msec frame time
:angry: Watch dog will trigger in 4 seconds


(El Stupido) #6

I have no idea why it dies (windows server… yuck… sorry) but “Opening IP socket: localhost:27960” seems a bit fishy to me. You could try to force the ip by using +set net_ip x.x.x.x on the command line.


(kamikazee) #7

localhost:27960 just means that the server runs on the local PC, port 27960. If another PC can reach your PC, it works.

The watchdog timer is a special feature which checks every x seconds (as set in “com_watchdog”) to see if a map is running. If it isn’t, it will execute the command specified in “com_watchdog_cmd”. If that one is empty, it will kill the server.

Now, it seems you aren’t starting a map (or a campaign in your case) so the watchdog time kills the server after 60 seconds.


(El Stupido) #8

Hmm i thought it was the server log and it was binding the socket to 127.0.0.1 which would mean he could only connect it from the mashine the server is running on… but maybe i should just shut up and drink another 5 cups of coffee xD


(Snow_death) #9

That is what it was thank you Ragnar