eqemu0.3.3.1 errors (clean server)

[Sh1nj1]

i've been having a lot of problems, with the emu ever since version 3.2 was out, now with 3.3.1 even more, first off, i cant log into the servers, i can get to the character login screen on some servers, but when i log in i drop back to desktop, i've tried searching the boards and read the sticky's on it and tried the fixes but nothing seems to work, when i run my server i get errors when ever i or others try to log into it (screen shot of the errors is included) i made a clean database for the server and only sourced the database included with the 3.3.1 executable.

db.ini

# READ README.TXT!

[Database]
host=localhost
user=Shinji
password=***********
database=eq


### --- This file tells world.exe what computer mySQL is on. Host should
### --- be left as localhost unless mysql is
### --- on a differant computer than world.exe.

loginserver.ini

### --- This file tells world.exe what loginserver to connect to.
### --- do not add an account and password unless a EQEmu Dev member has created an account for you.
### --- adding an account and password only grants the server a green name and is not needed.

### --- Public Login is un-supported as is LAN playing. We reccomend using the EQEmu.org Loginserver ALWAYS.

# READ README.TXT

[LoginServer]
loginserver=eqlogin1.eqemu.org
loginserver2=eqlogin2.eqemu.org
loginport=5999
loginport2=5999
worldname=Sh1nj1's EverQuest Station
locked=false
account=
password=
worldaddress=24.73.96.76

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

boot5zones.bat

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: zoneNT.exe is for use with Windows NT, 2000 and XP.

REM:--------------Start-----------------------


@echo off
start zoneNT . 24.73.96.76 7995 127.0.0.1
start zoneNT . 24.73.96.76 7996 127.0.0.1
start zoneNT . 24.73.96.76 7997 127.0.0.1
start zoneNT . 24.73.96.76 7998 127.0.0.1
start zoneNT . 24.73.96.76 7999 127.0.0.1
exit
cls


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

running, windows xp pro, anyone know whats causing this?

[Everdude02]

@echo off
start zoneNT . 24.73.96.76 7995 127.0.0.1
start zoneNT . 24.73.96.76 7996 127.0.0.1
start zoneNT . 24.73.96.76 7997 127.0.0.1
start zoneNT . 24.73.96.76 7998 127.0.0.1
start zoneNT . 24.73.96.76 7999 127.0.0.1
exit
cls


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

running, windows xp pro, anyone know whats causing this?


Try changing ALL of the IP's to 24.73.96.76, seems like you missed the 127.0.0.1's. Not sure if this will fix it, but it will help.

[Symarra]

Read up on XP....

http://www.microsoft.com/windowsxp/...pro/default.asp

Do you have a LAN setup?

If you have a NIC and its connected to a LAN, pull the CAT5 cable out of your NIC restart computer, log into XP.
ps. If the only NIC your have installed runs to your cable modem then disregard this.

By doing the above you've esstially, mandated your IPs to only your dial-up/cable modem IP address & 127.0.0.1 (ie. localhost)

[Sh1nj1]

... umm the second ip is just to hide the real up from the computer itself so that it thinks its local host but its actualy internet, this way you can host a server and be able to log into a server with eqw at the same time, i do run on a network (no router though) so this comp is connected to a hub, it has a static ip so nothing you mentioned can affect it :mad:

[Shawn319]

Try changing ALL of the IP's to 24.73.96.76, seems like you missed the 127.0.0.1's. Not sure if this will fix it, but it will help.

Well the second IP (after port) tells zone.exe where world.exe is, so why make zone.exe go to your ISP then back to your computer? doesnt make sence to go 5000 miles in the air, rather than two sectors away on your HD :) You can try using "ip port ip" but it PROBABLY wont help much :)


btw, Unknown opcodes are not "errors" thay are packets the emu doesnt recognize.

[Symarra]

If you haven't fixed it then try what I said.....


PULL the durn plug on the NIC !

Then try the emu