WarzoneCS WarzoneCS
Menu
English
Boost Your Server

CS 1.6 LAN Party Guide — Host, Connect, Play

Complete guide to running a CS 1.6 LAN party — host setup, sv_lan config, connecting via LAN IP, filling teams with bots, common firewall fixes.

Updated: 2026-07-30

LAN parties are how a lot of us first played CS 1.6, and they're still the best way to introduce someone new. No accounts, no cheaters, no lag, just a bunch of friends in one room with a switch and some cheap laptops. This guide covers everything from host setup to filling empty slots with bots.

What you need

  • A LAN switch or WiFi router — any consumer router with 4+ Ethernet ports works. WiFi is fine for 2-6 players; wired is better for 8+.
  • 1 host machine — runs the CS 1.6 server. Any Windows 7/8/10/11 laptop with 4 GB RAM is enough.
  • N client machines — one per player. Same install works for host and clients.
  • CS 1.6 installed on every machine — the WarzoneCS installer is the easiest path.
  • All machines on the same subnet — plug them into the same router / switch. Same WiFi SSID. If Windows says "Public network," change it to Private on each machine.

Fastest setup — listen server (host also plays)

The host launches CS 1.6, hits "Create Server," and other people join their listen server via the host's LAN IP.

Host steps

  1. Launch CS 1.6 on the host machine.
  2. Main menu → New Game.
  3. Server name: whatever. "Alex's LAN," "Rec Room," anything.
  4. Password: leave blank unless the party is huge and you don't want randoms.
  5. Map: de_dust2 for the first round is a safe classic.
  6. Game mode: Classic (bomb defusal). CSDM/deathmatch requires a plugin.
  7. Max players: match your party size. Set to actual count + 2 for bots to fill.
  8. Click Start.

The host lands in the map immediately, playing as any team they pick.

Find the host's LAN IP

On the host machine:

  • Windows 10/11: Win+R → cmd → ipconfig → look for "IPv4 Address" under the active adapter. Usually 192.168.x.y or 10.x.y.z.
  • Faster method: Win+R → cmd → type ipconfig | findstr IPv4

Write down that IP. Every client will connect to it.

Client steps

Each client machine:

  1. Launch CS 1.6
  2. Main menu → Find Servers → LAN tab
  3. The host's server should appear in the list (name matches what the host set)
  4. Double-click to join

If the LAN tab is empty (common on some Windows configurations), fall back to direct connect:

  1. Open console (~)
  2. Type: connect 192.168.x.y:27015 (replace with the host's actual IP)
  3. Press Enter

Direct connect works even when broadcast discovery is blocked.

Alternative — dedicated server on the host

If the host has enough hardware and doesn't want to play, run hlds.exe (dedicated server) instead of a listen server. Runs headless in a console window, doesn't consume the host's game.

The WarzoneCS installer ships hlds.exe alongside hl.exe. Launch it with:

hlds.exe -console -game cstrike +sv_lan 1 +maxplayers 12 +map de_dust2

Server console appears. Clients connect the same way as to a listen server.

Con: dedicated servers have no interactive host, so team-balance decisions need someone with rcon access. Only worth it if the host machine really can't afford the extra CPU load of running the game AND the server.

sv_lan — the one setting that matters

Server-side setting that tells the server "you're LAN-only, don't try to reach the master server":

sv_lan 1

The listen-server dialog does this automatically. If you're setting up a dedicated server manually, include +sv_lan 1 in launch args or sv_lan 1 in server.cfg.

What sv_lan 1 changes:

  • Server doesn't ping cs.warzonecs.com master server
  • Server doesn't appear in the Internet tab, only the LAN tab
  • Server accepts connections from 192.168.*.*, 10.*.*.*, 172.16-31.*.* only

Filling empty slots with bots

Host or dedicated server console:

bot_quota 10
bot_quota_mode fill
bot_difficulty 1
bot_join_team any

Bots fill up to 10 total players, split between humans and bots. As humans join or leave, bot count auto-adjusts.

Full breakdown: CS 1.6 bots guide.

Firewall — the #1 cause of "LAN not working"

Symptom: host launches server, host can see own server in browser, no client can see or connect.

Cause: Windows Firewall on the host is blocking incoming UDP on port 27015.

Fix on the host machine:

  1. Win+R → wf.msc (Windows Firewall with Advanced Security)
  2. Inbound Rules → New Rule
  3. Port → UDP → Specific local ports: 27015
  4. Allow the connection
  5. Apply to Private + Domain (not Public, unless you know what you're doing)
  6. Name it "CS 1.6 LAN" for clarity

Alternatively, launch CS 1.6 as administrator once — Windows pops a firewall prompt, and clicking "Allow access" adds an exemption automatically.

On the client machine: usually no firewall changes needed for outbound. If clients still can't connect, temporarily disable third-party antivirus (Kaspersky, McAfee, etc.) which have their own firewalls.

Router setup — LAN vs guest network

Some consumer routers isolate "guest WiFi" from the main network. If half your clients are on the main SSID and half on the guest SSID, they can't see each other's traffic.

Fix: connect everyone to the same SSID. If your router has a "guest network isolation" toggle, disable it.

For Ethernet: all cables into the same switch (or same router LAN ports). No VLANs.

Match-day tips

Round timer: default 1:45 for classic. Feels short for LAN — a lot of people prefer 2:15 or 2:30. Set on the server console:

mp_roundtime 2.15

Freeze time: default 6 seconds. Cut to 3 for faster matches:

mp_freezetime 3

Team switching: rcon-only by default. Have the host bind a rcon shortcut:

bind "F9" "rcon changeteam CT"
bind "F10" "rcon changeteam T"

Rcon password: set on the host BEFORE clients connect (once someone's in without rcon, they can't rcon-elevate):

rcon_password "lanparty"

Then clients need to rcon_password "lanparty" in their console to use rcon commands.

Deathmatch warmup: for the first 5 minutes before the "real" round, run DM to loosen everyone up. Requires a CSDM plugin — install with AMX Mod X, or just play a warmup round of classic on cs_office.

Backup snacks and drinks: LAN parties last 4-8 hours. Have caffeine.

Common LAN party problems

"Server browser LAN tab is empty on every client." Firewall on host, guest isolation on router, or all-clients-on-WiFi + host-on-Ethernet with a router that doesn't bridge the two. Try direct-connect via connect 192.168.x.y:27015.

"Connection failed after 4 retries." Wrong IP, wrong port, or firewall. Verify host IP with ipconfig, verify port is 27015 (default), open the firewall rule.

"Everyone shows 'BOT' as their team." bot_quota_mode fill needs at least one human on each team before joining bots. Have both team humans join before running the bot commands.

"Rounds end but nothing happens between them." mp_roundtime is at default 0 (infinite). Set to 1.75 or higher.

"CS 1.6 launches but can't hear voice chat." GoldSrc voice needs voice_enable 1 (default) and a working microphone driver. Test in Windows sound settings first.

"Someone joined the wrong team and can't switch." rcon needed. If nobody has rcon set up, restart the server.

"The host laptop gets hot and starts stuttering." Old laptops running CS 1.6 hit 100% GPU + CPU. Plug into wall power (don't run on battery), elevate laptop for airflow, close Chrome tabs, cap fps_max 100 on the host.

What next?