MY DELIGHTFUL ERROR

[DeletedUser]

Originally Posted by LoginServer.ini

[LoginServer]
loginserver=eqlogin1.eqemulator.net
loginport=5997
worldname=My Test Blah
worldaddress=64.68.82.168
locked=false

[WorldServer]
Defaultstatus=0
Unavailzone=

[LoginConfig]
ServerMode=Standalone
ServerPort=5999
UplinkAddress=
UplinkPort=
UplinkAccount=
UplinkPassword=

Originally Posted by db.ini

[Database]
host=localhost
user=test
password=test
database=eq
compression=off

Originally Posted by Boot5zones.bat

@echo off

if NOT exist spells_en.txt goto NOSPELL

start zone . 64.68.82.168 7995 127.0.0.1
start zone . 64.68.82.168 7996 127.0.0.1
start zone . 64.68.82.168 7997 127.0.0.1
start zone . 64.68.82.168 7998 127.0.0.1
start zone . 64.68.82.168 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

I'm on a router.. Windows XP.

I've added the eqemu/eqemu/status: 200.. so the 1017 error isn't from that.

Apparently minilogin isn't working, so I tried doing this with the public loginserver.. but i'm getting the same error. I can log into 5.2 servers no problem.

I've redone the database many times.. I know it's not the database. I've never had a 1017 error until now, my 5.1 server worked fine.

I don't think it has anything to do with the zones, because the zones are connecting fine and the server isn't locked.

No clue what to post for errors.. because i'm not getting any errors besides a 1017.. :o

[Edgar1898]

64.68.82.168 isnt your ip address

[Ralex]

Hm, that makes me curious. I use Minilogin, but recieve the same error, regardless. A few simple moments to switch back to the 5.1 software without need for reconfiguring, and it works flawlessly.

[Wumpas]

Darkyth I have the same problem My 5.1 server runs fine my 5.2dr1 works fine my 5.2 same setup with every posible database configuration and sourcing combination imaginable does not work. I too have ruled out my database as boot5zones and world connect fine and server is not locked. . . I hate saying this next part as it tends to invoke the rath of everyone but. . . 1017 !!

(Wumpas hides under a chair cowering)

Im going to try again tonight I think I sourced my database from scratch at least 15 times today and even used dragons pre sourced database unsucessfully (I don't think its a database problem)... That said does 5.2 have any changes to ports or methods of connection that could affect how it runs with certain firewall settings. (AGAIN 5.1 and 5.2dr1 work flawlessly)

(Note: the 5.2 release and 5.2 source both produce same error)

If i find any way to get this to work ill post it but Im about to throw in the towel for the day as i spent 7 hours frying my eyes in front of my computer to get it to work. (ATENTION: error is due strikcly to my own errors until proven otherwise by a dev) my day off is once again consumed with

Do WHILE 1017 = 1
{
drop database eq;
create database eq;
source (insert database here)
----unplug pc speaker as it resonates with my fillings no joke !----
grant all privileges on *.* to eqemu@localhost identified by 'eqemu' with grant option;
INSERT INTO account SET name='eqemu', password='eqemu', status=200;

check the Forums for possible causes or signs im not the only one in the boat.
}

For those that dont understand my pseudo code just repeat those steps over and over and over and over changing every variable you can until it works :P it may help to down a beer on every other loop.

[DeletedUser]

Originally Posted by Edgar1898

64.68.82.168 isnt your ip address

Then why is it allowing the zones to connect without error?

[Wumpas]

Ok after some forum browsing I found that the general consensus is that Minilogin is our 1017 caulpret I guess ill set up and play from a diffrent pc on my lan instead.

P.S. If anyone knows of any plans by anyone to update the minilogin it would be nice to know.

ok Gnight guys im way past my bedtime

[Edgar1898]

because zones connect to the world server using the second ip address, not the first. I would have thought you would have figured that out by now....


and a simple dns query of 64.68.82.168 returns crawler14.googlebot.com, so I dont know where you think you got that ip from but try again.