Problem Logging my Character in: Client Disconnected (not active in process)

[Angelox]

Say what kind of setup you have; all windowsXP Lan? are you useing a windowsXP firewall? if so, disable all software firewalls temporarly to make sure this is not the problem. If you are behind a router (routers have their own firewall), you don't need a software firewall anyway. here's a list of ports I clear on my shorewall when I run eqemu;

3306/udp 5999/udp 9000/udp 7000:7004/udp 3306/tcp 5999/tcp 7000:7004/tcp

7000-7004 is what my zone launcher uses -make sure you clear what ever your zone launcher uses

[koldar]

I have tried opening up my firewalls completely and I still initially receive this error when ever I login in for the first time.

[Kayot]

If your using the latest DB build from PEQ you don't and shouldn't use any of the SQL commands. I'm going to remake the guide soon to reflect all the changes.

[techguy84]

Josh, the

<address>192.168.0.3</address>
            <localaddress>127.0.0.1</localaddress>

located your eqemu_config.xml file was giving me issues also. I dont know if this is really needed so just change it to

<!-- <address>192.168.0.3</address> -->
            <!-- <localaddress>127.0.0.1</localaddress> -->

Doing this cancels them out. I had this issue with timing out so I just removed those two lines by doing that, (they're orginally like that I belive).
Once I did that, all my connection issues went away and I could log in perfect everytime.

Just my 2cps though.

[Thyris]

I had this same problem. repeatedly, and I think I've found the problem.

I was playing around with the items and set the default backpack* to 100% WR.

Since I made that change, I would get up to Character select and as I go to enter world, crash.

I restored the backpack to it's original state, and bam, entered world.

Hope that helps.

[Carnage_ou812]

I haven't changed any of the items in the database.
I have no problems connecting on the same machine that hosts the world/zone server (actually it hosts everything).
Neither of the other 2 machines can connect due to this error.
Disabling the 2 lines dealing with address and localhost disables minilogin.

Any idea how to get world.exe to use an address other than 127.0.0.1? Did I miss something common?

[Carnage_ou812]

Here is the whole load from world.exe.

[Debug] Starting Log: logs/eqemu_debug_world_3180.log
[Debug] [WORLD__INIT] Loading server configuration..
[Debug] [WORLD__INIT] Log settings loaded from log.ini
[Debug] [WORLD__INIT] CURRENT_WORLD_VERSION:EQEMu 0.7.0
[Debug] [WORLD__INIT] Connecting to MySQL...
[Status] Starting Log: logs/eqemu_world_3180.log
[Status] Using database 'peq' at 192.168.10.10:3306
[Debug] [WORLD__INIT] Starting HTTP world service...
[Debug] [WORLD__HTTP] Loaded mime types from mime.types
[Debug] [WORLD__INIT] Loading variables..
[Debug] [WORLD__INIT] Loading zones..
[Debug] [WORLD__INIT] Clearing groups..
[Debug] [WORLD__INIT] Clearing temporary merchant lists..
[Debug] [WORLD__INIT] Loading items..
[Status] EMuShareMem loaded
[Status] Loading items from database: count=54307
[Debug] [WORLD__INIT] Loading guilds..
[Debug] [RULES__CHANGE] Loading rule set 'default' (2)
[Debug] [WORLD__INIT] Loaded default rule set 'default'
[Debug] [WORLD__INIT] Loading EQ time of day..
[Error] Starting Log: logs/eqemu_error_world_3180.log
[Error] Could not load EQTime file eqtime.cfg
[Debug] [WORLD__INIT_ERR] Unable to load eqtime.cfg
[Debug] [WORLD__INIT] Loading launcher list..
[Debug] [WORLD__INIT] Reboot zone modes ON
[Debug] [WORLD__INIT] Deleted 0 stale player corpses from database
[Debug] [WORLD__INIT] Deleted 0 stale player backups from database
[Debug] [WORLD__INIT] Zone (TCP) listener started.
[Debug] [WORLD__INIT] Client (UDP) listener started.
[Debug] [NET__IDENTIFY] Registered patch 6.2
[Debug] [NET__IDENTIFY] Registered patch Titanium
[Debug] [NET__IDENTIFY] Registered patch Live
[Debug] [WORLD__LS] Connecting to login server...
[Debug] [WORLD__LS] Setting World to MiniLogin Server type
[Debug] [WORLD__LS] Connected to Loginserver: 192.168.10.10:5999
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1425
[Debug] [WORLD__CONSOLE] New launcher from 127.0.0.1:1425
[Debug] [WORLD__LAUNCH] Adding pending launcher 1
[Debug] [WORLD__LAUNCH] Launcher Identified itself as 'zone'. Loading zone list.

[Debug] [WORLD__LAUNCH] Removing pending launcher 1. Adding zone to active list.

[Debug] [WORLD__LAUNCH] zone: dynamic_01 reported state STARTED (1 starts)
[Debug] [WORLD__LAUNCH] zone: dynamic_02 reported state STARTED (1 starts)
[Debug] [WORLD__LAUNCH] zone: dynamic_03 reported state STARTED (1 starts)
[Debug] [WORLD__LAUNCH] zone: dynamic_04 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1433
[Debug] [WORLD__CONSOLE] New zoneserver #1 from 127.0.0.1:1433
[Debug] [WORLD__ZONE] [1] Zone started with name dynamic_01 by launcher zone
[Debug] [WORLD__ZONE] [1] Auto zone port configuration. Telling zone to use por
t 7000
[Debug] [WORLD__LAUNCH] zone: dynamic_05 reported state STARTED (1 starts)
[Debug] [WORLD__LAUNCH] zone: dynamic_02 reported state STOPPED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1437
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1438
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1439
[Debug] [WORLD__CONSOLE] New zoneserver #2 from 127.0.0.1:1439
[Debug] [WORLD__CONSOLE] New zoneserver #3 from 127.0.0.1:1438
[Debug] [WORLD__CONSOLE] New zoneserver #4 from 127.0.0.1:1437
[Debug] [WORLD__ZONE] [4] Zone started with name dynamic_04 by launcher zone
[Debug] [WORLD__ZONE] [4] Auto zone port configuration. Telling zone to use por
t 7001
[Debug] [WORLD__ZONE] [3] Zone started with name dynamic_03 by launcher zone
[Debug] [WORLD__ZONE] [3] Auto zone port configuration. Telling zone to use por
t 7002
[Debug] [WORLD__ZONE] [2] Zone started with name dynamic_05 by launcher zone
[Debug] [WORLD__ZONE] [2] Auto zone port configuration. Telling zone to use por
t 7003
[Debug] [WORLD__LAUNCH] zone: dynamic_06 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1441
[Debug] [WORLD__CONSOLE] New zoneserver #5 from 127.0.0.1:1441
[Debug] [WORLD__ZONE] [5] Zone started with name dynamic_06 by launcher zone
[Debug] [WORLD__ZONE] [5] Auto zone port configuration. Telling zone to use por
t 7004
[Debug] [WORLD__LAUNCH] zone: dynamic_07 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1443
[Debug] [WORLD__CONSOLE] New zoneserver #6 from 127.0.0.1:1443
[Debug] [WORLD__ZONE] [6] Zone started with name dynamic_07 by launcher zone
[Debug] [WORLD__ZONE] [6] Auto zone port configuration. Telling zone to use por
t 7005
[Debug] [WORLD__LAUNCH] zone: dynamic_08 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1445
[Debug] [WORLD__CONSOLE] New zoneserver #7 from 127.0.0.1:1445
[Debug] [WORLD__ZONE] [7] Zone started with name dynamic_08 by launcher zone
[Debug] [WORLD__ZONE] [7] Auto zone port configuration. Telling zone to use por
t 7006
[Debug] [WORLD__LAUNCH] zone: dynamic_02 reported state STARTED (2 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1447
[Debug] [WORLD__CONSOLE] New zoneserver #8 from 127.0.0.1:1447
[Debug] [WORLD__ZONE] [8] Zone started with name dynamic_02 by launcher zone
[Debug] [WORLD__ZONE] [8] Auto zone port configuration. Telling zone to use por
t 7007
[Debug] [WORLD__LAUNCH] zone: dynamic_09 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1449
[Debug] [WORLD__CONSOLE] New zoneserver #9 from 127.0.0.1:1449
[Debug] [WORLD__ZONE] [9] Zone started with name dynamic_09 by launcher zone
[Debug] [WORLD__ZONE] [9] Auto zone port configuration. Telling zone to use por
t 7008
[Debug] [WORLD__LAUNCH] zone: dynamic_10 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1451
[Debug] [WORLD__CONSOLE] New zoneserver #10 from 127.0.0.1:1451
[Debug] [WORLD__ZONE] [10] Zone started with name dynamic_10 by launcher zone
[Debug] [WORLD__ZONE] [10] Auto zone port configuration. Telling zone to use po
rt 7009
[Debug] [WORLD__LAUNCH] zone: dynamic_11 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1453
[Debug] [WORLD__CONSOLE] New zoneserver #11 from 127.0.0.1:1453
[Debug] [WORLD__ZONE] [11] Zone started with name dynamic_11 by launcher zone
[Debug] [WORLD__ZONE] [11] Auto zone port configuration. Telling zone to use po
rt 7010
[Debug] [WORLD__LAUNCH] zone: dynamic_12 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1455
[Debug] [WORLD__CONSOLE] New zoneserver #12 from 127.0.0.1:1455
[Debug] [WORLD__ZONE] [12] Zone started with name dynamic_12 by launcher zone
[Debug] [WORLD__ZONE] [12] Auto zone port configuration. Telling zone to use po
rt 7011
[Debug] [WORLD__CLIENT] New connection from 192.168.10.11:2762
[Debug] [NET__IDENT_TRACE] 192.168.10.11:2762: First opcode 0x4dd0 did not match
expected 0x2792
[Debug] [NET__IDENT_TRACE] 192.168.10.11:2762: Tried patch 6.2_world, and it did
not match.
[Debug] [NET__IDENT_TRACE] 192.168.10.11:2762: First opcode 0x4dd0 did not match
expected 0x2ec9
[Debug] [NET__IDENT_TRACE] 192.168.10.11:2762: Tried patch 6.2_zone, and it did
not match.
[Debug] [NET__IDENT_TRACE] 192.168.10.11:2762: First opcode matched 0x4dd0 and l
ength matched 464
[Debug] [NET__IDENTIFY] Identified stream 192.168.10.11:2762 with signature Tita
nium_world
[Debug] [WORLD__CLIENT] New client from 192.168.10.11:2762
[Debug] [WORLD__CLIENT] kids1: Logged in. Mode=(CharSel)
[Debug] [WORLD__CLIENT] kids1: MiniLogin Account #14
[Debug] [WORLD__CLIENT] kids1: Attempting autobootup of cabeast (106)
[Debug] [WORLD__ZONE] [12] Setting to 'cabeast' (106)
[Debug] [WORLD__CLIENT] kids1: Entering zone cabeast (106)
[Debug] [WORLD__ZONE] [12] [cabeast] Broadcasting a world time update
[Debug] [WORLD__ZONE] [12] [cabeast] Setting to 'cabeast' (106)
[Debug] [WORLD__CLIENT] kids1: Sending client to zone cabeast (106) at 192.168.1
0.10:7011
[Debug] [WORLD__CLIENT] kids1: Client disconnected (not active in process)

[Carnage_ou812]

Here is the loginserver.ini

[LoginServer]
loginserver=192.168.10.10
loginserver2=192.168.10.10
loginport=5999
loginport2=5999
worldname=Brell Serilis
worldaddress=192.168.10.10
locked=false
account=
password=

[WorldServer]
Defaultstatus=
Unavailzone=

[ChatChannelServer]
worldshortname=
chataddress=
chatport=

[LoginConfig]
ServerMode=MiniLogin
ServerPort=5999

Here is the eqemu_config.xml

<?xml version="1.0">
<server>
<world>
<shortname>Brell Serilis</shortname>
<longname>Friends of Norrath - Brell Serilis</longname>
<!-- Only specify these two if you really think you need to. -->
<address>192.168.10.10</address>
<localaddress>192.168.10.10</localaddress>
<!-- Loginserver information. -->
<loginserver>
<host>192.168.10.10</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 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>192.168.10.10</host>
<port>3306</port>
<username>root</username>
<password>password</password>
<db>peq</db>
</database>
</server>

Note: Names and passwords changed to protect the innocent.

Even with all of this, as seen in my previous post, the launcher still ties the zones to the loop-back address and I can't find where it is referencing it.

Any help would be greatly appreciated.

[techguy84]

Try changing this

<host>192.168.10.10</host>

back to 127.0.0.1

You dont have to reference the host machines IP for the database to connect. I dont know if this will help fix your issues though.