JavaScript is required to use Bungie.net

Destiny 2

Discuss all things Destiny 2.
Edited by Jebus: 8/7/2019 5:37:42 AM
2

How to force solo play in matchmade activities (EAZ, strikes, etc.) on PC

After taking a little bit of time experimenting with port forwarding, I believe I personally found a way to keep yourself from being matchmade with others in Destiny 2 on PC. After the thought of grinding 200 more miniboss kills on my 2 alternate characters, I wanted to find a way to guarantee solo play on PC like how there is on PS4, just by simply changing the PS4's system clock. So far, [i]I cannot absolutely guarantee this process will work just yet[/i], but at this time it has worked three times for me without fail, and for another as well. [b]Below are the steps I took. Just make sure Destiny 2 is closed, first of all.[/b] [b]1.[/b] Go to the taskbar search bar (or hold WinKey + R for Run prompt) and type [b]wf.msc[/b] into the textbox. This will open Windows Firewall. [b]2.[/b] Left-click and then right-click on [i]Inbound Rules[/i] to the left of the Windows Firewall window, and click [i]New Rule[/i]. [b]3.[/b] Select [i]Port[/i], click [i]Next[/i], make sure [i]TCP[/i] is selected, click [i]Specific Local Ports[/i], type [b]1935, 3097, 3478-3480[/b] and click [i]Next[/i]. [b]4.[/b] Select [i]Block the connection[/i] and click [i]Next[/i]. To keep things simple, make sure [i]Domain[/i], [i]Private[/i], and [i]Public[/i] are checked and click [i]Next[/i]. [b]5.[/b] On this page, you can name this rule to whatever you want, but I named this rule [b]D2 solo TCP inbound[/b] to make it easy. [b]•[/b] Repeat the steps 2-5 above, [i][b]except[/b][/i] for the first part of step 3. Instead, click [i]UDP[/i]. The name in step 5 should also reflect this. [b]The steps for Outbound rules are almost the same:[/b] [b]1.[/b] Left-click and then right-click on [i]Outbound Rules[/i] to the left of the Windows Firewall window, and click [i]New Rule[/i]. [b]2.[/b] Select [i]Port[/i], click [i]Next[/i], make sure [i]TCP[/i] is selected, click [i]Specific Local Ports[/i], type [b]1935, 3097, 3478-3480[/b] and click [i]Next[/i]. [b]3.[/b] Select [i]Block the connection[/i] and click [i]Next[/i]. To keep things simple, make sure [i]Domain[/i], [i]Private[/i], and [i]Public[/i] are checked and click [i]Next[/i]. [b]4.[/b] On this page, you can name this rule to whatever you want, but I named this rule [b]D2 solo TCP outbound[/b] to make it easy. [b]•[/b] Repeat the steps 1-4 above, [i][b]except[/b][/i] for the first part of step 2. Instead, click [i]UDP[/i]. The name in step 4 should also reflect this. [u][i][b]When you are finished with anything you need to do solo and wish to be matchmade with others, just be sure to remember to either delete all four of these rules, OR by allowing all four of the connection ports in Windows Firewall by right-clicking on the rules you created, click 'Properties', make sure the 'General' tab is open, click 'Allow the connection', and then click 'OK'.[/b][/i][/u] [b]•[/b] Finally, when you're finished with the above steps, open the Destiny 2 tab on Battle.net, select [i]Asia[/i] as the Region and launch Destiny 2 and select any activity you wish to solo in. Sorry Xbox players, so far there's no way to force solo on your platform, although you could replicate the same process by tethering your console to your PC and bridging the connection. If this isn't possible, you could temporarily disable UPnP and disabling connections to ports [b]1935, 3097, 3478-3480[/b] on your router and it [i]may[/i] work depending on how intuitive your router's port forwarding settings are. Cheers.
English
#destiny2

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon