0.6.0-DR2 setback

[kedobin]

I'm running eqemu 0.6.0-DR2 on two computers. They both work when playing using their own minilogin. I decided to try and network them, so they can be on the same server, but I ran into a few problems. After a couple adjustments here and there, I managed to get down to error 1017. This occurs on both machines, one of which is the server computer.

I did some further testing - first I made sure both could still minilogin, which both did successfully. Then, I made the server computer use its IP instead of 127.0.0.1, and I found that for some reason, the emu won't accept the IP.

Before I attempt getting the other comp to work with this one, I want to see what I'm doing wrong on the server to not accept its own IP.

I have turned off all firewalls to my knowledge. I am running a router between the two comps, but I've set it to reserve the IPs of each of these machines.

Thanks for any help.

Server comp adjusted files:
eqhost.txt

[LoginServer]
Host=192.168.1.3:5999

Boot5zones.bat

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

if NOT exist spells_us.txt goto NOSPELL

start zone . 192.168.1.3 8780 127.0.0.1
REM: start zone . 127.0.0.1 8781 127.0.0.1
REM: start zone . 127.0.0.1 8782 127.0.0.1
REM: start zone . 127.0.0.1 8783 127.0.0.1
REM: start zone . 127.0.0.1 8784 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------------------------

db.ini

# READ README.TXT!

[Database]
host=192.168.1.3
user=alteredname
password=alteredpass
database=eq


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

LoginServer.ini

# READ README.TXT

[LoginServer]
loginserver=192.168.1.3
loginport=5999
worldname=Qeynburrow Plains
worldaddress=192.168.1.3
locked=false
account=
password=


[WorldServer]
Defaultstatus=0
Unavailzone=

[ChatChannelServer]
worldshortname=
chataddress=
chatport=

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

World.exe output, after 1017. Before 1017, no visible error output.

[Status] CURRENT_WORLD_VERSION:EQEMu 0.6.0-DR2
[Status] Loading variables..
[Status] Loading zones..
[Status] Clearing groups..
[Status] Loading items..
[Status] EMuShareMem loaded
[Status] Loading items from database: count=36965
[Status] ./LoginServer.ini read.
[Status] Loading guild ranks..
[Status] Loading ./addon.ini..
[Status] Loading EQ time of day..
[Status] Deleted 0 stale player corpses from database
[Status] Deleted 0 stale player backups from database
Please don't make me a levelme server. :(
TCP listening on: 192.168.1.3:9000
World server listening on: 192.168.1.3:9000
Setting World to MiniLogin Server type
Connected to LoginServer: 192.168.1.3:5999
41907 New TCP connection: 127.0.0.1:1328
New zoneserver: #1 127.0.0.1:1328
Zoneserver SetConnectInfo: 127.0.0.1:1328: 192.168.1.3:8780
72157 New client from ip: 192.168.1.3 port: 1330
Login with '10516' and 'QMV1I7HNG7'
192.168.1.3: Wrong name/pass: name='10516'
Removing client from ip:192.168.1.3 port:1330

[kedobin]

Whether people assumed I searched beforehand or not (which I did attempt), I did finally find out how to word the search.

It's highly unlikely, but if someone else happens to come across this forum post due to a problem like this, you have to modify your hosts file.
I did notice that you do not have to register anything if you do not plan on having online play (I haven't tested if this would work online). You just need to type the ip address, then afterward type what the name is supposed to be.

127.0.0.1 localhost
192.168.0.87 thisworkstoo.net #not a real dns, but still works on my lan

I can even ping this name for the ip from a machine with an altered hosts file, and the ping succeeds.

**OFF TOPIC**
BTW, is it possible to permit searching of 3-letter words? If a person is wanting to know about a lan or nat, they can't get very far due to this restriction (that, and not too many people would want to type local area network or network address translation when they can use these acronyms).