So Close, yet a step away

[laxative]

Greetings,

I read that minilogin might be outdated, so I took a shot at going with Eqemuloginserver.exe. I had a working server with minilogin more than 2years ago, but all that data is gone.

I'm very close, I've got the executables loading, eqemulogin server appears to be running, I got the steam underfoot client which finally will connect, I have no server listing, I know I missed something dumb.

I am still confused at which ini files I no longer need. Hopeing for help, here's what I got:

Environment: Windows7 Server, Correct Perl, MYSQL, and SVN codes/databases.

EQEmu XML Config file:

<?xml version="1.0"?>
<server>
<world>
<shortname>Orion</shortname>
<longname>Orion EQ Emu</longname>

<!-- address has to be specified for minilogin to work -->
<address>72.227.118.239</address>
<localaddress>192.168.1.145</localaddress>

<!-- Loginserver information. -->
<loginserver>
<host>72.227.118.239</host>
<port>5999</port>
<account></account>
<password></password>
</loginserver>

<!-- Sets the shared key used by zone/launcher to connect to world -->
<key>make up some random string of characters here</key>

<!-- Enable and set the port for the HTTP service -->
<http port="9080" enable="true" mimefile="mime.types"/>
</world>

<!-- Database configuration, replaces db.ini -->
<database>
<host>localhost</host>
<port>3306</port>
<username>root</username>
<password>******</password>
<db>peq</db>
</database>
</server>

Eqemulogin.ini

Port=5999
 DumpPacketsIn=true
 DumpPacketsOut=true
 Trace=true
 DatabaseServerName=72.227.118.239
 DatabaseCatalogName=peq
 DatabaseUserName=root
 DatabaseUserPassword=0rion123
 OPCodePathAndFileName=opcodes.conf

I tried several different lines around opcodes, no change

Login.ini

[database]
host = localhost
port = 3306
db = peq
user = root
password = *****
subsystem = MySQL

[options]
unregistered_allowed = TRUE
reject_duplicate_servers = FALSE
trace = TRUE
world_trace = FALSE
dump_packets_in = FALSE
dump_packets_out = FALSE
listen_port = 5999
local_network = 192.168.1.

[security]
plugin = EQEmuAuthCrypto
mode = 5

[Titanium]
port = 5998
opcodes = login_opcodes.conf

[SoD]
port = 5999
opcodes = login_opcodes_sod.conf

[schema]
account_table = tblLoginServerAccounts
world_registration_table = tblWorldServerRegistration
world_admin_registration_table = tblServerAdminRegistration
world_server_type_table = tblServerListType

Loginserver.ini (not even used unless minilogin?) I know when I changed minilogin to public something different didnt happen, maybe my ipaddresses are wrong here? ...

### --- This file tells world.exe what loginserver to connect to.
### --- Leave the account and password field BLANK.

### --- Public Login is un-supported as is LAN playing. We reccomend using the EQEmu.net Loginserver ALWAYS.

### --- NOTE: Starting 6-1-2002, you can no longer use the word "Server" in worldname.
### --- NOTE2: the word "Server" is added to each server automaticly.

# READ README.TXT

[LoginServer]
loginserver=127.0.0.1
loginserver2=
loginport=5999
loginport2=5999
worldname=Orion
worldaddress=127.0.0.1
locked=false
account=
password=

[WorldServer]
Defaultstatus=
Unavailzone=

[ChatChannelServer]
worldshortname=
chataddress=
chatport=

[LoginConfig]
ServerMode=Public
ServerPort=5999

My Server shows up in the Database, however the values of server last login and last IP address are null.

Note I did setup this up first as a Minilogin server so those tables are still in there, but I changed the variables table entry from minilogin to public
and I get this message:

New world server connection .....etc etc
Server **name** did not attempt to login but this server requires a password.

I was pretty familiar with Minilogin, but I'm not doing well with Eqemulogin server it would seem.

Can anywhere suggest where I went wrong, I think I'm pretty close.

[laxative]

Found it!

Thank you Getophe:

I ran into the problem with my server not showing up in the server selection list in the client. I solved it that way:

In your eqemu_config.xml file fill in the info for "account" and "password" in the "Loginserver information" section of the file to reflect the entry in the "tblserveradminregistration" table, by default when I created the table using the provided SQL file it was "Admin" and "Password", but make sure to check and use the actual entries, so it should look like this:



Code:
<!-- Loginserver information. -->
<loginserver>
<host>192.168.1.110</host>
<port>5999</port>
<account>Admin</account>
<password>Password</password>
</loginserver> restart the whole thing and now your server should be listed in your client ...

hope this helps

Cheers!

That was indeed the problem I'm up and connecting with the new services.

EDIT: also had to delete the user account in the ACCOUNT table because using this new method that gets populated for you.. yay!

-Laxa