Cannot Login to login server rerun patcher. (error inside)

patman · #9 01-25-2002, 11:32 AM

Ok, heres the full text of the output of what happens when I try to log in.

------
LoginServer.ini read.
Using database 'eq' at 10.0.0.4
Loading items...done.
Loading guild ranks...done.
World server listening on port:9000
Connected to LoginServer: eqlogin.gotfrags.com:5999
New TCP connection: 10.0.0.4:3634
New TCP connection: 10.0.0.4:3636
New TCP connection: 10.0.0.4:3639
New zoneserver: #1 10.0.0.4:3636
New zoneserver: #2 10.0.0.4:3634
New TCP connection: 10.0.0.4:3640
Zoneserver SetConnectInfo: 10.0.0.4:3634: 10.0.0.4:9005
Zoneserver SetConnectInfo: 10.0.0.4:3636: 10.0.0.4:9002
New zoneserver: #3 10.0.0.4:3639
New TCP connection: 10.0.0.4:3641
Zoneserver SetConnectInfo: 10.0.0.4:3639: 10.0.0.4:9001
New zoneserver: #4 10.0.0.4:3640
Zoneserver SetConnectInfo: 10.0.0.4:3640: 10.0.0.4:9003
New zoneserver: #5 10.0.0.4:3641
Zoneserver SetConnectInfo: 10.0.0.4:3641: 10.0.0.4:9004
67997 New client from ip: 10.0.0.3 port:1073
Logged in: LS#747: patman
Sending list of guilds
97998 Unkown opcode:13601 size:2056
Client disconnected
Removing client from ip:10.0.0.3 port:1073
------

as you can see, im getting the same opcode error, and then *poof* it decides to disconnect.

heres the loginserver.ini:

-----
[LoginServer]
loginserver=eqlogin.gotfrags.com
worldname=PatMan's Server (Internal IP)
locked=false
worldaddress=10.0.0.4
account=
password=
-----

Now, I had originaly tryed this with my full install (rok, sov, sol) of eq client. So I was thinking that maby it was caused by server filter, or some other wierd option I might have set.

So I created another directory and only installed the clasic package client. I didnt change any of the defaults, and I still get this error.

I've tryed connecting to other servers on gotfrag's login, nothing.

Basicly, the progress indicator of the loading screen gets to 'loading player charcter models' and thats when I see the opcode error and disconnect message on the console.

Anyone know what this opcode does, and if theres a temporary workaround to keep the client from sending it?