{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/24/2015 7:00:16 PM
3
NAT Type 2 Error after Hotfix
Heyo out there.
First of all, great work with that hotfix. #sarcasm
My friends and I all can't play together anymore because all of us suddenly get NAT errors. We didn't have them before this hotfix. We played several missions and strikes together, then the hotfix came in, we relogged, downloaded and updated the game and BAMM! Error. We login, try to join the fireteam but NOPE. NAT Type 2 error. I have always been on NAT 2 and never ever had a problem with that (as it is the standard router configuration). I already tried to forward all the destiny ports to my PS4 using a static IP but still nothing. The tower is almost empty which is a strong indicator that something is wrong with the connection. I also restarted the game, my PS4 and also my router several times. Any help? Any suggestions?
It's quite frustrating...
Cheers,
Aeon
-
2016: NAT TYPE 2 DETECTED...FORWARDING TO SYSTEM NAT DIRECTIVE 3... PREPARE FOR DISCONNECT...DISCONNECTED...
-
Right when you join the party talk into the mic had this issue last week
-
Edited by kuro41: 10/25/2015 12:52:11 AMHaving the same issue. Last time I checked most things WANT NAT type 2, party chat for example. I'm using a setup that goes Verizon modem/router--Cat6-->Linksys router--Cat6--->PS4. It seems setting up a static IP then forwarding the PS4 ports helped. (on the Verison, forwarded to the Linksys. On Linksys forwarded to PS4) Forwarding the ports for PS4 also bumped my up/down speeds there.
