Fix Lineage Server Login & Connection Errors

So you downloaded a new server, extracted the files, but now you can't get past the login screen. Don't worry — 90% of Lineage 1 private server issues are caused by the same 3 problems (based on player reports). Work through these fixes in order and you will be in-game within 10 minutes.

TL;DR: "Login Failed" is almost always a wrong IP in Login.ini or a firewall block. Game crashes are usually missing DirectX 9.0c. Fix those 2 first and 90% of issues resolve immediately (based on player reports).

Why Does "Server is Terminated" or "Login Failed" Keep Appearing?

This message means your client sent a login request and got nothing back. The connection is failing somewhere between your PC and the server. Work through these in order — start with the cheapest fix and escalate.

Fix 1: Check your Login.ini or Server.ini:

- Open the Login.ini file in your Lineage folder with Notepad.
- Make sure the IP address matches exactly what is listed on the server's website. A single wrong digit sends your client to a dead address.
- Watch for a stray space, a leading zero, or a copied port number tacked onto the IP. The IP and the port are usually separate fields — don't paste 192.0.2.10:2000 where only the IP belongs.
- Some servers publish a hostname (like login.example-server.net) instead of a raw IP. If so, the hostname resolves through DNS — see the DNS section below if it won't connect.

Fix 2: Run as Administrator:

- Right-click Login.exe -> Run as Administrator. Lineage writes to its own folder, and on Windows 10/11 a folder under C:\Program Files is read-protected. Without admin rights the client silently fails to update its config and drops the connection.
- To make it permanent: right-click -> Properties -> Compatibility -> check "Run this program as an administrator".

Fix 3: Firewall or antivirus blocking:

- Windows Defender Firewall often blocks private server connections because the client is unsigned. Go to Windows Security -> Firewall & network protection -> Allow an app through firewall, and add both Login.exe and Lineage.exe for private and public networks.
- Third-party antivirus (Avast, AVG, Bitdefender, Kaspersky) frequently flags private server clients as a false positive. Old game executables trip heuristic detection because they are unsigned and modify their own files. Add the entire Lineage folder to your antivirus exclusion list, not just the .exe.

Fix 4: Port not reachable:

- Lineage clients typically talk to the server over a specific TCP port (2000 is the classic default, but many private servers use a custom port). If your firewall, router, or ISP blocks it, you get "Login Failed" even when the IP is correct.
- Test whether the port is open: open Command Prompt and run Test-NetConnection [Server_IP] -Port [port] in PowerShell, or use ping to confirm the host is up first. If the port test fails but ping succeeds, the server is up but the port is blocked or the game service isn't running.

Why Does the Game Crash Immediately After Opening?

Cause: Missing DirectX or Visual C++ Redistributables.

Fix: Download and install the All-in-One Runtimes package (search for "AIO Runtimes"). Lineage 1 is a 25-year-old game and relies on legacy DirectX 9.0c libraries that Windows 10/11 do not include by default.

The All-in-One Runtimes bundle installs every DirectX 9.0c redistributable plus the full range of Visual C++ runtimes in one pass, so you don't have to guess which version the client wants. Prefer manual installs? Get the DirectX End-User Runtime from Microsoft plus the Visual C++ 2010 and 2013 x86 redistributables. Install the x86 (32-bit) versions even on 64-bit Windows — the Lineage client itself is 32-bit.

If the crash happens after the intro plays rather than instantly, suspect a graphics or DPI conflict instead of a missing runtime — jump to the black screen section below.

How Do You Fix Graphical Glitches Like a Black Screen or White Boxes?

Cause: High DPI scaling on modern monitors.

Fix:

1. Right-click Lineage.exe -> Properties -> Compatibility.
2. Click "Change high DPI settings".
3. Check "Override high DPI scaling behavior" and select "Application".

Is It the Server or Your Setup? A 60-Second Diagnostic

Before you reinstall anything, find out which side the problem is on. Most wasted troubleshooting time comes from reinstalling the client when the server was simply offline.

Ping the server. Open Command Prompt and run ping [Server_IP]. Replies mean the machine is reachable; "Request timed out" means the host is down or blocking ICMP — not proof by itself, since many servers drop ping on purpose.

Test the game port. In PowerShell, run Test-NetConnection [Server_IP] -Port [port]. TcpTestSucceeded : True means the game service is up and reachable — the problem is almost certainly on your end. False means the service is down or a firewall between you and it is dropping the traffic.

Check if others are affected. Open the server's Discord. If dozens of players are posting the same error at the same time, it's the server — stop troubleshooting your PC and wait for the operator.

Try from another network. Tether to your phone's mobile data and launch again. If it connects on mobile but not on home Wi-Fi, your ISP or router is the culprit, and a VPN or a router restart usually fixes it.

Rule of thumb: if the error appeared suddenly on a client that worked yesterday and nothing on your PC changed, suspect the server first. If you just downloaded and extracted a fresh client, suspect your setup first.

Why Does the Server Hostname Fail to Resolve?

Some servers give you a domain name instead of a raw IP. If the client can't turn that name into an address, you get a connection failure that looks identical to "Login Failed."

Flush your DNS cache. Open Command Prompt as administrator and run ipconfig /flushdns. A stale cached record pointing at an old server IP is a common cause after a server migrates hosts.

Switch to a public DNS resolver. Some ISP DNS servers are slow to pick up new records or block certain domains. In your adapter settings, set your DNS to a public resolver such as Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1), then flush the cache again.

Confirm the name resolves. Run nslookup [hostname]. An IP back means DNS is fine and the problem is elsewhere; an error means the domain is expired, misconfigured, or blocked on your network.

What Should You Do When "Lineage.exe Has Stopped Working"?

Cause: Data corruption or incompatible text files (text.idx / text.dat), usually from an interrupted download or a file the antivirus quarantined mid-extraction.

Fix: Re-extract the server patch cleanly. Delete the half-extracted folder first — extracting on top of existing files leaves the corrupted ones in place. Turn off antivirus real-time protection, extract again to a fresh folder, then re-enable protection and add an exclusion. For more details on handling antivirus false positives, see our Safety & Anti-Virus Guide.

If the patch itself failed to apply: A client patch that stops partway through leaves a mismatched mix of old and new files, which crashes on launch. Symptoms are a patcher that froze, closed early, or threw a checksum error. The reliable fix is to delete the whole client folder and download the full client fresh, rather than trying to re-patch a broken install. Never patch a folder that is inside C:\Program Files — run the client from somewhere like C:\Games\Lineage so the patcher has write access without fighting Windows permissions.

Still Stuck?

Join the server's Discord and post a screenshot in their #support channel. The community is usually very helpful.

Sometimes the issue is regional routing. Check out our VPN Guide to see if a better connection path solves your login problem. You might also want to review the Essential Tools Guide for utilities that help diagnose and fix common issues.

Frequently Asked Questions

Q: The server was working yesterday but now I get "Login Failed." What happened?

The server is most likely down for maintenance or has crashed. Check the server's Discord or website for announcements. If there is no announcement, wait 30 minutes and try again — most server operators restart quickly after unplanned downtime.

Q: Do I need to disable my antivirus every time I play?

No. You only need to temporarily disable real-time protection during the initial extraction of the server files. After that, add the Lineage folder as an exception in your antivirus settings so it does not interfere with gameplay. Re-enable your antivirus immediately after extracting.

Q: Why does the game work fine on my laptop but not my desktop (or vice versa)?

This is usually a driver or compatibility issue. Make sure both machines have the same DirectX and Visual C++ runtimes installed. Also check that the desktop is not using a dedicated GPU that forces settings incompatible with the old Lineage engine — try setting the game to run on integrated graphics.

Q: Can Windows 11 run old Lineage clients?

Yes, but you may need compatibility mode. Right-click the game executable, go to Properties > Compatibility, and set it to run in Windows 7 or Windows XP SP3 mode. Also apply the high DPI fix described above.

Q: How do I check if the server itself is down versus my connection being the problem?

Ping the server IP from Command Prompt: open cmd and type ping [Server_IP]. If you get replies, your connection is fine and the issue is local. If you get "Request timed out," the server is either down or blocking ICMP. Check the server's Discord for status updates in that case.