So I'm doing this first time.

2 days without any luck.

I downloaded the server on a Virtual Box. Just to see how it's all configured.
https://mega.nz/file/h4gkzY7I#ilmkWW38d-HVSstazu6IHSN8h18jlc5whv-ZrtejyP8

But server VIRTUAL BOX OS was expired, same as MSSQL. So I could't launch it there.

Only what I cloud - download all Server files.



Good thing there, that it have SQL scripts and HAuthD.

With a tutorial on https://bitbucket.org/Bumblemumps/l2homage/wiki/Home
I started to configure it.

1. I have server with Windows Server 2019 and MSSQL 2019.
2. I changed 6_lin2world.sql lines, where it needs SQL User and Password data. (To one that is my Db User and Db password)
3. I created all databases that's needed, imported all sql scripts and changed dbo.server row.

5. For all databases I created ODBC files



6. In hAuthD.ini I changed lines for DB connection



7. I added account with AccountManager.
8. I opened all needed (I hope so) ports

Now it's time to start Server

1. hAuthD.exe
2. CachedMyExt64HF.exe
3. Loader.exe
4. L2ServerMyExt64HF.exe
5. L2NPCMyExt64HF.exe

In the end, it looks like this



Ok, now it's time to start client.
I had one clean, I connected with it to a Java Server. So I changed l2.ini ServerAddr to mine (I hope here it's all that needed).

And started!

It's connected me to a server choose screen



But when I click CONFIRM, it shows me ERROR



Please help me in solving that! I just don't know what else to do.

Maybe It's a client issue. If like this, please help me with finding it and making GOOD system folder.

Thank you for any response!

you dont try to login from same pc right?

also i've heard that newer mssql can cause issues maybe trying to go backwards compatible will help you even with some errors

i assume port/firewall is configured ip's are correct in l2.ini and gameserver database so.. not much left to check you are one step before the working solution its fustrating i know

Looks like client issue, more specific wrong protocol you need to find the correct system and/or try to disable cliext

Nope. This was very tricky part.

My hosting provider smokes something illegal. That's the reason why they binded port 7777 for remote connection.

7777 is the port that uses LINEAGE. So thats why all PTS didn't worked on my server...

I still didnt get how I found this.

The issue of virtual machine system expiration and MSSQL expiration is easily resolved.