Try IP address of config server for the -cshost parameter and see if it works. Then if the provided -csport <port> -csappname <app_name> -csuser <username> -cspassword <password> is all correct, then check SCS logs for a new mlcmd connection (Validate those credentials using CME or GA or any tool that requires authentication into Genesys Config Layer first). You should see something like this in your SCS logs which is basically the output you will also see in your command line result
17:20:47.588 Client: new client 444 connected.
17:20:47.588 Client: host name wasn't obtained. IP-address: ***.***.**.**:47240
17:20:47.589 Create CIRequester (socket: 444, name: 'mlcmd')
17:20:47.589 Trace 192.168.10.98 Solution_Control_Server GCTI-43-10400 SC Interface 'mlcmd' connected, username='default', socket=444, client's host='(***.***.**.**:47240)', client's tenant='Environment'
17:20:47.589 ### LOCAL MESSAGE#=10400, 'SC Interface 'mlcmd' connected, username='*****', socket=444, client's host='(***.***.**.**:47240)', client's tenant='************''
17:20:47.590 SCI(444,mlcmd) <== {confserv } [APP_STATUS_RUNNING, PRIMARY]
17:20:47.590 SCI(444,mlcmd) <== {102, DBServer_Logs } [APP_STATUS_RUNNING, PRIMARY]
17:20:47.590 SCI(444,mlcmd) <== {103, Solution_Control_Server} [APP_STATUS_RUNNING, PRIMARY]
17:20:47.590 SCI(444,mlcmd) <== {104, DAP_Logs } [APP_STATUS_UNKNOWN, EXITED]
17:20:47.590 SCI(444,mlcmd) <== {105, Message_Server} [APP_STATUS_RUNNING, PRIMARY]
Masked IPs above.