Help with logging on to a minilogin

noraa58 · #1 03-07-2004, 01:46 PM

Hi. I have a friend who is running a server and ive been trying to log onto his server, but can't. I get the dreaded 1017 error. Is the problem on my side? how can i tell? what can i do to fix it?

Im running win2k with sp4

datarate.txt

Code:

8.0

eqhost.txt

Code:

[Registration Servers]
{
"68.123.41.134:5999"
}
[Login Servers]
{
"68.123.41.134:5999"
}

those are his ips.

is there anything else i need to do? I have a firewall, but i have a few ports fowarded. they are 5999, 3690-3770, 7990, 7995-7999, 9000. i dont know why i need all those fowarded but thats what he said... so any clue? should i get him to post all the server based stuff?

noraa58 · #2 03-07-2004, 05:21 PM

ok, here is all the info of the server im trying to connect to

db.ini

Code:

[Database]
host=localhost
user=********
password=*********
database=eq
compression=off

loginserver.ini

Code:

[LoginServer]
loginserver=192.168.1.125
loginport=5999
worldname=SiilverWolves
worldaddress=192.168.1.125
locked=false

[WorldServer]
Defaultstatus=0
Unavailzone=

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

eqhost.txt

Code:

[Registration Servers] 
{ 
"localhost:5999" 
} 
[Login Servers] 
{ 
"localhost:5999" 
}

minilogin.exe

Code:

LoginServer.ini read.
MiniLoginAccounts.ini read.
Server mode: Standalone
Login server listening on port:5999

boot5zone.bat

Code:

C:\eqemu\CVS\eqemu\eqemu\NewSource\Build>REM: ****Read this first!!!**** 

C:\eqemu\CVS\eqemu\eqemu\NewSource\Build>REM: This file requires your real IP in the place of "YourIP" when you are connecting 

C:\eqemu\CVS\eqemu\eqemu\NewSource\Build>REM: To the EQEmu Loginserver. 

C:\eqemu\CVS\eqemu\eqemu\NewSource\Build>REM: When you are using minilogin, Replace all IP Addresses to say 127.0.0.1 

C:\eqemu\CVS\eqemu\eqemu\NewSource\Build>REM: If you still get errors try using localhost instead of 127.0.0.1 

C:\eqemu\CVS\eqemu\eqemu\NewSource\Build>REM:--------------Start-----------------------

world.exe

Code:

[Status] CURRENT_WORLD_VERSION:EQEMu 0.5.5-DR1
[Status] Loading variables..
[Status] Loading zones..
[Status] Loading items..
[Status] EMuShareMem loaded
[Status] Loading items from database: count=28223, max id=69137
[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
Assassinating people that whine about horses...done
TCP listening on: 192.168.1.125:9000
World server listening on: 192.168.1.125:9000
Connected to LoginServer: 192.168.1.125:5999
25578 New TCP connection: 127.0.0.1:1819
New zoneserver: #1 127.0.0.1:1819
Zoneserver SetConnectInfo: 127.0.0.1:1819: 127.0.0.1:7999
25672 New TCP connection: 127.0.0.1:1820
25672 New TCP connection: 127.0.0.1:1821
25687 New TCP connection: 127.0.0.1:1822
New zoneserver: #2 127.0.0.1:1822
New zoneserver: #3 127.0.0.1:1821
New zoneserver: #4 127.0.0.1:1820
25718 New TCP connection: 127.0.0.1:1823
New zoneserver: #5 127.0.0.1:1823
Zoneserver SetConnectInfo: 127.0.0.1:1820: 127.0.0.1:7998
Zoneserver SetConnectInfo: 127.0.0.1:1821: 127.0.0.1:7997
Zoneserver SetConnectInfo: 127.0.0.1:1822: 127.0.0.1:7996
Zoneserver SetConnectInfo: 127.0.0.1:1823: 127.0.0.1:7995

I honsetly dont know what most of that means, but thats the server stuff im trying to connect to. hope you can help

smogo · #3 03-07-2004, 05:52 PM

your friend is using LAN/loopback ips for his server / minlogin setup.

This means the server can be accessed using these adresses from his LAN, but not from your's, as you connect using his external adress.

When you connect to the minilogin server, it tells your eq client that server is running on '127.0.0.1' (from LoginServer.ini), where it means 'localhost' on server's point of view, but when EQ client tries to connect, it uses '127.0.0.1', which means localhost (your machine) for EQ client.

Solutions :
- if you are on same LAN (what i doubt), change 127.0.0.1 to the server's ip adress (192.168.x.x) everywhere, it should be a better start.
- if on seperate subnets, tell your friend use EQEMu Login servers. Your friend is shy and doesn't want to show up, well, then there are solutions using minilogin, but you'll get into painfull NAT issues.

i hope this helps.

samandhi · #4 03-07-2004, 11:53 PM

Also, you are not the one that needs any ports forwarded, you simply need to open up ports for the firewall. You also need to make sure that you are pathed up to current (at least in your backup directory), as you will not be able to connect on a 0.5.5 DR 1 server with any patch older than Feb 10th...

noraa58 · #5 03-08-2004, 10:52 AM

alright, thanks to both of you! as to the question of using a minilogin, I think that would be preferable because he has somewhat limitedBw and the server can only handle like 4 people. So any explination on how to do that would be much appreciated

samandhi · #6 03-08-2004, 10:54 AM

Running minilogin IS set up for private use. His server will NOT show up on the EQEMu Loginserver. So that should solve the BW issue. What exactly are you wanting an explanation on here? hehe

noraa58 · #7 03-08-2004, 11:11 AM

Oh, i see. I thought it would display him as a server to log into or something and others could eat his BW. tanks

samandhi · #8 03-08-2004, 11:32 AM

It will only show up to those that he gives his IP address to (so they can connect to that server, and they change their eqhost.txt to reflect that IP they want to connect their client to.

noraa58 · #9 03-08-2004, 11:34 AM

ok, now he wants to know how to lock his server and put a password on it. any ideas?

RexChaos · #10 03-08-2004, 11:37 AM

Quote:

Originally Posted by noraa58

ok, now he wants to know how to lock his server and put a password on it. any ideas?

Yes have him post here instead of making you the middle man. Hehe...

AFAIK there's no way to password protect the server, but you could move the start area into lava and everyone is instantly killed when they log in. Hehe...then he can move your character to a safe point.

samandhi · #11 03-08-2004, 11:44 AM

There IS a way to essentially password protect it. When you change it to locked = true, no one will be able to log into it exept people with server_op status... Thereby making it so no one can log in... If you want to take it a step further and allow everyone that logs in this way server_op status, but no real power, just set (in addon.ini) all the commands you dont want those people to have to 250 not 200 (which is server_op), then you will have to set up your account to be server_op but with 250 status... Now you will have access to all those commands but the other people logging on will NOT...

noraa58 · #12 03-08-2004, 11:45 AM

ok, now i guess its my problem... He has the server set up and says otehr people logged in but i still get a 1017 error when i try to play

samandhi · #13 03-08-2004, 11:46 AM

Look at the one stop error guide in general support for 1017 error...

noraa58 · #14 03-08-2004, 11:57 AM

meh i guess it wasnt my problem, its fixed! I AM IN!!!! thank you guys, you are a really good support network

samandhi · #15 03-08-2004, 02:04 PM

Ironic thing is that no one that has posted in this thread is officially a support helper <smile>