Right, take a looksie here. Last night I had to figure this out on my own, and well... I did it.
This is my LoginServer.ini file.
Code:
[LoginServer]
loginserver=localhost
loginserver2=localhost
loginport=5999
loginport2=5999
worldname=Xelnagan's
worldaddress=192.168.0.130
locked=false
account=
password=
[WorldServer]
Defaultstatus=
Unavailzone=
[LoginConfig]
ServerMode=Standalone
ServerPort=5999
UplinkAddress=
UplinkPort=
UplinkAccount=
UplinkPassword=
Notice how the worldaddress is not 127.0.0.1 or localhost? Yeah, if you leave it like that, the additional clients logging on will be trying to log onto a server on their own computer, which is non-existant, hence the 1017.
This is my Boot5zones.bat file.
Code:
start zone . 192.168.0.130 7995 192.168.0.130
start zone . 192.168.0.130 7996 192.168.0.130
start zone . 192.168.0.130 7997 192.168.0.130
start zone . 192.168.0.130 7998 192.168.0.130
start zone . 192.168.0.130 7999 192.168.0.130
Again, this needs to be the host computer's IP and not 127.0.0.1 or localhost, otherwise the additional clients will be trying to load it from their own computer... Again...
This is my MiniLoginAccounts.ini.
Code:
192.168.0.130 eqemu eqemu
192.168.0.1 joe blow
Each client's log account must be bound to THEIR IP, otherwise they will be accessing eqemu every time(yes, even if you use different login information). I also noticed it wasn't accepting accounts until I booted up EQAdmin and set the passwords in the database for the accounts.
Last, but not least... This is my eqhost.txt for the other computers/clients, the host should be using the second one I list.
Code:
[Registration Servers]
{
"192.168.0.130:5999"
}
[Login Servers]
{
"192.168.0.130:5999"
}
Code:
[Registration Servers]
{
"localhost:5999"
}
[Login Servers]
{
"localhost:5999"
}
Replace 192.168.0.130 with your IP and everything should be fine(with the exception of replacing account names, passwords, and user IPs in MiniLoginAccounts.ini).
Good luck with that =D I've tested it, and it's working like a charm.
- Xelnagan