Rcon Login Issues

[Glj12]

This is what happens when I login and attempt to change parameters with rcon, and yes, the password is correct. Yes, I am connected to the game locally, and that is the proper address.

] rcon_address 172.16.1.35
] rcon_password passwordhere
] rcon sv_gravity 200
Unable to connect to remote server (172.16.1.35:27015)

The rcon port is open. It has never done this before, what is the matter?

[Drocona]

If you are connected to the game locally you should use the local IP adress not the external

[get]

if you are conected to server i mean "in-game" and open console type this:
rcon_password XXXXXXXXX
rcon test
rcon status

now if it answers with server details theres no problem.
nnormally you dont need to say the game where the server is if you use rcon commands, the client determines by itself that the needed server is the connected one.

regards.

[Glj12]

Drocona Wrote:If you are connected to the game locally you should use the local IP adress not the external

Unable to connect to remote server (172.16.1.35:27015)

Does this address, in all honesty, look like its public to you? 172 and 192 are internal usually.

And in response to the other guy, I'll try that rcon status.

Anyway, *update* it still says the same thing. How could it not be connecting, wth?

[cryotek]

Actually, AOL normally owns 172.*

[Glj12]

cryotek Wrote:Actually, AOL normally owns 172.*

I've seen MANY network setups in my life, and it is almost always 172 or 192 for internal. Usually, the number that proceeds 172 is a number b/t 1-20, thus not being ownership to AOL...

Let's have a helpful solution to my question. Relevancy is the key in this case.

[candy-man]

172.16.0.0/12, 192.168.0.0/16 and 10.0.0.0/8 are the blocks allocated for private LANs.

As far as the error, I usually have seen that when I did not use the ip flag when starting the server. If you type "status" in the server's console, what does the IP list as? 127.0.0.1?

[Drocona]

lol my apologies, I've never seen 172.* in my whole life, always 192.* and 10.* so I figured it was a WAN ip.

Anyways do what candy man says, see if the ip is bound correctly to the server

[Glj12]

Drocona Wrote:lol my apologies, I've never seen 172.* in my whole life, always 192.* and 10.* so I figured it was a WAN ip.

Anyways do what candy man says, see if the ip is bound correctly to the server

No worries dude. Anyway, it says that it cannot connect even when I type status... I think this started happenning after I updated mani admin maybe? Where could I look for blocked IP's like candy-man is talking about? I'll look around for the time being for anything along those lines, thanks. Also, when starting the server, should I add -ip 172.16.1.35:27015 or something like that?

[get]

-ip 172.16.1.35 -port 27015

on startup

[cryotek]

Because linux has loopback with 127.0.0.1 i think srcds will bind itself to that. so using +ip 172.16.1.35 should fix it. unless you bring down loopback.