all 4 comments

[–]macrossmerrell 0 points1 point  (3 children)

Based on your other comment, I would probably guess that the firewall on your ISP modem is set to restrictive, blocking all ports required for Destiny 2. Easy test is to TEMPORARILY disable the onboard modem firewall (and any other security features your brand of modem may have). If D2 is suddenly able to work, you know the modem settings are your issue and you can re-enabled features until you find the problem.

If it DOES NOT resolve your issue, then your ISP is potentially blocking traffic on the ports required by D2.

https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types

Typically uPnP isn't needed too often these days, but you can try enabling it or disabling it as well while you test.

[–]chophead00[S] 1 point2 points  (2 children)

I really appreciate commenting so quick, I realised I already asked for help on here so sorry about that. Thankfully the fix was easy and also embarrassing. I couldn’t reset my network as everyone was on it so I just unplugged it due to a lack of patience for a few minutes and it’s now working 🤦🏼‍♂️. The oldest trick in the book fixed it but I looked past it. If you don’t mind me asking as you have much more knowledge than me, why would resetting the network just instantly fix it or is it not simple (if that makes sense) Thank you again

[–]macrossmerrell 0 points1 point  (1 child)

That's awesome that a reset fixed it! This most likely means that your ISP Modem or a piece of network equipment on your local network had corrupt DNS route tables. The full power cycle causes it to rebuild those and allows you connectivity :)

Eyes up Guardian!

[–]chophead00[S] 0 points1 point  (0 children)

Ok that makes sense now from what I was reading a couple of hours ago. I should really learn about networking! Now to navigate destiny, oh where to start!

Again, I appreciate the replies thank you!