{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/13/2017 12:00:21 PM
6
Hi,
same issue for me, with a technicolor modem. (not only technicolor modems affected, seems much more, like your's (thomson) which has a special/affected firmware and/or port settings)
I read several fixes today, not sure if one of them is solving it ...
you can try "manually port forwarding" like:
1. Go to your routers webinterface (10.0.0.138) for mine.
2. Home Network --> select your PS4 (select the LAN mac address of your PS4)
3. Assign a game or application to a local network device (bottom of the screen)
Create new game or application and give it a Name "Destiny2" for example.
4. Protocol: UDP | Port Range: 3078 to 3079 | Translate to: (let it empty) | Trigger protocol: UDP | Trigger Port: 3078
16. Protocol: TCP| Port Range: 3478 to 3480| Translate to: (let it empty) | Trigger protocol: TCP | Trigger Port: 3478
17. Protocol: TCP| Port Range: 1935 to 1935 | Translate to: (let it empty) | Trigger protocol: TCP | Trigger Port: 1935
18. Protocol: UDP | Port Range: 3074 to 3074 | Translate to: (let it empty) | Trigger protocol: UDP | Trigger Port: 3074
______________
bungie shared already following information/steps for possible solution:
https://www.bungie.net/en/Help/Article/46243
br
Tommy
English
-
Hi, tried that but still have cabbage.
-
Same ^
-
same for me .. seems this workaround or port openings are not working (or only for few) ... to be honest, it is not worth for me, to change router/modem because ONLY d2 is affected. playing via mobile-phone hotspot is fine for me (also with nat-type1) story mode i play alone .. and yesterday i was able to find players for strikes .. just not your friends :D
-
it cant be a solution. I also complated campain with 4g hotspot but it takes at least 1-2GB data for day.. why we are paying more because of bungie's fault? they should fix this, my ISP does not accept "destiny 2 is not working" as a reason for changing modem.
-
Hi Quiard! I found a solution - which is working fine for me now (Technocolor Modem Tgv88xx) you just need to open specific ports ... and CONE needs to be off on all those ports which you've to set: 1.Go to your routers webinterface (10.0.0.138) for mine. 2.Go to "Games & Applications" 3.Create "new game or application" and give it a Name "Destiny2" for example. 4. Add following Port ranges Protocol: UDP | Port Range: 3078 to 3079 | Translate to: (let it empty) | Trigger protocol: UDP | Trigger Port: 3078 Protocol: TCP| Port Range: 3478 to 3480| Translate to: (let it empty) | Trigger protocol: TCP | Trigger Port: 3478 Protocol: TCP| Port Range: 1935 to 1935 | Translate to: (let it empty) | Trigger protocol: TCP | Trigger Port: 1935 Protocol: UDP | Port Range: 3074 to 3074 | Translate to: (let it empty) | Trigger protocol: UDP | Trigger Port: 3074 5. Assign the created Game/Application to the IP address of your PS4 I'm quite sure this will fix it. Leave all other settings as you had before - i guess you have no problem with other games ... _____________________ let me know the outcome or get back to me in case of any questions!
-
@MrNiceGuy Thanks, but I tried this config 2 days ago.. Even it is still applied. I'm still getting cabbage error and I couldn't finish any strikes or last more than 20 min. this game experience is total disaster for me and I feel roobed, because I'm not sure if I'll be able to get a refund.
