{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by adresd:
9/11/2014 4:05:00 PM
2
StrictNAT - Getting really annoying now (PS4)
OK, so have in the past, setup my router to allow PSN etc.
Party chat and everything else works ok.
PS4 Shows a NAT type of 2 in network info.
Had to setup for other games including BF4, COD, WARFRAME etc to get rid of strict NAT, warnings because of the way my router handles UDP, they all work fine now.. TCP seems fine.
So have added the UDP ports and ranges, as given on the network issues page ( http://www.bungie.net/en/Help/Article/11875 ):
UDP 35000-35099 (In and Out)
UDP 3074 (In and Out)
Router allows all TCP outbound by default, so the TCP ports mentioned are covered.
Yet still I get a STRICT NAT warning in destiny.
Can anyone shed any light on what other ports BUNGIE might be using? or how they actually check for Strict NAT?
-
1 ReplyDestiny gives the message as long as it detects a Type 2 or 3 NAT. So, Type 1 it is...for that you have to connect the PS4 directly to the modem or use the DMZ-feature (if your router supports that).
-
4 RepliesI have the same issue as you OP, I don't have a solution or any answers :(. Someone else who plays Destiny using the same router/internet as me, on a different PS4, [b]doesn't[/b] get the strict NAT type warning. ???
