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
It's an issue with NAT translation. Basically, you've got 2 Arma clients on the same networking routing through the same public IP address. So even though they have 2 separate private IP's, 192.168.0.2 and 192.168.0.3, they're both using 2302, 2304, 2305 as the standard ports...even as outgoing. Most normal programs will generate a dynamic source port, Arma doesn't appear to do that. So when NAT tries to translate your outgoing connections, you're NAT firewall (192.168.0.1 and some public IP) can only support 1 or the other because (to overly simplify things), when you initiate an outgoing connection through a NAT router, it does this:
Private IP - 192.168.0.2
Private Port - 2502
Protocol: UDP
Public IP - 1.1.1.1 (or whatever public ip you're assigned)
Public Port - 2502
Protocol: UDP
And then it forwards your packet to the server. When the server replies, it'll reply to 1.1.1.1 on UDP port 2502. So if you have 2 computers that are trying to use that same IP and Port through the same NAT firewall, the packets will either get routed to one computer or the other computer...possibly both depending on your firewall. Depending on your NAT configuration and/or what router you're using, it could be more or less restrictive.
To get around this, modify your ArmA2 shortcuts and add " -port=2350" to one of the computers. The number doesn't really matter, just as long as it's different from the other computers which will use 2302, 2304, 2305 by default. This will change the client port (though it's not documented) and allow you to connect to Internet servers. Well, at least it should ;-)
Also, another strange thing is that it won't actually use the port you specify, in this case 2350, it'll use +2, +3 of that. So you could technically specify -port=2304 and it'll end up using 2306, 2307. If you specify -port=2303, it'll conflict on port 2305 so don't do that. Skip at least 3 for every computer.
You can always check open ports by opening up a command prompt, typing "netstat -an" and hitting enter. It'll list all of the open TCP and UDP ports. This being ArmA, you're interested in UDP. Dont pay attention to the endpoint column though...it's UDP which is "connection-less" so there isn't any maintained connection. The packets just kind of get there...or they don't and ArmA compensates (or tries to) appropriately.
Let me know if this worked for you.