Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Router
Make sure your router forwards (all) traffic to your PC. This is different for each router. Some routers call it a DMZ but mean "exposed host". My router has an option in network / NAT settings to specify a LAN IP to be used as server. This should match the LAN IP of the PC. You can find it in the properties of the internet connection (Tray icon in the Windows task bar). Or type "cmd" in the start menu, start the command prompt, and then type "ipconfig". In both cases it'll be the IPv4 address.
This is a sure-fire way. It may be enough to just forward port 27015 (UDP).
Firewall
Additionally make sure that the server software has full network access. I guess when using the default firewall which comes with Windows, there's a prompt when the server is started the first time. In case of a "listen server" (starting TFC and using the main menu to create a server), you may have to check the firewall settings in the Windows control panel. I'm using my AV's firewall though, which has application rules in the firewall options. I set it to "allow all connections" for the server ("hlds.exe", or "hl.exe" in case of a listen server).
Again, this is the sure-fire way. You could fine tune which kind of traffic should be allowed, e.g. incoming: port 27015 (local server), 26900-26901 (comm. with Steam servers) , outgoing: all ports.
Three different ways to start a server
- Through the TFC main menu. In this case, a game is started and you're hosting it.
- Using the "Half-Life Dedicated Server" (HLDS) in the tools section of the Steam library.
- Using Valve's command line Steam client to retrieve the HLDS: https://developer.valvesoftware.com/wiki/SteamCMD
For some reason a running HLDS is only then visible for other players (internet tab in Steam's server browser) if console mode is used. This requires a parameter, however the launch options in Steam's library aren't passed on to the server. So it has to be started in a different way, either as shortcut to the executable ("hlds.exe"), or using a batch file. The minimum parameters are:-console -game tfc +map 2fort
The Linux version of the HLDS doesn't have a GUI and thus is always in console mode.
Don't know a lot of companies. In America there's for example
NFO - https://www.nfoservers.com/order.php
GameServers - https://www.gameservers.com/game_servers/tfc-half_life_team_fortress.php
Picked those because they have ready-to-go servers. But you could also rent a VPS e.g. at OVH and install SteamCMD there.
There are 7 TFC servers which get more or less traffic, that's about it.
Top 8 from this list of manually added servers, minus the 24hr 2fort server (it's usually just bots).
https://www.gametracker.com/search/tfc/