Connection to the Steam VAC servers could not be made

[WillsJB]

Hey guys,

I'm in the process of setting up a new server for beta testing Jailbreak: Source, an Orange Box mod. After a few days of messing around I've managed to get the server running, however, when anyone connects to it, after around 2 minutes they get booted with the error message:

"Connection to the Steam VAC servers could not be made."

The server is seemingly contacting the VAC servers as it comes up with the little badge in the server browser, and states its VAC Secure. I don't have access to the console though, as it's a server being run by someone else. I'm just issuing instructions based on a local model I've been using.

This issue affects everyone who joins the server, so I'm 90% sure it isn't a client issue.

Can anyone point me in the right direction?

[St1flus]

If it's a third party mod I don't think you can make it VAC secure because you have already changed the dynamic-link libraries, VAC for example, finds if the .dlls are edited for a specific game like CSS, it thinks there is cheats, which obviously should be because why else would you edit one? Anyhow, for 3rd party hosting, it has to be non VAC secure, unless you contact valve to release your mod so they can make it VAC secure.

I'm pretty sure that's why, if not, sowy

[pengy]

Which ports do you have open?

[WillsJB]

Oddly enough, the solution in the end was to change the Steam.inf file on the server to appID=215 rather than 218.

The downside of this, is that noone can connect via the Steam Server Browser, as it loads the wrong client libraries. However, they CAN join via the ingame browser this way.

If it's set to 218, they can join via the Steam Server Browser, but it kicks them after 2-3 minutes with the error: "Connection to the Steam VAC servers could not be made."

I'm trying some combinations now, I'll update this thread if I find a solution.

[St1flus]

Remove the VAC you can't use it, see, different keys / libraries