Another 1017 post (sorry)

[Sarepean]

Okay, I'm posting everything. Compare and whatnot--- copy and paste if you need to.


Loginserver.ini:

### --- This file tells world.exe what loginserver to connect to.
### --- Leave the account and password field BLANK.

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

### --- NOTE: Starting 6-1-2002, you can no longer use the word "Server" in worldname.
### --- NOTE2: the word "Server" is added to each server automaticly.

# READ README.TXT

[LoginServer]
loginserver=eqemulator.net
loginport=5998
worldname=Sarepean's Test
worldaddress=70.178.49.239
locked=false
account=
password=

[WorldServer]
Defaultstatus=0
Unavailzone=

[ChatChannelServer]
worldshortname=
chataddress=
chatport=




boot5zones.bat:

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

REM: This file requires your real IP in the place of "EXTERNAL_IP_HERE" 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

REM: start zone . external ip PORT internal ip

start zone . 70.178.49.239 8766 192.168.1.100
start zone . 70.178.49.239 8764 192.168.1.100
start zone . 70.178.49.239 8765 192.168.1.100
start zone . 70.178.49.239 8763 192.168.1.100

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, make sure that your spells_us.txt and spells_en.txt are current to your version.


If you make any changes, try it on your port forwarding setup and then on DMZ if it doesn't work. Let me know how it goes.

-Sarepean

[VoodooGnome]

Yea, my boot5zones.bat and loginserver.ini are set up right. I've ran a server before. The problem isn't in my files, I'm like 99.9% certain that it's my router causing it. I have a D-Link DI-514 and port forwarding and DMZ allow others to use my server. However, when it's not set to localhost I get 1017.

[Sarepean]

Edited:


If your DMZ is set up correctly and your port forwarding is set up correctly (one or the other should be set up and preferably not both), then it shouldn't be your router causing it which means that the error is either in your client version (which it can't be since you can connect when it's localhost) or in your files (which is unlikely since localhost works). Don't use the "no-ip.org" approach, go to whatismyip.com and use the IP they give you there as your external and use your network internal IP address.

[VoodooGnome]

Currently I only have my ports forwarded, DMZ is disabled. I've tried the no-ip.org, and the ip address whatismyip.com gives me. I can't think of anything it can be other than my router. Having the ports forwarded allows others to log on, but I, trying to log in from the host computer keep getting 1017 regardless of what I try (other than using localhost that is). Think maybe I should try getting an software update for my router?

EDIT: Downloaded the latest firmware for my router, and it didn't make any difference.

[Sarepean]

They can log in, but you can't... hmmm... weird... I'm stumped.