Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
god i wish that was me
also try the app for making a fireteam
1) Do you have any sort of anti-malware or intrusion-detection system set up on your PC?
2) Is anyone else on your network also playing Destiny 2?
3) Have you updated your router's firmware recently?
- The first point is because the game requires certain ports to be accessible for a connection to the D2 servers. Bungie's support article about networking specifies that PC players should have these TCP and UDP ports open in your router's network settings (or open/available on your PC) in order to play properly, and some security software can block access to these ports even if they are open/available at the router level:
TCP: 80, 443, 1119-1120, 3074, 3724, 4000, 6112-6114, 7500-7509, 30000-30009
UDP: 80, 443, 1119-1120, 3074, 3097-3196, 3724, 4000, 6112-6114, 27015-27200
- The second point is because in order for multiple people on the same network to be able to play Destiny 2 at the same time you have to have UPnP enabled in your router. Check this article about networking from Bungie and the UPnP section should explain it fairly well: https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types
- The third point is because router firmware updates can sometimes not work properly or contain bugs that weren't caught in testing and can affect certain features or connectivity to your network. If your router's firmware page in the admin interface says it was updated around the same time you started having these issues then that's most likely the cause. A lot of the standard routers out there allow you to roll back to a previous version of their firmware by obtaining it from the manufacturer's website and simply re-installing the older version (which overwrites the newer one).
EDIT: I also wanted to state that a while ago I had a similar issue with Battlefield 3 where after I had been playing for a few months I could no longer connect to their MP servers. The fix was I had to contact my ISP and have them change my public IP address. Once this was done and I rebooted my modem and router I was able to connect again to their servers. This may be an easier route to take if you're not familiar with how to do the other steps I've mentioned. The only downside is if you happen to have anything running on your network that relies on that public IP being static (which most are nowadays at major ISPs) such as at-home web or server hosting then it'll have to be reconfigured with the new IP address.
File path C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
Check the Inbound and Outbound rules for Destiny 2 and if you see any of them with the red circle and slash in them, there is your problem. Right click on the problem rule, open up the Properties submenu, click on "Allow the connection," then click Apply. Restart your game and you should start seeing fellow guardians again.
Inversely, you may be able to disable these setting should you want to play the game solo. The rules that seem to block other players from connecting to you are named "Destiny2-Solo-1" and "Destiny2-Solo-2." Disable those and you can play solo with absolutely no blueberries. At least, that's what it appears to be.