"Unable to connect to remote server..."

[Xade]

rcon trouble...

server restarts, but all rcon power is lost. a manual closing down is the only solution.

any ideas on a PERMANENT fix?! :(

example:

rcon_password **********
rcon say rar
Unable to connect to remote server (xx.xxx.xxx.xxx:xxxxx)

20:20:20 HLSW NOTE: Connecting to xx.xxx.xxx.xxx:xxxxx ...
20:20:41 HLSW ERROR: Connection failed (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. )




>:(

[Buddar]

im having exactly the same problems with it same errors the server rcon is definiatly correct too

22:05:53 HLSW ERROR: Connection failed (No connection could be made because the target machine actively refused it. )
22:12:07 HLSW NOTE: Connecting to 82.197.67.132:27020 ...
22:12:08 HLSW ERROR: Connection failed (No connection could be made because the target machine actively refused it. )
22:12:49 HLSW NOTE: Connecting to 82.197.67.132:27020 ...
22:12:50 HLSW ERROR: Connection failed (No connection could be made because the target machine actively refused it. )
sorry about ip direct paste

[wecojack]

Unable to connect to remote server (xx.xxx.xxx.xxx:xxxxx)

because +ip "ip" was not stated but that is also screwed up.

[showdax]

I've posted about this in the past and have gotten no useful replies about it. Not even an acknowledgement that it's being worked on by developers.

Previous thread: http://www.steampowered.com/forums/showthread.php?s=&threadid=162650 (If a mod sees that, could you move it to this forum? It no longer belongs in the forum that it's in.)

Edit: Wait, are you sure this has anything to do with Source DS? I don't use HLSW, but it looks like it's for HL1 only, not Source-based games.

[Spinner]

I added this to my start command line and It works fine for me

+rcon_password yourpassword

[Xade]

you're definately using linux though, Spinner?

rcon does 'WORK', but only after the server has been totally shut down and restarted and configged.

it seems rcon expires after about 10 hours or something.

worst part is... NOBODY seems to acknowledge this as the MASSIVE problem that it is.

Valve are severely limiting their userbase if they restrict their admins to only using Windows hosts.

worse still, there hasn't even been an official response to what is probably one of the single biggest problems with their product at this time.

a POSSIBLE solution is to have a third party computer on a permanent connection connected via HLSW to the server 24/7. but even this solution is unreliable.

if the community had any answer to this massive issue, they'd have given it by now. yet instead we have the (usual) Linux Silence here...

[stryfetew]

Yeah, that's pretty bad us linux admins are held up hands tide behind our backs. We see a hacker on the server and can't do a thing about it.

[PiTaGoRaS]

Yep, the rcon socket dies after a few hours/days and its impossible to connect again unless the server is restarted.

Very sad that VALVe hasn't even acknowledged it when it was a problem already present in the beta srcds.

[Spinner]

Yes Im using Fedora Core 2 and Ive never had a problem.As long as I add +rcon_password to the command line.And I forgot 1 time to do It and couldnt control the server from In game so I used this.


http://www.cs-sourcemod.com/invision/index.php?act=Attach&type=post&id=2


This allows you to kick ban and chat with players In game on Counter-Strike Source.

[wecojack]

Originally posted by Xade
you're definately using linux though, Spinner?

rcon does 'WORK', but only after the server has been totally shut down and restarted and configged.

it seems rcon expires after about 10 hours or something.

worst part is... NOBODY seems to acknowledge this as the MASSIVE problem that it is.

Valve are severely limiting their userbase if they restrict their admins to only using Windows hosts.

worse still, there hasn't even been an official response to what is probably one of the single biggest problems with their product at this time.

a POSSIBLE solution is to have a third party computer on a permanent connection connected via HLSW to the server 24/7. but even this solution is unreliable.

if the community had any answer to this massive issue, they'd have given it by now. yet instead we have the (usual) Linux Silence here...

use -remember_password the first time you connect and update to keep the user name and password saved on your machine. Valve has thought of everything.

edit: with rcon you have to establish both +ip and +port with local address to get rcon established without problems on some computers. worked for me