Season of Worthy

[PCDesmond]

It looks like Destiny has found a way around this, any chance you could update it for the latest season?

Thanks so much.

[Dealman]

I've been getting messages about this on Reddit, will try and look into it today! One user reported that blocking some of the ports that Steam uses worked.

[Dealman]

@PCDesmond Would you be so kind to try and add 20814 as an additional port to block? You can do this under the settings tab. So it should look like this;

1935,3097-3098,3478-3480,20814

I'm afraid this port might be different for everyone, hopefully not. You'll have to remove and re-apply the custom rules for it to update.

[PCDesmond]

@Dealman I just tried, and got placed into a group. I saw the post on Reddit after I posted here. I tried adding a lot of the ports on the list here, but still am getting placed into other people:

https://www.bungie.net/en/Help/Troubleshoot?oid=13610#PortForwarding

Thanks for looking into it, my wife and I love using your program for solo farming!

PS, I also found this thread on Reddit, don't know if can help you or not:

https://www.reddit.com/r/DestinyTheGame/comments/fh35e1/how_to_play_solo_strikesyour_own_instance_guide/?sort=new

[Dealman]

@PCDesmond Thanks, then it's probably like I suspected. That port works for me. Not sure how or if I could automate this process.

I found this port via using Windows Resource Manager, you can open it via pressing the windows key and entering resmon.

If you'd like to try it yourself, go to the Network tab and select destiny2.exe, it may be a bit tricky to check as it jumps around a bit.

Once you have that selected, expand the Listening Ports tab and look at the values there. Should be a bunch of 5XXXX and maybe a few 6XXXX ports. Is there a 20XXX port listed there as well?

If yes, try blocking that one via my program.

Also I noticed I had duplicate Destiny 2 ports now for some reason, so try double-checking that the default ports are not enabled even though my program reports them as disabled. If you wanna check it manually you can click the button under the Settings tab and it'll open the policy settings window for you.

Otherwise just click the default ports button twice and it should do it automatically.

[PCDesmond]

@Dealman I tried, I had a 28XXX port, but adding it to your app didn't work. I did try the new powershell script linked in my previous post, and it worked. I don't know much about networking, but it looks like the local port versus remote port might be the thing.

I appreciate you looking into everything, and your program has been a real help.

Thanks.

[Dealman]

@PCDesmond And you re-added the custom rules so it updated, right? Did you add it to both the UDP and TCP text fields?

Blocking 27000-27100 remote ports also seems to work, however when I only block 20814 it loads a lot faster and I don't get the Steam server error message.

Will be uploading a new version of the program later today. Also fixed some other random bugs. Thanks for helping me test :)

[Dealman]

I've pushed some changes and uploaded a new version taking the above findings into consideration. It seems like it still works, just a lot more painful now.

Will leave this issue open for a while in case someone figures something out.

[JamIsJam88]

Hey does this still work for anyone? It has worked for me once or twice and then stops working after.

[Supernalboot]

blocking outbound ports 27000-27100 works 100% in the season of arrival. I've not tested it using the software but doing it manually works fine.

[danlavelle]

Not sure if you're still maintaining this, but I tried the 'trick' of adding the 27000-27100 block to both TCP and UDP and was unable to get this tool to work. Unsure if it's due to Beyond Light changing things and Bungie's networking differening.

[Dealman]

Not sure if you're still maintaining this, but I tried the 'trick' of adding the 27000-27100 block to both TCP and UDP and was unable to get this tool to work. Unsure if it's due to Beyond Light changing things and Bungie's networking differening.

Oof, that's unfortunate... It's very possible they've changed something, it's a pretty large expansion. If we decide to check Destiny 2 out again I'll take a look, but I can't really promise anything :(

There's some programs out there that can help you see what ports a process is using, they're a bit finicky but might help you find the ports you need to block. :)