Jump to content

binglenozumi

Members
  • Content Count

    3
  • Joined

  • Last visited

About binglenozumi

  • Rank
    Newbie

Recent Profile Visitors

841 profile views
  1. But that packet thing is shown when I turn on athena-start, which I haven't connect any client to it though...
  2. I've tried your method, it returns this (no matter is using DDNS name or comment them out) Unknown packet 0x006a received from login-server, disconnecting. So I have no idea what is going on, it looks like there is something happening, but it doesn't
  3. Hi, I am currently building my server, and found out it keep having the issue of either connection to login server lost or connection to char server lost... [Info]: Attempt to connect to login-server...war.txt[Status]: Connecting to 127.0.0.1:6900[Warning]: Connection to Login Server lost. Which it does saying [Status]: The char-server is ready (Server is listening on the port 6121).[Status]: The login-server is ready (Server is listening on the port 6900). So when I look at all the logs that are running, there is no error with SQL nor other errors during the compile or other means Here are all my config files look like: char-server.conf // Server Communication username and password.userid: nozumipasswd: nozumi// Server name, use alternative character such as ASCII 160 for spaces.// NOTE: Do not use spaces or any of these characters which are not allowed in // Windows filenames /:*?"<>|// ... or else guild emblems won't work client-side!server_name: Hercules// Wisp name for server: used to send wisp from server to players (between 4 to 23 characters)wisp_server_name: Server// Login Server IP// The character server connects to the login server using this IP address.// NOTE: This is useful when you are running behind a firewall or are on// a machine with multiple interfaces.login_ip: 127.0.0.1// The character server listens on the interface with this IP address.// NOTE: This allows you to run multiple servers on multiple interfaces// while using the same ports for each server.//bind_ip: 127.0.0.1// Login Server Portlogin_port: 6900// Character Server IP// The IP address which clients will use to connect.// Set this to what your server's public IP address is.char_ip: kornhill.dyndns.org// Character Server Portchar_port: 6121 map-server.conf // Interserver communication passwords, set in account.txt (or equiv.)userid: nozumipasswd: nozumi// Character Server IP// The map server connects to the character server using this IP address.// NOTE: This is useful when you are running behind a firewall or are on// a machine with multiple interfaces.char_ip: 127.0.0.1// The map server listens on the interface with this IP address.// NOTE: This allows you to run multiple servers on multiple interfaces// while using the same ports for each server.//bind_ip: 127.0.0.1// Character Server Portchar_port: 6121// Map Server IP// The IP address which clients will use to connect.// Set this to what your server's public IP address is.map_ip: kornhill.dyndns.org// Map Server Portmap_port: 5121 and inter-server.conf // Global SQL settings// overridden by local settings when the hostname is defined there// (currently only the login-server reads/obeys these settings)sql.db_hostname: 127.0.0.1sql.db_port: 3306sql.db_username: ragnaroksql.db_password: ragnaroksql.db_database: herculessql.codepage:// MySQL Character SQL serverchar_server_ip: 127.0.0.1char_server_port: 3306char_server_id: ragnarokchar_server_pw: ragnarokchar_server_db: hercules// MySQL Map SQL Servermap_server_ip: 127.0.0.1map_server_port: 3306map_server_id: ragnarokmap_server_pw: ragnarokmap_server_db: hercules// MySQL Log SQL Databaselog_db_ip: 127.0.0.1log_db_port: 3306log_db_id: ragnaroklog_db_pw: ragnaroklog_db_db: loglog_codepage:log_login_db: loginlog Any suggestions to resolve that problem? thanks
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.