Bad server name. Unknown reason.

[John Adams]

Best way I can answer this is to show you my config. I have World/Zones running on a Fedora Core 4 Linux box. My config is:

<server>
        <world>
                <shortname>tess</shortname>
                <longname>Dev Server</longname>
                <address>192.168.0.40</address>
                <localaddress>192.168.0.40</localaddress>
                <loginserver>
                        <host>192.168.0.30</host>
                        <port>5999</port>
                        <account></account>
                        <password></password>
                </loginserver>
        </world>
        <database>
                <host>localhost</host>
                <port>3306</port>
                <username>eq</username>
                <password>eq</password>
                <db>eq</db>
        </database>

As you can see, contrary to Mr Condescending who says "read: you don't" without giving a shred of explanation why it's configurable, but never ~yawn~ needed... I use it, and it works. <address> and <localaddress> are set, and they work for me.

192.168.0.40 is my Linux FC4 box (world/zones and MySQL)

My Minilogin.exe is running on a spare Windows Server 2003 box, and here are those configs:
3 files only:
Minilogin.exe
opcodes.conf
loginserver.ini

Loginserver.ini --

[LoginServer]
loginserver=192.168.1.20     <-- wrong but works anyway
loginport=5999                   <-- correct
worldname=Dev Server        <-- correct
worldaddress=192.168.1.40  <-- wrong but works anyway
locked=false
account=
password=

[WorldServer]
Defaultstatus=
Unavailzone=

[ChatChannelServer]
worldshortname=
chataddress=
chatport=

[LoginConfig]
ServerMode=Minilogin    <-- correct
ServerPort=5999          <-- correct

I draw your attention to the fact that even tho this Loginserver.ini doesn't match whatsoever to my actual World info, it still runs anyway. ~boggle~ These devs are better than the docs writers, I tell ya.

Last but not least, in MySQL, table: variables, there is a row called "LoginType". That needs to have a value of "minilogin"

INSERT INTO `variables` (`varname`, `value`, `information`, `ts`) VALUES ('LoginType', 'minilogin', 'Set this to Minilogin to login using a minilogin server :)', '2006-11-24 11:09:41');

(which is the part that bites 90% of the emu admins on the ass...

Now I am concluding after only 6 mos of playing with this emulator that half the instructions are written "as needed", and depending on how one guy got his emulator to work. There are likely many, many ways to tie it all together - but the Wiki'd, documented instructions are the best. As you see, even mine is bogus. "Works for me".

For my Minilogin server, all the world seems to care about is that there is a Minilogin.exe running "somewhere", and that the name in the INI matches the <longname> in the eqemu_config.xml (not sure why that's so important, except to prevent us from running our own loginservers for our pals).

All of this is described brilliantly in this wiki page.

Sounds like you have a good grasp of how things work. So I hope this helps.