Quote:
Also, I still get a 10061 error just one time at the beginning of eqlaunch, but then it says its connected to localhost and begins loading zones. Here's what it says:
[Debug] Starting Log: logs/eqemu_debug_4936.log
[Debug] [LAUNCHER__INIT] Loading server configuration..
[Debug] [NET__WORLD] WorldConnection connect: Connecting to the server localhost
:9000 failed: TCPConnection::Connect(): connect() failed. Error: 10061
[Debug] [LAUNCHER__ERROR] worldserver.Connect() FAILED! Will retry.
[Debug] [LAUNCHER__INIT] Starting main loop...
[Debug] [NET__WORLD] Connected to World: localhost:9000
|
That 10061 error is not a problem, it's just that the launcher tries to connect to world before world is ready. You can see it successfully connects shortly afterwards by the [NET__WORLD] Connected to World: localhost:9000 message.
Code:
<!-- Loginserver information. Defaults shown -->
<loginserver>
<host>clmtyserver.dnsalias.com</host>
<port>5998</port>
<account>MyAdminAccountName</account>
<password>MyAdminAccountPassword</password>
</loginserver>
If you are running EQEmuLoginServer on the same PC as world, then I would put localhost or 127.0.0.1 or your internal IP (192.168.x.x) in the <host> part of the loginserver section. Also, I don't think you need to specify an account or password for the loginserver.
It sounds like world is not connecting to the loginserver. If you switch to the command window in which EQEmuLoginServer.exe is running, you should see a message along the lines of 'New server connection from a.b.c.d' when world connects to it, or you might have some error messages in there.
In addition, look at the output of world.exe, does it say connected to loginserver, or are there error messages there as well ?
Threaded Mode
