Private Login Server

[Aldest]

Not at all. Here you are:

<?xml version="1.0">
<server>
<world>
<shortname>shadowrealm</shortname>
<longname>Shadow Realm</longname>

<!-- Only specify these two if you really think you need to. -->
<address>5.2.52.138</address>
<localaddress>5.2.52.138</localaddress>

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

<!-- Sets the shared key used by zone/launcher to connect to world -->
<key>some long random string</key>

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

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

[neiv2]

Can you elaborate on your host? <host>5.2.52.138</host>

Is this a static IP address? All the instructions I have seen specify the use of 127.0.0.1 as the host.

[neiv2]

Thank you , Aldest; my world is now working. The only two variations that existed between your eqemu_config.xml file and mine were:

(1) there were a lot of extraneous settings in my version regarding chat servers, mail servers, zone default status, launcher configuration, file locations, and directory locations that apparently just do not apply to PEQ. I was attempting to use the eqemu_config.xml file that an AX user posted earlier. I assumed that may have been part of the problem, so I deleted all of those lines.

(2) There are explicit instructions in that eqemu_config.xml file regarding the World address and localaddress; to wit, "<!-- Only specify these two if you really think you need to. (read: You don't) -->." But I noticed that you had populate these fields, so I did as well (with 127.0.0.1).

Now my world works.

Image, you may want to make a sticky note on your forum for PEQ db users, and post Aldest's eqemu_config.xml file as a template to use.

You may also want to include the fact that you must use the INSERT command to populate the login_accounts table with the md5 password, and not use a manual db population process (that tripped me up). That, I think, will save tons in support hours.

[neiv2]

Now, of course, I have a new issue.

I am able to get into the world, but I am unable to zone to any other zone. Each time I try it, I am pushed back and told, "This zone is not ready to receive visitors yet. Please try again in a few moments."

[neiv2]

P.S. I am able to zone if I double click zone.exe a few times. But of course, this is not the ideal situation.

[Congdar]

might be your database tables launcher and launcher_zones
my launcher is
zone | 2
and my launcher_zones is
zone | poknowledge | 0

This gives me two dynamic zones and one static plane of knowledge.

when you start eqlaunch.exe zone the 'zone' has to match what you have in the first column of launcher and launcher_zones.

[neiv2]

Actually, the problem was that I had forgotten to include eqlaunch in the fire-up sequence : )

All's well now. Thanks.

[neiv2]

Okay, server is all set up and running. One final question, though. What changes do I need to make in the clients that are logging in? How should their eqhost read, especially if I have used 127.0.0.1 for the server and these are local clients? Should their eqhost files look identical to mine? Anything else that needs to be changed here? My son's client machine cannot login for some reason. Yes, I created his account in the db.

[Congdar]

127.0.0.1 means THIS computer that you are on. So for your son, 127.0.0.1 would mean his computer.

From a command prompt on the computer running the eqemu server type ipconfig and press the enter key. You will see several lines. You want the numbers from IP Address or on Vista it's IPv4 Address. Usually something like 192.168.1.1 and use that for your sons eqhost.txt file 192.168.1.1:5999

[neiv2]

That was one of the things we tried earlier. We also tried using the Address that shows up for my server on the Login Server Status page. Still no go.

If any PEQ user who uses the Private Login has an idea (Aldest?), that would be great.

[Angelox]

That post I made somwhere for converting MiniLogin accounts to the new login system was pretty sucky and complicated. Here's my latest one that works from within MySql and is tested as good.

--------------------------------------------------------------------------
--- Converts your MiniLogin accounts to the New login acount system.   ---
--- Be sure your 'new_login.login_accounts' is clear before transfer.  ---
--- You can change directory settings to what you prefer.              ---  
--- Linux users need a "world writable" directory (try /tmp ).         ---
--- If you don't like the change, MiniLogin will still work.           --- 
--------------------------------------------------------------------------
SELECT id,name,password FROM ax_classic.account INTO OUTFILE '/eqemu/updates/account_part1.txt'
FIELDS TERMINATED BY ',' ENCLOSED BY '"' LINES TERMINATED BY '\n';

LOAD DATA INFILE '/eqemu/updates/account_part1.txt' INTO TABLE new_login.login_accounts
FIELDS TERMINATED BY ',' ENCLOSED BY '"'
LINES TERMINATED BY '\n';

UPDATE new_login.login_accounts SET `password` = MD5(`password`) WHERE LENGTH(`password`) > 0 AND (LENGTH(`password`) != 65 AND LOCATE(':', `password`) != 33) AND LENGTH(`password`) != 32;

You can alter the lines/directorys to fit your needs schema new_login is what I named the LS database.
If you had a Public Login account system, then the port will move the names over, but with blank passwords - you'll need to set passwords;

UPDATE login_accounts SET password=md5("NewPassword") WHERE name = 'UserName';

If you don't like what you did, you don't need to revert - since table account has not been altered, you'll be able to choose whichever LS system you want.

[Aldest]

I'm glad my file helped and I'm sorry I wasn't around sooner to answer your question.

It has been a busy weekend!

[Aldest]

Ok, I've got a new issue. Hopefully Angelox might have the solution!

I have previously been using leaf networks to get everyone in the same "LAN." It is unreliable and frustrates my users. It did work though.

I switched over to just using a straight connection from the outside to my home IP. It worked great... except for everyone in my household.

Local users could connect to the login server, pick a server, but never make it to character select. I fixed that by putting a host entry on the machines.

Now they can log in but every time they zone they get disconnected with this error message in world:

[Debug] [WORLD__CLIENT_ERR] jud: ID is 0. Is this server connected to minilogin
?
[Debug] [WORLD__CLIENT_ERR] jud: Could not find a minilogin account, verify ip a
ddress logging into minilogin is the same that is in your account table.

[Aldest]

Disregard the above.

To correct this you need to change your server type from minilogin to public.