1017 from world server when using EQEmu public login
 

hola again

havent found this one yet on the boards but I am getting a 1017 now when logging in using the public eqemu login server.

Here's what world is kicking back:

76500 New client from ip: 192.168.42.42 port: 1361
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Client disconnected
Removing client from ip:192.168.42.42 port:1361
85019 New client from ip: 192.168.42.42 port: 1361
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Logged in: LS#3564: Psychobabble
Client disconnected
Removing client from ip:192.168.42.42 port:1361


This is a linux compile of world, version 0.3.8

obvious questions would be - why am i being 'flooded' with Logged in: msgs, what is with the 'second attempt' and why are they failing?

this build works fine to a minilogin server on my local windows box. Don't even have to change the ip to the internal network ip.

any ideas?

Thanks,

PB

Whats your LoginServer.ini look like?

-Brian

[LoginServer]
loginserver=eqlogin1.eqemu.net
loginserver2=eqlogin2.eqemu.net
#loginserver=192.168.42.42
loginport=5999
loginport2=5999
worldname=My God, What Have I Done
locked=false
account=
password=
worldaddress=24.198.*.*

[WorldServer]
Defaultstatus=
Unavailzone=

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

(worldaddress editted for security purposes)

its basically the same one that came with the eqemu 0.3.8 source

Are you connecting from a private LAN behind the server running the world/zone server?

i.e. is the server your running also your router/firewall?

-Brian

yes it is.

all i have to do is change the loginserver= to my internal windoze box running minilogin to get it to work; dont need to change the zoneserver or worldserver startup ip's to the internal IP.

I am running the 2.4 kernel via Mandrake 8.2 (blech) - very simple firewall rules.

PB

I had a simular problem...

Read the post I put here about the ~/world/console.ccp file:

http://forums.eqemu.net/showthread.p...p;pagenumber=2

And try that out. That fixed all my NAT problems. Also make sure you specify your World/Zone server to use your external IP.

-Brian

hmmm, ok I applied the patch as stated by you, btuch at the end of that post, and recompiled world. still getting the same exact problem in the world log as shown above.

i am using my external IP for both zone and world.

thanks for the help, but still not working over here - weirdness!

PB

Bah, sry that didn't help. I assume shutdown the old world, and are now running the newly compiled world?

Just checkin ;)

-Brian

LOL yeah, pretty sure i did it right. double checked after it didnt work the first time and all that good stuff ;)

but thanks for bein responsible and asking.

i simply do not have the time right now to delve into the code more - perhaps in the future.

I think the 'newbie' 3.0.4 GCC libraries are part of the problem, since from what i can tell it compiles pretty well with 2.96 and 3.2

welp, snagging Redhat 8 as we speak, and thats running GCC 3.2 right? gonna give that ago perhaps this weekend, cuz i friggin hate mandrake 8.2 for server gear. yeesh.

thanks for the help tho Brian

PB

I still can't believe RH jumped to 3.2 so quick, but yes, The new RH is gcc3.2.

I had it compiling and working with 3.0.4, but thats been months ago..

yeah, 3.0.4 was fine for showeq, but this eqemu is a bitch, to be frank.

i read the whole NAT thread more carefully and made the changes to my windows box hosts file as suggested, and substituted my worldserver name with my dyndns name for the linux/firewall box. still no luck! now I am beginning to wonder what else might be funky with my setup *le sigh*

lata