Very nice off topic and not very contructive posting. So who are you and
what is your forum name so I can ignore you on the forums, and what is
your SteamID so I can block you.
Wait, what?
What does your linux server have to do your client machine not being
able to connect?
Have you tried checking your cables? Maybe you have a bad internet
connection and it's fouling up your steam auth ... Try calling you cable
company and tell them your screen is fuzzy, that should get them out to
check on stuff quicker.
-mauirixxx
- Sent from my #hlserveradmins IRC fanboyism
-Original Message-
From: hlds-boun...@list.valvesoftware.com
[mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Daniel
Reinhardt
Sent: Thursday, February 19, 2009 12:00 PM
To: Half-Life dedicated Win32 server mailing list
Subject: Re: [hlds] TF2 Issue Unable to Connect: Engine Error
Yes, but prior to the 16th and 18th updates this ran perfectly fine. I
know about the +clientport launch option, and that doesn't even work.
So far I have seen only one person connect.
When I try to join other servers, okay this is bizarre when I stop HLDM
Server on my machine I am playing from it works. When I run the HLDM
Server
TF2 fails to load up.
No other games have conflicts or issues with this but TF2. I can host
HLDM on the same machine and play other games like DoD:S and CSS just
fine, and I can also play Left 4 Dead just fine.
So something in the client or server update is causing this issue. TF2
ignores the launch option of +clientport to use a different client point
then 27015. I have TF2 listening on Port 27017.
And when I have HLDM Off this is the error I get:
/snip
sr...@capricorn:~/srcds/source/orangebox$ ./srcds_run +map cp_dustbowl
+port
27017 +ip 192.168.1.2
Auto detecting CPU
Using SSE2 Optimised binary.
Server will auto-restart if there is a crash.
Console initialized.
Game.dll loaded for Team Fortress
Particles: Missing 'particles/error.pcf'
maxplayers set to 24
Unknown command port
Unknown command startupmenu
Network: IP 192.168.1.2, mode MP, dedicated Yes, ports 27017 SV / 27005
CL SOLID_VPHYSICS static prop with no vphysics model!
(models/props_foliage/grass_02_cluster01.mdl)
ConVarRef room_type doesn't point to an existing ConVar
exec: couldn't exec skill1.cfg
Executing dedicated server config file
Spawnpoint at (2472.00 -1616.00 -124.00) is not clear.
Spawnpoint at (2400.42 -1622.53 -124.00) is not clear.
Spawnpoint at (2576.61 -1624.86 -124.00) is not clear.
Spawnpoint at (2425.47 -1506.63 -124.00) is not clear.
Spawnpoint at (2520.00 -1592.00 -124.00) is not clear.
Spawnpoint at (2576.61 -1547.52 -124.00) is not clear.
[S_API FAIL] SteamAPI_Init() failed; unable to update local steamclient.
Continuing with current version anyway.
exec: couldn't exec server.cfg
exec: couldn't exec cp_dustbowl.cfg
Adding master server 68.142.72.250:27011 Adding master server
69.28.140.247:27011 Connection to Steam servers successful.
VAC secure mode is activated.
Client Cryptodan connected (71.178.174.178:27005).
Dropped Cryptodan from server (No Steam logon
/Snip
At the No Steam Logon is when my TF2 just causes my screen to flash and
flicker and TF2 consumes ram at about 16Megs a second.
--
From: Rick Payton r...@mai-hawaii.com
Sent: 19 February, 2009 21:33
To: Half-Life dedicated Win32 server mailing list
hlds@list.valvesoftware.com
Subject: Re: [hlds] TF2 Issue Unable to Connect: Engine Error
Wait now I'm more confused about what's going on.
You run a TF2 server on the same lan. Got it. I think Steve's response
is what threw me off, until I read you're also running a hldm server
under windows. IS that being run on the same computer you're trying to
PLAY tf2 from? Color me confused
-mauirixxx
- Sent from my #hlserveradmins IRC fanboyism
-Original Message-
From: hlds-boun...@list.valvesoftware.com
[mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Daniel
Reinhardt
Sent: Thursday, February 19, 2009 10:40 AM
To: Half-Life dedicated Win32 server mailing list
Subject: Re: [hlds] TF2 Issue Unable to Connect: Engine Error
The server is on an entirely different machine. Located on the same
network. The client is on my Computer and its throwing that error up
on every TF2 server I try to connect too.
I am running an HLDS Windows Server for regular Half-Life Deathmatch,
but I tried adding +clientport 27017 and so on and so forth to the
launch options and nothing. This is only after the last 2 updates.
--
From: Rick Payton r...@mai-hawaii.com
Sent: 19 February, 2009 20:29
To: Half-Life dedicated Win32 server mailing list
hlds@list.valvesoftware.com
Subject: Re: [hlds] TF2 Issue Unable to Connect: Engine Error
Well then apparently I'm living in the past. :D
I've never had to / wanted to run both
