{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/22/2017 4:19:16 PM
2
Up until the holiday season, I was able to play destiny with my wife locally and grand children remotely. since the last change I am now unable to join ANY FIRE TEAM WHERE MY WIFE IS A MEMBER.
If she leaves the team and am able to join them.
I cannot join her directly to form a team but can do everything that is expected with others.
I have followed the blogs, tried all the fixes and have come up empty handed on this issue and since nothing on my end has changed, it is obviously caused by bungie updates.
please note that I have a degree in networking so I know how to configure my home network, but seeing as how it was working fine until a little over a month ago... when will you look BACK and see what was done to create this problem.....I have purchased 2 ps4 consoles and your game specifically to play with family.
I enjoyed playing with my wife for almost a year before you and your team messed it up....Please fix ASAP . I will not purchase Destiny 2 unless you have done this......long before it gets here as my patience is running out with this issue.
This Thank you is in advance of any work so does not count if you do not fix tit.
English
-
Bearbeitet von RAIST5150: 1/23/2017 5:18:10 AMIt is a long shot.... but you might get lucky depending on your router. I noticed my Asus actually seems to track UDP in conntrack. Was a shock when I saw it keeping track of it like it was. I still run with UPnP though, because my daughter still gets on the PS3 sometimes when I am on the PS4, not to mention remote access to the media server and what not....just makes managing things easier. But.... I can turn off UPnP, and the game actually appears to work normally without ports manually forwarded or UPnP. The router appears to log the UDP connections as ASSURED and conntrack goes into that short countdown before killing them like you would expect with TCP, and since we are frequently pushing data back and forth, it appears to be keeping them open for the matches...behaving almost like a stateful TCP session. Just plain weird. Who knows....maybe you will get lucky?
-
Bearbeitet von NuTristan: 1/22/2017 7:08:56 PMJan 22nd 2017 - still having this issue. Please fix immediately. uPnp/NAT none of these issue fix it since recent patch
