At a roadblock

You should only be able to connect with kPT or jPT clients to THAT server... This is what I've been saying. The protocols on the ePT and bPT clients are not compatible, even if you hex the port from 10007 to 10009.

It's like trying to run a WoW pre TBC client on a post FT MaNGOS set up. They changed the database, the encoding, the packet size, added packet globbing. It's totally different. (since you seem to know a bit about WoW servers)

This probably gets lost in my overkill responses. My bad.

I would imagine the reason you get wrong account messages from 1871 (anything from 1855 - 2400 I suspect) is one of the following:-
1) You have admin set in hotuk.ini on your client, but neither your user name, nor the IP 127.0.0.1 is granted *ADMIN in your server hotuk.ini.
2) Your account has been blacklisted for trying to connect with the wrong kind of client too many times.
3) You have a specific version range in your server hotuk.ini, and 1871 is not within it, or you have the CLSafecode option on.
or
4) Your server is not actually connected to your SQL database correctly, and therefore cannot confirm your user name and password.

Option 4 is most likely IMHO. 3 should give a "Wrong version" message, but they can vary with client translation. Again 2 should show "Account banned" or such, but may be badly translated. Option 1 and the CLSafecode part of 3 often present as a DC on entering the game world, or when trying to auth up.

So, advise for the most likely cause:
If you use ODBC, recheck the SQL connection for c8master. If you use sql.dll and clan.dll, they can be a pig to set up right, and they can be a pig to find ones that even work at all... I'm still struggling. ^_^

Looks like I need to rethink my approach to this problem.
Here is a recap of where I am at.
1. Server is 619 and using the Endless tower exe
2. ODBC is configured (c8master)
3. SQL swever is done databases added
4. Scripts executed
5. Hotuk.ini on server side modified
6. Sqldll.reg modified and executed
7. Char and Field copied from client
8. Sql.dll Provider=SQLOLEBD.1 (removed the .1)

The following is the client side
1. Ept client installed with 3124 as the base versiom
2. copied and removed the xtrap from 3124 (using this client)
3. Modified Ptreg.rgx
4. Modified and executed the Ptreg registry
5. I have no Hotuk.ini on the client

So there is where I am atm.
I feel like I am back in school lol

I don't see the step where you add a user account to your database... It's an easy one to forget you have done.

Aside from that, I think if you put >this< in your server folder, and ran it instead of the ET2 one, you could log in. If not, then I suspect the database connection is wrong somehow.

Bare in mind that that server is VERY OLD. It won't support much, I doubt it will go beyond about level 70, and probably doesn't support Ice, Fire, Lost etc. Let alone Endless Tower. But you should be able to log in.

To log in to the ET server, you NEED to stop using English clients. You can use a translated Korean or Japanese client, but not an English native one.

If you still can't log in with that server... I would say rename sql.dll and clan.dll (Just sql.dll.old and clan.dll.old will do) and shut down and reload your server before trying again.

If that doesn't work, remove SQL (c8master) from ODBC and re-apply that operation, carefully. That's not to say you weren't careful the first time, but I have to do this a lot, and you get careless after the 7th or 8th attempt, and if you stuff it up, I have had it lock me out of SQL all together many many times. :'(

I will try and use that old server to test with, and yes I did create an account..

I was just about to switch my efforts to the UPT server/c;ient
but I will hold of on that

Thanks again for the time and efort of helping me out

I am finaly successful, using kpt-ET and the Kpt1871 ET client
What I did was to start from the begining, ao many thank to all
who posted here to help me out...I need to write down what I did so I can pass it on...

Cheers:w00t: