{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by vanHooijdonk:
2/4/2015 10:18:08 AM
2
UPNP and Destiny and MarionBerry errors
So I have figured out at least one of the reasons for the MarionBerry error.
When destiny connects to the destiny servers when you start te game it tries to open up port 1200 UDP on the router through UPNP. When this port is already opened up by destiny earlier ( previous gaming session) this will fail. And will result in a MarionBerry error. When you log in to your router and remove this UPD 1200 port forward (Demonware??) to your XBOXONE and reconnect from within the game, you are able to connect.
To me this seems a solvable issue from within the Destiny game. Either remove the exiting port forward upon starting the game, or not try and create it when the port forward is already in place.
I have a CISCO RV320 router, XboxOne and 100MBit Fiber internet connection.
Due to this single issue, I am forced to disable UPNP on my router. With Nat Type 2 and all other issues that come with this.
-
They don't want you to level up too fast.
-
It seems I have a similar issue on the #PS4 as well. I have only been able to login by disabling UPNP on my router (Buffalo WSR-1166DHP firmware rev 1.04) and adding the console's IP to the DMZ. But by disabling UPNP, I lose XBOX Live access on my Xbox360 and have to add the Xbox 360's IP to the DMZ to get it to work. Then if I switch back to the PS4, I also have to switch the DMZ again in order to sign in. I don't seem to have any online problems with other PS4 games. Only Destiny seems to cause me frustrations.
