Your IP's in your client are wrong. Edit your loginlist.csv and one other one... channellist? On your client to connect. Your server is running fine. The SIEGE_CALL_FAIL doesnt affect anything ingame except for seige.
not really, when i was running the DK Veterans server all my IP's where 127.0.0.1
and it said, connected so why change it if it works ?
if i entered a ip like: 192.168.1.*** it didn't work so ....
my guess: siege script not working
Your IP's in your client are wrong. Edit your loginlist.csv and one other one... channellist? On your client to connect. Your server is running fine. The SIEGE_CALL_FAIL doesnt affect anything ingame except for seige.
not really, when i was running the DK Veterans server all my IP's where 127.0.0.1
and it said, connected so why change it if it works ?
if i entered a ip like: 192.168.1.*** it didn't work so ....
my guess: siege script not working
Server side, true. Almost all of them should be 127.0.0.1 which is the internal loopback address. CLIENT side, your ip's need to be set to the external IP on the dedicated. (If your not using a dedicated.... Just nevermind this thread lol). Another reason your client may not connect is due to port issues. If your using a dedi; open the ports in your firewall to allow connections.