Server debug assistance please.

[Domingodarkrage]

How did you fix the movement problem? I'm currently having that issue, as well as npc's not responding to hails.

I'm about to start setting mine up so others can join. If I come across your problem I'll post what I find.

[Fulcrum]

Originally Posted by Domingodarkrage

How did you fix the movement problem? I'm currently having that issue, as well as npc's not responding to hails.

I'm about to start setting mine up so others can join. If I come across your problem I'll post what I find.

Aye, it took me a little time to comb through the file folders of the SVN directory for the correct updates.

I'd been looking in the folder *\Eqemusvnfiles\DB\PEQdatabase\updates on a wild goose-chase, but all of the files in there
seemed to be applied to the database already.

Thanks to a tip in the right direction, I found the required files in the following directory:
*\eqemusvnfiles\eqemu\trunk\eqemuserver\utils\sql

... and apply all the (non-optional) updates in there that are of a number > your database... which can be found in your
PEQ datadbase under the heading of db_version, (I used the suggested Navicat lite.)

This solved both the problems with being stuck in place and the unresponsive quest NPC's for me.

[Fulcrum]

Allrighty, to combat the 1017 error I've taken a few steps which haven't particularly fixed the problem, but have made this issue potentially fix-able.

I've replaced the flakey router and modem, both of which worked but HAD been hit by lightning more than once... I wasn't getting ping returns from either local or remote machines until I did so.

I killed the Windows firewall and installed a more customizable... and frankly better... firewall program.

I can still log in from my own machine, however any remote clients cannot connect due to a 1017 error.

I just grabbed a capture of my Eqemu_config.xml and a copy of the login_opcodes.... just to see if there's not something I'm overlooking. Mind you, I haven't really bothered to clean up the config, so you're going to see a lot of junk in there... (which I don't think matters, but then again, I'm more used to turning a pipe-wrench than playing nice with computer-code.

<?xml version="1.0">
<server>
	<world>
		<shortname>Junk</shortname>
		<longname>The Server That's Not Behaving</longname>

		<!-- Only specify these two if you really think you need to.  (read: You don't) -->
		<!-- <address>the.dyndns.address</address> -->
		<!-- <localaddress>192.168.1.2</localaddress> -->

		<!-- Loginserver information.  Defaults shown -->
		<loginserver>
			<!-- <host>192.168.1.2</host> -->
			<host>eqemulator.net</host>
			<port>5998</port>
			<account>nopeguessagain</account>
			<password>nawtachance</password>
		</loginserver>

		<!-- Server status.  Default is unlocked -->
		<!-- <locked/> -->
		<!-- <unlocked/> -->
	
		<!-- Sets the ip/port for the tcp connections.  Both zones and console (if enabled).  Defaults are shown -->
		<tcp ip="the.dyndns.address" port="9000" telnet="enable"/>
		<!-- <tcp ip="localhost" port="9000" telnet="disable"/> -->

		<!-- Sets the shared key used by zone/launcher to connect to world -->
		<key>JerryGarciaLivesForever</key>
		
		<!-- Enable and set the port for the HTTP service.  Defaults are shown -->
		<!-- <http port="9080" enabled="false" mimefile="mime.types" />  -->
		<http port="9080" enabled="false" mimefile="mime.types" />
	</world>

	<!-- Chatserver (channels) information.  Defaults shown -->
	<chatserver>
		<host>192.168.1.2</host> 
		<!-- <host>localhost</host> -->
		<!-- <host>channels.eqemulator.net</host> -->
		<port>7779</port>
	</chatserver>

	<!-- Mailserver (in-game mail) information.  Defaults shown -->
	<mailserver>
		<host>192.168.1.2</host> 
		<!-- <host>localhost</host> -->
		<!-- <host>channels.eqemulator.net</host> -->
		<port>7779</port>
	</mailserver>

	<zones>
		<defaultstatus>20</defaultstatus>

		<!-- Sets port range for world to use to auto configure zones -->
		<ports low="7000" high="7010"/>
	</zones>

	<!-- Database configuration, replaces db.ini.  Defaults shown -->
	<database>
		<!-- <host>localhost</host> -->
		<host>127.0.0.1</host> 
		<port>3306</port>
		<username>NotTheRealUsername!</username>
		<password>NotTheRealPassword!</password>
		<db>peq</db>
	</database>

	<!-- Launcher Configuration -->
	<launcher>
		<!-- <logprefix>logs/zone-</logprefix> -->
		<!-- <logsuffix>.log</logsuffix> -->
		<!-- <exe>zone.exe or ./zone</exe> -->
		<!-- <timers restart="10000" reterminate="10000"> -->
	</launcher>

	<!-- File locations.  Defaults shown -->
	<files>
		<spells>spells_us.txt</spells>
		<opcodes>opcodes.conf</opcodes>
		<logsettings>log.ini</logsettings>
		<eqtime>eqtime.cfg</eqtime> 
	</files>
	<!-- Directory locations.  Defaults shown -->
	<directories>
		<maps>Maps</maps>
		<quests>quests</quests> 
		<plugins>plugins</plugins> 
	</directories>
</server>

login_opcodes....

#EQEmu Public Login Server OPCodes
OP_SessionReady=0x0001
OP_Login=0x0002
OP_ServerListRequest=0x0004
OP_PlayEverquestRequest=0x000d
OP_PlayEverquestResponse=0x0021
OP_ChatMessage=0x0016
OP_LoginAccepted=0x0017
OP_ServerListResponse=0x0018
OP_Poll=0x0029
OP_EnterChat=0x000f
OP_PollResponse=0x0011

And here's login.ini if it'l help:

[database]
host = localhost
port = 3306
db = eqemu
user = user
password = password
subsystem = MySQL

[options]
unregistered_allowed = TRUE
reject_duplicate_servers = FALSE
trace = TRUE
world_trace = FALSE
dump_packets_in = FALSE
dump_packets_out = FALSE
listen_port = 5998
local_network = 192.168.1.2

[security]
plugin = EQEmuAuthCrypto
mode = 5

[Titanium]
port = 5998
opcodes = login_opcodes.conf

[SoD]
port = 5999
opcodes = login_opcodes_sod.conf

[schema]
account_table = tblLoginServerAccounts
world_registration_table = tblWorldServerRegistration
world_admin_registration_table = tblServerAdminRegistration
world_server_type_table = tblServerListType

[Domingodarkrage]

I gave up on privately hosting a game without using eqemulator's login because I could not resolve similar issues that you are getting now, and some router problems.

However, I thought that having the !<--- and -----> in your config file disabled that line, which looks like it would disable your login server from those on the outside. If anyone knows the real effect, please state it. I am also more familiar with a pipe wrench than this stuff.