Lan List vs. Rcon ?

[Lord_Palethorn]

Hi,

I have a dedicated server installed on a Debian linux. The server will be used on a LANParty, so it's not for internet use.

When I Boot it up with the next command:

./srcds_run -game cstrike -autoupdate +maxplayers 9 +map de_dust2

I get the server in my LAN list, but the RCON does NOT work (unable to connect to xxx.xxx.xxx.xxx)

When I add +IP 192.168.1.9 in my command, the RCON works, but the server will not be found in the lan list anymore :s

Also, when I change map with the command "map de_dust2" all clients got disconnected...


I hope someone can help me

grtz

[Arjen]

Does the server.cfg have sv_lan 1?
Maybe you should add -port 27015 to the startup line.

Then: connect 192.168.1.9:27015 in client console

[Lord_Palethorn]

Arjen Wrote:Does the server.cfg have sv_lan 1?
Maybe you should add -port 27015 to the startup line.

Then: connect 192.168.1.9:27015 in client console

Yes the sv_lan 1 line has been added into the server.cfg

I can connect trough it, but when I add that +IP parameter, i just don't see it in the list.. I can mannualy connect to it.. but it would be nice if my participants could find the server in their lan list..

[pengy]

Do you have a firewall? The command to change maps is changelevel de_dust2. Try it with -IP.

[Lord_Palethorn]

changlevel works, thanks.

I tried with -IP no effect.. no firewall

[pengy]

Hmmm, don't set IP, and do an rcon_address IP then rcon_password password and see what happens

[Lord_Palethorn]

still the same problem:


] rcon say test
Unable to connect to remote server (192.168.1.3:27015)
] rcon_address 192.168.1.3
] rcon say test
Unable to connect to remote server (192.168.1.3:27015)

[Forsaken]

what does your startup line look like?

[Lord_Palethorn]

Forsaken Wrote:what does your startup line look like?

./srcds_run -game cstrike +map de_dust2 -nomaster -insecure
=> In this case, the server will be found in the LAN server list, but the rcon won't work

./srcds_run -game cstrike +map de_dust2 -nomaster -insecure +IP 192.168.1.9
=> In this case, the server won't be found, but I can connect to it, and rcon works