Yet another problem.
 

After setting everything up and fixing my Boot5Zones problem a new problem arises! When going into the login screen my server is always locked. ... I've heard of this happening to other people but their problem is usually needing to run Boot5Zones and that's not the case here.

The zones have to start and connect to world before the server becomes unlocked, check the zone server screens for errors or just not connecting to world. World will aslo hav a message when a zone connects to it.

Ah yes. Here we go.
I run boot5zones, and each zone says,
"
Using database 'eq' at localhost
EQEMu 0.4.1 Spekkio
Loading zone names, items & NPCs...
EMuShareMem.dll loaded.
...done.
done.
If this is the last message you see, you forgot to move spells_en.txt. from your EQ dir to this dir.
Spells loaded.
Loading guild ranks...done.
Loading faction data...done.
WorldServer connect: Connecting to the server failed. Error: 10060
InitWorldServer failed
Entering sleep mode
"
It then proceeds to spam me with the "WorldServer connect: Connecting to the server failed. error: 10060" message until the program is closed. Note to self: don't try to set things up when half asleep. I'll search the other posts for this problem but any help would be appreciated. :?

whats in you boot5zones.bat...

Boot5Zones

REM: ****Read this first!!!****

REM: This file requires your real IP in the place of "YourIP" when you are connecting
REM: To the EQEmu Loginserver.

REM: When you are using minilogin, Replace all IP Addresses to say 127.0.0.1

REM: If you still get errors try using localhost instead of 127.0.0.1

REM:--------------Start-----------------------
@echo off

if NOT exist spells_en.txt goto NOSPELL

start zone . 68.51.140.179 7995 68.51.140.179
start zone . 68.51.140.179 7996 68.51.140.179
start zone . 68.51.140.179 7997 68.51.140.179
start zone . 68.51.140.179 7998 68.51.140.179
start zone . 68.51.140.179 7999 68.51.140.179
exit
cls

:NOSPELL
echo You did not copy the spells_en.txt from your everquest directory to this one. Please do so or zones will crash on startup.
PAUSE

REM:---------------END------------------------



ALSO, I forgot because I only installed it just recently but I'm now using a router instead of direct connection to my cable. I'm almost positive that's what the problem is but I'm not quite sure how to fix it as I don't know too much about networking.

the 2nd ip on your boot5zones should be 127.0.0.1 if that machine doesn't have that ip.

Changed second IP in Boot5Zones to 127.0.0.1 and the server is no longer locked. Hurrah. However, the infamous 1017 error is still showing it's ugly face. I was installing an addon (0.3.13) when I came across many errors in spawns.sql
The installation program terminated, and now I see a noticeable change in the time it takes for world.exe and boot5zones to finish their work. No error messages in those programs, just takes longer and the 1017 message keeps coming back to haunt me. Not sure whether it's the addresses in boot5zones or whatever is going on with spawns.sql that is the problem, but it would make sense that the connection problem is in the addresses. But then hey, look at my signature quote. :roll:

Content of Boot5Zones
"
REM: ****Read this first!!!****

REM: This file requires your real IP in the place of "YourIP" when you are connecting
REM: To the EQEmu Loginserver.

REM: When you are using minilogin, Replace all IP Addresses to say 127.0.0.1

REM: If you still get errors try using localhost instead of 127.0.0.1

REM:--------------Start-----------------------
@echo off

if NOT exist spells_en.txt goto NOSPELL

start zone . 68.51.140.179 7995 127.0.0.1
start zone . 68.51.140.179 7996 127.0.0.1
start zone . 68.51.140.179 7997 127.0.0.1
start zone . 68.51.140.179 7998 127.0.0.1
start zone . 68.51.140.179 7999 127.0.0.1
exit
cls

:NOSPELL
echo You did not copy the spells_en.txt from your everquest directory to this one. Please do so or zones will crash on startup.
PAUSE

REM:---------------END------------------------
"

Everything goes smoothly, no error messages, until I try to log in, at which time I get the 1107. I never thought though, that it might just be me. If someone else would attempt to log on to my server (Ohtori) and see if it works then post here with the outcome I would be thankful. :D