{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
2/15/2021 2:22:04 AM
3
So the original problem of people crashing into activities was hotfixed since it seemed to be a network issue, I was wondering if using a firewall to block traffic from the ports destiny 2 requires to be open and after blocking then (inbound and outbound), no more crashing into jetsam and archers line. So it seems to be a problem with connecting to other people.
With the firewall blocks the game is perfectly fine, biggest problem is that as is it blocks traffic so no fireteams (basically a solo game).
English
-
Thank you! CAN CONFIRM that this temporarily fixes the issue. Like stated though, you won't be able to connect to other players when you enter the area. It was fine for me because I just needed to complete a lost sector in Jetsam of Saturn in order to progress the quest in the Forsaken. I just changed the settings back after I completed it. For clarity, this is what I did: go to Control Panel>System and Security>Windows Defender Firewall>Advanced settings. First is to change inbound settings. Inbound settings>right click Destiny 2 (there will be two; do the same for both)>properties>General>Block connection. Do the same for both Destiny 2 entries (one is UDP and other is TCP). Next, Inbound settings>New rule>Select port>Select TCP>Select specific port>type in 27000-27200, 3097>Select block connection>Check all boxes>Name it whatever you want. Next, repeat those steps, but select UDP instead of TCP. Now to do the same for Outbound connection. Select outbound connection>new rule>port>TCP>select specific port, type in 27000-27200, 3097>select block connection>check all boxes>name whatever. Now again, repeat steps, but select UDP instead of TCP. This should set the correct rules to block the connection for D2. After you've completed what you need to in Jetsam, go back and right click on the rules that you created (will be listed as whatever you named it) and delete. Then go back to inbound settings and right click Destiny 2>properties>change back to allow connection. This is what I did and I was able to get to the area to complete my quest.
-
Thanks for this detailed post. I tested it out today and didn't crash with these firewall settings enabled. This does help explain why I seemed to crash at different times/in different spots after entering Jetsam - it depends on the location of other players in the area!
