CS 1.6 connection timeout: find which part fails
A timeout means the connection did not complete within the allowed time. It does not identify the cause by itself. Start with one reproducible attempt and the exact console message, then follow the branch that matches your result.
In the game console, enter the command below using the address shown by your chosen server.
connect IP:PORT1. Confirm that this is a connection problem
Use the same client throughout the comparison. Changing the client and the network together would make the result difficult to interpret.
- Record the real host:port, time of the attempt and complete error message.
- Create a local game on an included map. If that also fails to load, investigate the game installation first.
- Distinguish timeout from a password prompt, full-server response, ban or incompatible-client message. Those responses need their own resolution.
2. Test one server against another
Another successful connection narrows the problem, but does not prove that the first server is down for everyone.
- Only one server fails: copy its current address again, including the port. Ask its owner whether it is online and whether your client is supported.
- Several known working servers fail: continue with the connection and application checks below.
- Direct connection works but the browser list stalls: investigate the browser refresh separately. Steam documents routers struggling with many simultaneous server replies.
3. Compare the network path
If the other network works, focus on the original router, provider or network rules. On a managed network, ask its administrator to investigate rather than bypassing its controls.
- Restart the game and Steam, where applicable, and check whether the internet connection itself works.
- If practical, compare Wi-Fi with a wired connection to your router. Restart your own router normally; do not factory-reset it.
- Try the same server from another trusted network when available, keeping the client unchanged.
4. Check permissions and retain the evidence
Keep the firewall enabled. Review permissions for the trusted game executable and Steam, where applicable; verify the actual file path before changing a rule. Do not open broad port ranges as a generic fix.
Retest after one change. If the timeout remains, share the address, exact message and your local-map, second-server and alternate-network results with the server owner or network support.
Sources and further reading
Choose your next step
Compare one failing destination with a working one
Start a local map, then try another known server. If only one destination times out, verify its address and availability before changing your client. If multiple destinations fail, compare another network where possible and review application-specific firewall permissions. Keep the exact error and test conditions so each change has a measurable result.
Questions before you play
Should I turn off my firewall to fix a timeout?
Avoid disabling protection globally. Check the game's specific permission and compare the failing connection with another server or network to locate the actual problem.