Port Forwarding Issues

[Echo Congo]

So I been trying to fixing my port forwarding issues for months now because I would like to be able to host my own server for my friends. I went into my router settings and opened the following ports: UDP: 2302-2305. I'm not sure if those are the right ports or if I'm missing any from that. I do want to also mention that the internet service I have is AT&T. If someone could help me out with this, that would be much appreciated. I just want to be able to host my own server lol.
https://gyazo.com/f034d03d1e68eeff2d67d79ef5ae1241

[Snofur]

I've had this issue recently and I've been experimenting abit, asfar as I know you only need to allow 2302-2306 UDP through your router and it should show up instantly in the server browser in
the ArmA 3 Launcher. Windows Firewall should not be needing any port fowarding, but in my case I went through every ArmA 3 rule and went into the Advanced tab and made sure Edge Traversal were set to Allow Edge Traversal, not sure why some are disabled but if the router port fowarding dosen't work try enabling Edge Traversal for all Windows Firewall ArmA 3 exceptions.

I have a UPNP Enabled Router, but that dosen't help, for some reason it does not allow the whole 2302-2306 range, so I manually set ports 2302 to 2306 UDP as an exception. I'm not sure what your host port means, but I assume it's your PC's own IP, I had to enter the ports twice into two boxes then assign my PC's IP adress to make it register, annoying but it worked.

Reason this is a fact, atleast for me is because asoon as I removed the port fowarding while having everything set up my server dissapeared from the face of the earth, asoon as I put them back up the server showed up, I also found some link on a forum that lets you ping Steam and see if Steam can actually detect the server, which it did with or without port fowarding, so I don't think it's entirely Steam's fault if it dosen't show up.


Hope this helped, if not I don't really have anything else.


Here's a page for port fowarding as refference. I only port fowarded the 2302-2306 range.
https://community.bistudio.com/wiki/Arma_3_Dedicated_Server#Port_Forwarding

[Echo Congo]

I appreciate man, I’ll try doing that whenever I get the chance. I know my response is far overdue lol, just been pretty busy with life lmao.

Originally posted by Snofur:

I've had this issue recently and I've been experimenting abit, asfar as I know you only need to allow 2302-2306 UDP through your router and it should show up instantly in the server browser in
the ArmA 3 Launcher. Windows Firewall should not be needing any port fowarding, but in my case I went through every ArmA 3 rule and went into the Advanced tab and made sure Edge Traversal were set to Allow Edge Traversal, not sure why some are disabled but if the router port fowarding dosen't work try enabling Edge Traversal for all Windows Firewall ArmA 3 exceptions.

I have a UPNP Enabled Router, but that dosen't help, for some reason it does not allow the whole 2302-2306 range, so I manually set ports 2302 to 2306 UDP as an exception. I'm not sure what your host port means, but I assume it's your PC's own IP, I had to enter the ports twice into two boxes then assign my PC's IP adress to make it register, annoying but it worked.

Reason this is a fact, atleast for me is because asoon as I removed the port fowarding while having everything set up my server dissapeared from the face of the earth, asoon as I put them back up the server showed up, I also found some link on a forum that lets you ping Steam and see if Steam can actually detect the server, which it did with or without port fowarding, so I don't think it's entirely Steam's fault if it dosen't show up.


Hope this helped, if not I don't really have anything else.


Here's a page for port fowarding as refference. I only port fowarded the 2302-2306 range.
https://community.bistudio.com/wiki/Arma_3_Dedicated_Server#Port_Forwarding