people disconected from my server when trying to enter the w

[sandy]

i m under windows xp no router just windows xp
i m using eqlogin server ( not mini )
i can connect to myself without problem
but anyone else who tries to connect to my server is disconnected after they press enter the world at character creation after the same unknown opcode sent :
here is what happened in world.exe :

Guild Send Request...
Received 0xe521.
Unknown opcode: 0x56e0 size:0
Unknown opcode: 0x5af0 size:0
Unknown opcode: 0x6310 size:0
Unknown opcode: 0x006c size:0
Unknown opcode: 0x72c0 size:0
Unknown opcode: 0x75f0 size:0
Unknown opcode: 0x7af0 size:0
Unknown opcode: 0x7fe0 size:0
Unknown opcode: 0x8704 size:0
Unknown opcode: 0x0073 size:0
Unknown opcode: 0x76ff size:0
Unknown opcode: 0x7aff size:0
Client disconnected
Removing client from ip:65.128.126.186 port:4412

they can connect to other servers but not mine
what do i have to do plz help =) ?????

[Bladelock]

I have been havin the same issue except its for me only. No one else logs to my server. and it tells me that the zone is unavailable. and the same message you get on the world.exe

ZoneID = 0
Couldn't find/read ./cfg/j.cfg. (returning -1)
Couldn't find/read ./cfg/.cfg. (returning -1)
Corrupt (or nonexistant) zhdr file ./cfg/.cfg -- fread count = -1 (should be 170
)
Using default zone header data...
-----------
Zone server 'j' listening on port:7995

I dont understand this too much, But looks like to me its not Finding any of my server files. Is this right? and how so? Maybe this is turning into something totaly different.

Zoneserver connection lost: 127.0.0.1:2431 (127.0.0.1:7995)
Removing zoneserver: 127.0.0.1:2431 (127.0.0.1:7995)
Zoneserver connection lost: 127.0.0.1:2430 (127.0.0.1:7995)
Removing zoneserver: 127.0.0.1:2430 (127.0.0.1:7995)
Zoneserver connection lost: 127.0.0.1:2429 (127.0.0.1:7995)
Removing zoneserver: 127.0.0.1:2429 (127.0.0.1:7995)
Zoneserver connection lost: 127.0.0.1:2428 (127.0.0.1:7995)
Removing zoneserver: 127.0.0.1:2428 (127.0.0.1:7995)
Zoneserver connection lost: 127.0.0.1:2427 (127.0.0.1:7995)
Removing zoneserver: 127.0.0.1:2427 (127.0.0.1:7995)
Client disconnected

[devn00b]

Sandy many of us are having these problems...check my post under *** Attention Dev team ***.

[Norvak]

I have a Dyndns system set up so that people can connect to my machine. I've got a hunch, but I havn't tested it, so it's going to take a little explaining. What I've done is edit boot5zones.bat to read:

@echo off
start zone . malice.homedns.org 7995 malice.homedns.org
start zone . malice.homedns.org 7996 malice.homedns.org
start zone . malice.homedns.org 7997 malice.homedns.org
start zone . malice.homedns.org 7998 malice.homedns.org
start zone . malice.homedns.org 7999 malice.homedns.org
exit
cls

Normally it's set to read:
start zone . malice.homedns.org 7995 127.0.0.1
etc..
exit
cls

Now, the hunch I have is that the World Server hands off to one of the zone servers, as is evident when I log in and it says:

Zoneserver SetZone: 127.0.0.1:7775
Client disconnected
Removing client from ip: xxx.xxx.xxx.xxx:3282

That is what I see when I connect and can play. So what I'm seeing happening maybe is that it's serching for the appropriate zoneserver at 127.0.0.1 on the client machine instead of on the server machine. So I altered it to connect to malice.homedns.org and booted it up. Logged in and it worked fine for me, but I need someone else to log in and test it.

Hope that made sense.

[Korisha]

ok, I tried dyndns and found that you HAVE to specify both sides as one or the other, you cant mix them, if you do the server confuses itself, its like people who try zone . localhost 799* 127.0.0.1 it just doesnt work, the mix messes with the program for some reason (dont know why, it just seems to, I'm not a coder, so I dont know specifics) but when I set mine up, I specified IP on both sides (not the little 127.0.0.1 but real IP) and it works just fine, only errors I've had were today, when my isp was being stupid, and the occasional dual namers which I mentioned in the attn dev team post.... hope that helps, if not, sorry for wasting your time having to read my crappy advice

[Norvak]

Progress!....maybe

Ok, here goes. I downloaded Port Detective because something is really f*cked in the ports.

Looking through the login process from server select to being in-game, I see that the world server hands off to the zone server. No problem.

People who can't get connected even have this. They get passed the world server, but no further than that.

Here's what I discovered:

World server auto looks at port 9000, I checked it with zone detective, shows "in use".

Connected all the way into the game and hit the zone server on port 7999. Got connected.

Checked with port detective. Shows 7999 as "Free/not in use" So something is amiss here. I dunno what, but it looks like the ports are a bit screwed up. That zone server would be at 'malice.homedns.org:7999' not '127.0.0.1:7999'.

Any ideas?

[Korisha]

make sure both sides of your zone . malice.homedns.org 799* have the malice.homedns.org it should look kinda like

zone . malice.homedns.org 7995 malice.homedns.org
zone . malice.homedns.org 7996 malice.homedns.org
etc etc


if you specify an outside ip/host for one, you have to do it for both, or else anyone who tries to connect to your computer will crash out with odds and ends errors, espically if it looks like

zone . malice.homedns.org 7995 127.0.0.1

because when the world passes it to the zone, the zone will send THEM (the client program) the command to load zone at 127.0.0.1 which if you dont know is the localhost command, the computer itself, meaning your system on zoneload is telling the client to load the zone from its self machine, the machine the client is running on....

this for the most part is only speculation(I'm not a programer), but its what fixed the troubles I had on my server, and now only a couple people have troubles, and its usually when trying to go into zones that I have had prior zoneserver disconnects when loading, so its really nothing that worries me, as I am sure that my little piddly error will get fixed on the next update :)

Hope it helps, if not, sorry to have bothered your time

[Norvak]

Yes, I keep malice.homedns.org on both sides.

It's one of the things I've been looking at. :)

[Korisha]

if that doesnt work, you might have to try specifying the actual ipaddress, some of those "homedns" and "dyndns" host type programs dont allow some of the "odd" ports, 7999, 8888, and so on, you need to check your program out to make sure that the primary host doesnt screw with the port