How to Connect to a CS 1.6 LAN Server – Full Guide

Last updated: June 17, 2026

Connecting to a Counter-Strike 1.6 LAN server should be as simple as opening the LAN tab and double-clicking a result, but the auto-scan frequently fails to find local servers even when everything is set up correctly. The reliable fallback is entering the Counter-Strike 1.6 server IP manually, either through the server browser’s Favorites tab or directly with a console command.

Finding the correct cs 1.6 LAN IP address

Before anyone can connect, one PC needs to actually be hosting a game – from the main menu, choose New Game (or Create Server), pick a map, and start it. That PC is now the host, and everyone else connects to it using the steps below. If you skip this step, there’s nothing to connect to yet, regardless of how correctly you enter an IP.

Success after that depends on entering the right internal IP format. To find the host’s local IP, open Command Prompt (search cmd in the Start menu) on the host PC and type ipconfig. Look for the line labeled IPv4 Address – that’s the address other PCs on the same network will use to connect.

• Connecting on the host PC itself: use localhost:27015 or 127.0.0.1:27015
• Connecting from other PCs on the network: use the host’s internal IP, for example 192.168.1.15:27015

This internal IP only works for devices on the same local network (same router or switch). It is different from your public IP, which is only relevant if you’re trying to connect over the internet rather than a true LAN.

Method 1 – adding the server IP to Favorites

Use this method to save the manual server address for future sessions instead of retyping it every time.

1. Launch your Counter-Strike 1.6 client
2. Open Find Servers and select the Favorites tab
3. 
4. Click Add Server
5. 
6. Enter the local IP and game port (for example 192.168.1.102:27015). If the server uses a custom port, replace 27015 with that specific number.
7. Click Add this address to favorites
8. 
9. Double-click the server in your Favorites list to join
10. 

Method 2 – using the cs 1.6 connect command

The console connect command is the fastest way to bypass menus entirely, and it works even when the server isn’t showing up anywhere in the LAN or Favorites list – this is a known quirk where a server runs and accepts connections perfectly fine while remaining invisible to the auto-scan.

1. Press the tilde key (~) to open the developer console
2. Type connect [Server_IP], for example connect 192.168.1.15:27015
3. Press Enter

If this connects successfully but the server still doesn’t appear in your LAN tab, that’s expected behavior in many cases and not something to keep troubleshooting – the connection itself is what matters.

What sv_lan actually does (and what it doesn’t)

There’s a common point of confusion worth clearing up directly: sv_lan controls whether the server is restricted to local network discovery or advertises itself publicly – it does not control whether LAN clients can find or connect to it.

• sv_lan 1: restricts the server to local network only, blocking outside internet connections from reaching it
• sv_lan 0 (the default): allows both LAN and internet connections

If your LAN server isn’t showing up in the browser list, toggling sv_lan is rarely the actual fix. In most cases the server simply isn’t appearing in the auto-scan for an unrelated reason – a firewall blocking the broadcast, a router that filters local broadcast traffic, or simply an auto-scan limitation in this 25-year-old engine – while the server itself is reachable and joinable directly via the connect command the whole time.

Troubleshooting – LAN server not showing up

If you can’t see or join the LAN server, check these in order:

• Windows Firewall: the first time you launch the CS 1.6 server or client, Windows typically shows an “Allow access” popup – make sure you click Allow for both Private and Public networks. If you missed that popup or dismissed it, go to Windows Security, Firewall & network protection, Allow an app through firewall, and manually enable the CS 1.6 executable for both network types.
• Other firewall or antivirus software: third-party security software sometimes blocks game traffic even after Windows Firewall allows it – check for a separate exception if you’re running one.
• Router-level blocking: some routers, particularly ones with strict AP isolation or guest network settings, block local broadcast traffic between devices even though they’re on the same Wi-Fi. If devices are on a guest network, move them to the main network.
• Try the connect command directly: if the server doesn’t appear in any list but you have the correct internal IP, skip the browser entirely and use connect [IP]:27015 – this works independently of whether the LAN scan can see the server.

If instead you see an error specifically reading “LAN servers are restricted to local class C clients”, that message means the server thinks the connecting IP isn’t on the same local subnet as itself – it’s a more specific version of the same underlying issue, and the fixes below for matching subnets apply directly.

Playing CS 1.6 LAN-style with friends who aren’t on your network

If “LAN” really means playing with friends who aren’t physically on your Wi-Fi or Ethernet, a virtual LAN tool solves this without exposing your home network or needing router configuration. Radmin VPN is a free, widely used option built for exactly this case.

1. Install Radmin VPN on every PC that wants to join, then have the host create a network and share the name and password
2. Everyone else joins that same Radmin VPN network
3. Open Radmin VPN, go to System, Firewall Exceptions, and add hl.exe so the game’s traffic isn’t blocked by Radmin’s own firewall layer
4. If you’re on the Steam version, disable Steam Networking in Steam’s settings, since it can interfere with this kind of virtual LAN setup
5. Create the game as normal, open console, and check the IP address shown – it will look like a LAN IP (for example 26.x.x.x:27015) issued by Radmin rather than your router
6. Type sv_lan 0 in console so the server doesn’t restrict itself to a subnet Radmin’s virtual adapter doesn’t match

This effectively creates a private virtual LAN over the internet, so the rest of this guide’s connect command and Favorites methods work exactly the same way once everyone is on the Radmin network.

Ports the host needs open

If players still can’t connect after trying the steps above, the host’s firewall or router may be blocking the actual game port rather than just the discovery broadcast. CS 1.6 primarily uses UDP port 27015, though the full recommended range for HLDS-based servers is UDP 27000-27020. For a same-network LAN game, router port forwarding typically isn’t necessary – it only matters if you’re trying to let people connect from outside your local network. The Windows Firewall exception covered above is usually sufficient for true LAN play.

CS 1.6 LAN connection reference

Symptom	Likely cause	Fix
LAN tab shows no servers at all	Auto-scan failing to detect broadcast	Use Favorites or the connect command with the host’s IP directly
Connect command times out	Firewall blocking the actual connection	Allow the CS 1.6 executable through Windows Firewall
Server works but isn’t visible in any list	Normal auto-scan limitation, not a real problem	Just use connect [IP]:27015 – no fix needed
Some PCs connect, others can’t on same network	Guest network or AP isolation	Move all devices to the same main network
Toggling sv_lan didn’t fix visibility	sv_lan controls public vs LAN-only advertising, not discovery	Leave at default (0) and troubleshoot firewall instead

For the best local network experience, make sure every PC is running a clean, matching game build. Download Counter-Strike 1.6 from our homepage.