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
not if you connect your computer directly to a modem with no router.
if that is not an option you need to learn to poke holes in the router or let somebody else host.
or rent a server.
If you want to know it for specific games, you should ask in discussion hub of the game.
ARMA 3 still requires port forwarding.
http://steamcommunity.com/app/107410/discussions/1/648817378050000286/
Take on Mars does not require port forwarding anymore:
https://steamcommunity.com/app/244030/discussions/0/35219681538879478/#c616189742776164684
But if games need you to create a "server", its required that it can receive unrequested ingoing traffic, aka joining.
Best is to ask for the game in question which ports need to listen.
That is quite relieving.
With games which do not require portforwarding, does the player simply create the new match and it works just like that? Or are there other processes?
Each computer on your internal network is given a non-public IP address, and the NAT device does the job of letting all those devices use a single public IP address. When you connect outwards to a server on the public internet, the NAT device makes an association between the port that was used to initiate the request on your machine, with a port on the NAT's public-facing interface.
For the sake of argument, say that you're trying to the Google homepage, http://google.com.
Your computer picks a random port to send the request from, say, 34567, and it directs it to port 80 (the HTTP port) of google.com. The NAT device picks this up, and sends out the request on its public port, say, 45678. google.com gets your request, and sends back the page, to the public IP address, and port 45678. The NAT device remembers that it sent out data that came from your computer's port 34567 out on port 45678, so it sends replies to 45678 to your computer's port 34567. So you can see http://google.com
Now if you're hosting a service on a port, for example, port 2302 on your computer, if the NAT device gets an incoming signal on port 2302, it won't know which computer to send it to. That's why you need to set up port forwarding; to set up the mappings between the external public ports of the NAT device and the internal private ports of your computer.
The ultimate fix for this sort of nonsense is the roll-out of IPv6, which has IP addresses available in abundance, so every computer on your own home network will be able to have a real publicly routable IP address, so no port forwarding nonsense will be required.