Can't get beyond the login screen

[edolfo]

Hey guys,

I set up eqemu version 0.7.0-1118 on an Ubuntu 7.10 box. I already have a webserver running on it (Apache + PHP + MySQL), so I skipped all instructions in regards to getting these things set up (Apache + PHP for a custom database editor from peq). Ideally I'd like to log in and play when I'm not at home (http://www.eqemulator.net/wiki/wikka.php?wakka=MiniLogin), i.e. not within my internal network. I've cut back on that ambition to try to get it to work internally.

I can't get beyond the login screen.

My server is behind a router, but I've already set all relevant requests to forward on to my server. That is, I have the following ports set to forward on to my server (not all of which are relevant to eqemu):

80 (HTTP)
22 (SSH)
8080 (Custom music server)
8000 (Torrent interface)
17415 (slsk)
5999 (eqemu)
9080 (eqemu HTTP)

I have wine installed through the repositories, and it's running MiniLogin. Compilation of eqemu went through O.K. after following the guide here (http://www.eqemulator.net/wiki/wikka.php?wakka=DebianLinuxServer).

The server's internal IP address is 192.168.1.2
The server's external IP address is 63.249.90.243

I have configured everything clientside correctly (I think). I modified eqhost.txt and altered a shortcut to the Everquest executable. Yes, I am running the titanium edition, and no, I have not patched to the live version. Following are my configuration files:

eqhost.txt:

[LoginServer]
Host=192.168.1.2:5999


eqemu_config.xml:


<?xml version="1.0">
<server>
<world>
<shortname>Dragonslayer</shortname>
<longname>Is Wayne Brady gonna have to choke a bitch?</longname>

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

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

<!-- Sets the shared key used by zone/launcher to connect to world -->
<key>some long random key</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>192.168.1.2</host>
<port>3306</port>
<username>root</username>
<password>*************</password>
<db>dragonslayer</db>
</database>
</server>


LoginServer.ini:

### --- 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=192.168.1.2
loginserver2=newlogin1.eqemulator.net
loginport=5999
loginport2=5999
worldname=Is Wayne Brady Gonna Have to Choke a Bitch?
worldaddress=192.168.1.2
locked=false
account=
password=

[WorldServer]
Defaultstatus=
Unavailzone=

[ChatChannelServer]
worldshortname=
chataddress=
chatport=

[LoginConfig]
ServerMode=StandAlone
ServerPort=5999


And here is something fairly disturbing: the contents of MiniLogin.log:

MiniLogin.log

LoginServer.ini read.
[Status] Loading opcodes..
Server mode: MiniLogin
Login server listening on port:5999
Failed to open port 5999.


Why would it fail to open that port?

If anyone has any ideas or needs more information, please let me know.

Thanks,

Edolfo

[Derision]

Failed to open port 5999.


Why would it fail to open that port?


Maybe something else is already using that port. If you enter the command:

netstat -ap | grep 5999

Do you get any output ?

[edolfo]

Ahh, this is interesting. It looks like something IS using that port:


edolfo@edolfo-server:~$ sudo netstat -ap | grep 5999
tcp 0 0 *:5999 *:* LISTEN 13808/MiniLogin.exe
udp 0 0 *:5999 *:* 13808/MiniLogin.exe


Doh. Good idea though, not sure why I didn't think of that. Guess it's one of those days...

[cavedude]

Your problem is common on Linux boxes. When you kill Wine, Minilogin remains in memory using port 5999. On my Gentoo test server, I ended up adding

killall -9 MiniLogin.exe

to my stop script and it took care of the problem. Your mileage may vary on Ubuntu, but I don't see any reason why that won't get it. If you need a full stop script, let me know.