Josh, the

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

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.

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.

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?

Here is the whole load from world.exe.

Here is the loginserver.ini

Here is the eqemu_config.xml


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.

Try changing this

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.

Actually, looking through your world server log I do not see a problem. The client disconnected (Not in active process) simply means that the world server handed off the client to the zone server.

What sort of problem are you actually having?

Computer 1: Hosts Emulation server. This connects fine.
Computer 2: Connects through to character select but drops after that (can't actually log into a zone.
Computer 3: Connects fine.

Because of the 3rd computer install going okay, I am looking heavily at my network packets to determine if there is something wrong with computer 2. With computer 3 running on the network with minilogin, that definitely puts it over to client-side issues.

Thanks for all of the PMs as well as the follow-up posts. You guys are pretty good about supporting this community.

I will post with my vpn project results later.

Moral to the story:

Leave nothing to chance. Make sure you verify the components of your clients before you start any guide.

The memory had been swapped out on the offending client that would not connect. The program was loading in small chunks while paging. Very messy.