IG L2.NET Private Server connection guide, no client mods. (video included)

[djpliku]

Download the video:

http://www.filefront.com/15529175/L2.NET-IG-LOGIN-GUIDE.rar/

 

What this video covers:

 

1. Downloading the tool

2. Lam's ipjack

3. Obtaining the ip and port

4. Lam's ipjack setup

5. L2.NET IG setup

6. Logging into the Lineage 2 client

 

1. Downloading the tool (pre video) PASSWORD IS l2net

Well, first off download the following tool.

http://ltwonet.com/showthread.php/4479-simple-TCP-conn-rerouting-program-%28IP-Jack%29

direct links

http://ltwonet.com/downloads.php?do=file&id=24

Mirror

http://www.inxile.ltwonet.com/download/tools/Lams_IP_jack.rar

http://www.fileshost.com/download.php?id=B88D15E41

 

2. Lam's ipjack

Extract the previous tool and create a shortcut to somewhere convenient. Google winrar to extract the files.

 

3. Obtaining the ip and port

Firstly, close any internet needy programs completely, this includes torrents and downloads.

 

Open your start menu at the bottom left corner, access your command prompt and enter cmd and press enter (if you do not see your command prompt, simple search for cmd.exe in the search field).

 

Then, launch the L2 client for your server. MAKE SURE IT IS NOT MODIFIED, enter your username and password as if you were login in normally and press enter to log in, switch to your command prompt window, type netstat -n

 

This will give you your server's ip and port, look for an ip which is USUALLY associated with the port 2106 and has the state of "ESTABLISHED". NOTE, port 7777 is NOT your login server's port, this is your gameserver port. You do not need this port as it is automatically generated by L2.NET.

 

Example of an ip would be

 

24.244.241.10:2106

24.244.241.1 :being the ip

2106 :being the port

 

4. Lam's ipjack setup

open "manager.exe", it should pop up in the bottom right corner of your screen as an explosion looking icon in your tray. Right click it, select "EDIT CONFIG", a text window will appear. What this application does is that it takes an ip and redirects it to another,

 

for example.

"l2.exe" 74.86.137.169 127.0.0.1

 

Will grab the application L2.exe's connection which is defined as 74.86.137.169(your server ip) and redirect it back to your computer which is 127.0.0.1(your L2.NET client).

 

So go ahead and copy paste my line, but edit the server's ip to your server's ip instead.

"l2.exe" xxx.xxx.xxx.xxx 127.0.0.1

You should also note, if your server is launching from L2.BIN, you should put L2.BIN instead of L2.EXE

"l2.bin" xxx.xxx.xxx.xxx 127.0.0.1

 

Lastly, right click on the manager.exe icon once again and select "Install filter", note that this shouldn't let you log into the Lineage 2 server now, go ahead and try it out to make sure you have the correct ip. If you somehow manage to login to the server, you messed up in obtaining your ip or installing the filter.

 

 

5. L2.NET setup

 

L2.NET WEB installer

http://ltwonet.com/showthread.php/1972-L2NET-Web-Installer

 

The L2.NET setup is pretty simple, update to the latest version as often as possible to prevent bans, bugs, crashes. Select "File" then "logon window" now, SELECT THE CORRECT CHRONICLE FOR YOUR SERVER, if you do NOT do this, the items will show up buggy and wont work! Edit any values needed for your server such as the token or protocol if they changed it. Then open the IG login tab. At first it may look a bit scary, but it really isn't, and I will walk you through it...

 

Firstly, copy your server's ip in the first box.

 

The second box under the one you put your server's ip is a box for a port. If your server has changed the port, do so as well.

 

The third box is for advanced settings which I wont cover, leave it as it is unless you know what you are doing.

 

The fourth box should be the same as the second box, the only difference if that this is your client's port. Once again used for advanced protection bypasses which aren't covered in this tutorial. So go ahead and put your server's port as well.

 

The L2.NET setup is complete, you can go ahead and click Listen.

 

6. Logging into the Lineage 2 client

Now, go back to your Lineage 2 client. Go back to the login screen where you input your user name and password. Log in as you would with your user and password. At this point, you should now see writing in the L2.NET chat box, if you do not, then you messed up obtaining some information or you forgot to install the filter from manager.exe.

 

Hopefully this clears up some of your questions, if there's something not covered in this tutorial, please let me know, it has been a long time since I was new with L2.NET, and might of overlooked some steps.

 

Thanks for reading, happy botting!

 

Link Broken for            http://inxile.ltwonet.com/download/tools/Lams_IP_jack.rar

Not Found

The requested URL /download/tools/Lams_IP_jack.rar was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

[mpj123]

thanks for reporting, I have been trying to reach inxile for a while now...not sure if he will fix the link. Use other download mirrors in the meantime.

[FreakaDDD]

Straight to the point. I`m using windows 7 x64 bits atm, I instaled l2net 385 on my pc and a friend made the entire configuration, and it worked, without me having to use, IPJACK(that was on an a gracia server)

Now I`m trying to make l2net to work on a freya server, I installed the 386 version everything works, except IP JACK. I deactivated all my firewals and anti virus and any other software for protection and still nothing.

BAsically i hit install filter and it doesnt install one, what could be the problem & how can I solve it.

 

BTW: a friend of mine made the same config, except the fact that his pc works on windows 7 x32bits

The bigged difference that we saw, was the process naming in the task manager, under the process tab. ON his 32 bits was written l2.exe on my 64 bits was named l2.exe *32

What would you suggest

We tried to log in OOG, and it works, we were able to bot it, however on the IG the l2net doesn`t seem to recognize the game

 

 

2 hours later i tries a guide regarding a loopjack, still nothing, I`m desperate here, please do replay back

 

 

 

The server is l2-divinity.com

[mpj123]

sounds to me like you are missing the DLL files in your system32 or system,

 

http://www.filefront.com/thankyou.php?f=16759171

 

extract first and run the batch file

[ciasteczkowyp]

I tried the same thing on freya and there's problems my friends :(

 

1. First of all You need a clean epilogue + system

http://www.gamershell.com/download_53076.shtml

2. Get fyree's wildcard and paste dsetup.dll in system

http://fyyre.ivory-tower.de/

3. Get the latest L2.NET with map + data packs in "CT1 - Freya L2NET" tab.

l2net.insane-gamers.com/

4. Backup Your system to some folder like bkup or sth.

===========================================

GETTING THE LOGIN IP

===========================================

5. I (If Yout server has a custom system to download)

a)Remove system folder and copy Your server's system instead

b)click log in

c)open command prompt when the eula shows up

d)type

"netstat -n"

e)write down the server's IP

(It will be the one ending with port :2106)

f)close the game.

g)remove the system

h)restore Your clean system from that bkup directory.

or

5. II Write the IP of the server's login (if the server writes it's hosts), the server's ip

will be the one before l2authd.lineage2.com

============================================

Once You've done that the rest is simple

6. configuring l2.net to Your l2 installation

a)Go to Your l2.net installation folder

b)Find a .txt file named

"interface.txt"

c) Open it with notepad or sth like it

d) find a line starting with "C:\Program Files\..."

e) replace the line with the place where Your l2.exe is, for me it would be

"D:\Epilogue\System\l2.exe"

f) close and save the file.

7.  editing hosts

a)go to c:\Windows\System32\Drivers\Etc\Hosts

b)edit it with notepad or other text editor

c) place Your host like like this

127.0.0.1 l2authd.lineage2.com //this will route all data into Your local l2.net executable.

below you can put Your server's ip for easy copy/paste

#123.123.123.123 L2authd.lineage2.com

=================================

Running the IG client

8.

a)run l2.net, choose epilogue and click IG

b)in IG setup just paste Your login server's IP into l2.net, don't touch anything else, the ports are all ready (unless Your login server has a different port)

c)click "listen"

d) run l2.exe

e) login

 

Voila, You're safely IG without any 3-rd party mods done to Your system.

 

 

//For some reason I have no idea how to do that on Freya >.<

 

Edit: Got it working for freya:

http://www.maxcheaters.com/forum/index.php?topic=181013.0 <= get the system from this guy

do the same steps just with freya client (so client path will be different)

when connecting with l2.net select freya (386 release) and enter Your server ip + click listen

log in, now You're IG with freya ^^^

[Semyazza]

hey i have weird problem using l2net

i connect successfully but l2net dont get any char list

server is runing on interlude  (avalon)

server ip: 212.59.22.134:2106
www: http://avalonas.hogvartsas.lt/index.php

i use 384 version of l2net

those are my logs:

22:57:54 :[gameserver - keys forwarded to client

22:57:54 :[gameserver - got packet encryption key

22:57:54 :[Welcome to the game loop

22:57:54 :[client -> bot gameserver : connected

22:57:54 :[valid protocol... forwarding to game server

22:57:54 :[ig - starting bot threads

22:57:54 :[bot -> gameserver : connected

22:57:54 :[bot -> gameserver : opening

22:57:54 :[valid protocol... waiting for game server connection

22:57:54 :[protocol version: 746

22:57:54 :[client -> bot gameserver : connected

22:57:53 :[bartz: 862/2000

22:57:53 :[loginsend - got the server list; modifying packet and sending to client

22:57:51 :[login ok

22:57:50 :[bot -> loginserver : connected

22:57:50 :[bot -> loginserver : opening

22:57:50 :[client -> bot loginserver : connected

22:57:24 :[client -> bot gameserver : using port 7777

22:57:24 :[client -> bot gameserver : waiting

22:57:24 :[client -> bot loginserver : waiting

22:57:17 :[loaded saved enterworld packet

22:57:17 :[loaded saved blowfish list

22:57:17 :[loaded saved server list

 

thanks for any help!

[bygru]

ha ! this is what i was lookng for ! great idea, great guide thanks a lot. works for me ofc IL off server

 

edit: amm i connected once whidout any problem and after i loged out and wanted to login after about half hour i got ban for account, when i created new one and tried to connect i got next ban and after 3rd try i got ban for ip any any idea why in first time server didint detected my l2net and in next connections they discovered me and baned ? the server is l2exite

[ciasteczkowyp]

server might be using custom packet with it's system to verify connection. You'd need to post that in here I guess and wait... or You just might have been doing something with supernatural speed like unclicking ancient tomes of the deamon with less than a 100 millisecond delay. <= that's a 100% bot giveaway ^^

[bartex85]

Hi Im have this problem with im loged in l2net for Avalonas serwer

 

http://screenup.pl/?l=VGJRS52

 

http://screenup.pl/?l=XMSDR8B

 

When im change system adres for 127.0.0.1 ing log im have Acess Failed but im no change and use this Guide Im have te shame problem on screens somebody have maybe any idea ?

[vartininkas]

AMAZING MAN THANKS!!!!!!!!

[ksn12250]

Thx Man So i questions l2walker script use in l2.net ?

 

[skip]

any suggestions how to check for protocol version?

[mpj123]

logging in with IG will tell you the protocol

[Voireusi]

Someoane can help me connect with l2net on the new server rpg 15x http://www.rpg-club.com/en/p-news

Gracia final

[Voireusi]

i log on the game with l2net all god but i ghet this when i want o use it

9:27:28 PM :[ERROR: crash: GameSendThread : An existing connection was forcibly closed by the remote host

9:27:27 PM :[ERROR: crash: GameReadThread : An existing connection was forcibly closed by the remote host