/rcon status not working

[Plasma]

has anyone else had this problem? /rcon status not working anymore? it use to work fine, but for some reason stopped. any ideas on how to fix this?

[holy_moses]

Plasma,

Make sure your not getting any error messages like "Bad Rcon Password". Then, try sending the command a few times in a row.

-Moses

[Willum]

On my 1.1 servers, (on different Linux boxes, one is TDM and one is RE/SD, both maxclients 22) when the server gets to 18 or more players, a status fails to produce a response. At 17 players or less, status responds fine. Not sure if 1.2 had an effect yet.

[Aces]

this is a bug

Mohaa has it

they still havent fixed it

[Cobra]

i got that bug myself today....
I do not know how many that was in the server.
beacause i was just using my servertool to look at the server.
And it did not get the rcon status to pass.

Do anyone know whats makes this problem ?

[ColdLogic]

I'm almost positive based on another post here somewhere that it has to do with the CR (carriage return) character, otherwise known as the 'enter' key.

The only way around this that I have heard of and successfully used is to bind a key to 'rcon status'

Then I hit the key, pull down the console and I have status there.

so I used: /bind = "rcon status"

Sometimes it still doesn't work and I had to rebind the key or hit the key a few times before status would come up. But it works the majority of the time.

[kasper501]

all i know, is im having the same issue on my 36 player linux dedicated server.

when the server is half empty or half full it works everytime. Once we get about 20 players or more, rcon status doesnt work, however i will try resending the command multiple times and see if that works.

kasper

[2drunk2funk]

This is an annoying bug
I have written a Rcon4Cod Windows GUI with all the Cod settings, modes, weapons and player list/kick/ban
The populate from server does not get a response when the server is pretty full which kinda sucks

It needs fixing

[SNYPE]

A problem has been found with fragmented UDP packets that can cause this.
Check this thread for the answer:
http://www.codadmin.com/nuke/modules.php?name=Forums&file=viewtopic&t=1423&postdays=0&postorder=asc&start=15