kroko Posted February 10, 2013 Share Posted February 10, 2013 as the tittle says vac sometimes automaticly disables it self on some game servers (css) atm it is disabled on one of my customers server. no matter what i do the server will not start up with vac on. Do anyone of you encounter the same problem? it is starting to annoy me alot that vac automaticly disables/enables at will. Thanks in advance kroko Link to comment Share on other sites More sharing options...
adamnp Posted February 10, 2013 Share Posted February 10, 2013 start the server in and use -condebug and it will write everything from console to console.log In that file, it should list 'connecting to valve servers...blah blah' 'connecting to vac servers....blah blah' It should tell you the error there, if there is an error. If there isn't an error, then either you don't have the proper ports open to the firewall, or your ip is blacklisted for some reason. -Adam Link to comment Share on other sites More sharing options...
kroko Posted February 11, 2013 Author Share Posted February 11, 2013 (edited) This is what console.log says. i cant really see any problem in that? maxplayers set to 16 No '-replayserverdir' parameter found - using default replay folder. Unknown command "r_decal_cullsize" maxplayers set to 16 'banned_user.cfg' not present; not executing. 'banned_ip.cfg' not present; not executing. maxplayers set to 17 (extra slot was added for SourceTV) WARNING: NNET_OpenSocket: bind: WSAEACCES Network: IP 178.63.21.23, mode MP, dedicated Yes, ports 27015 SV / -1 CL L 02/11/2013 - 09:09:58: -------- Mapchange to de_dust2 -------- 'banned_user.cfg' not present; not executing. 'banned_ip.cfg' not present; not executing. maxplayers set to 17 (extra slot was added for SourceTV) SourceTV broadcast active. The problem is somewhere in tcadmin, when i startup the server without tcadmin then vac works fine..... Edited February 11, 2013 by kroko Link to comment Share on other sites More sharing options...
CloudCUBE Posted February 13, 2013 Share Posted February 13, 2013 what happens if you don't specify the IP in the command line? Link to comment Share on other sites More sharing options...
adamnp Posted February 20, 2013 Share Posted February 20, 2013 WARNING: NNET_OpenSocket: bind: WSAEACCES This means it cannot bind to the specific IP. This could be a permission issue, or a user issue. Try running it under an admin account, and I bet it will work. You need to find whatever permissions are wrong, and or whatever is causing it to not be able to bind properly. This is most likely causing your VAC problem. Can you post your full command line? -Adam Link to comment Share on other sites More sharing options...
LFA Posted February 21, 2013 Share Posted February 21, 2013 The few times I have seen this error the fix is to remove the IP from the command line. Link to comment Share on other sites More sharing options...
Extent Posted March 26, 2013 Share Posted March 26, 2013 As soon as I did a CSGO update it disabled VAC on one of my customers servers. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now