{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Metni:
1/16/2017 3:08:32 PM
8
Hello CrimsonEchelon. Thank you for your detailed report, and I'm sorry to hear about the issues.
Since update 2.3.1.1, Bungie has been investigating an issue where players on local networks are unable to form a fireteam with each other, which is an issue that you may be experiencing. While Bungie continues to work on a solution, you will want to ensure that UPnP stays enabled. Port-forwarding may impact your ability to connect to players.
Please see this [url=https://www.bungie.net/en/Forums/Post/210716770?page=0&sort=0&showBanned=0&path=0]official support thread[/url] for more information. Apologies for any inconvenience this causes.
English
-
Edited by CrimsonEchelon: 1/16/2017 3:15:09 PMHey Menti. Ive tried that -- and even with UPnP enabled its not working - it maybe a crappy router/modem gateway - The only other thing i can think of is turning the gateway into bridge mode and trying a different router - which i will do when i get home today. I would think that a company link Bungie would have the ability to know how to fix this - its not really a little deal its a HUGE deal for people who are trying to game together.
-
You could try that, but when two consoles are trying to connect to Destiny at the same time, UPnP must be enabled. This usually eliminates any need of port-forwarding or having to use the DMZ. Feel free to let me know how it goes. Again, sorry to hear about the inconvenience!
-
No i hear you - and from what im seeing the UPnP is enabled - it still isnt working though -- Ill give it ago when i get home this evening.
-
Edited by Durandal: 1/16/2017 6:41:58 PMSometimes you have to turn off upnp, do a full reset of the router to wipe any stored info about things connected to it, and then turn upnp on, then hook up the consoles after that. (The consoles should be off -and I mean off, no power save mode,100% turned off - and disconnected from the router during all of that). Then when you hook each one up, make sure to assign a static ip to that console before powering up and connecting the next. Honestly, the community has done a lot of work and found a lot of different paths to try fixing this, and mentors and the guided help sections have long since fallen behind on that.
-
I'll try this when I get here home in about 6 hrs
-
Thanks chief. I'll make note of the Xbox 1/2 ips and then I'll unplug them while I do all this. So I'm clear. By reset - do you mean wiping it to factory or just unplugging it and letting it recycle its self - go do something for 15 mins then start. I'll assign the static ips prior to even plugging the Xbox back in
-
Partly right on this. Not full factory reset, as that can cause issues with your ISP. But do unplug it, do walk away for a while, do clear any the portray cache or memory. However, do not grab ips beforehand, that won't work. First, set up upnp, then connect one console. Get that IP address, and assign it as static in the router. Then do the same with the second. Mainly what you want to do is wipe all memory of ports in the router. The big problem with destiny and multiple consoles is that the consoles have been designed to always want to grab a port and hold onto it, and multiple machines will try to grab the same ports a lot of times, which mucks up the peer to peer connections. You want to try and get the consoles to grab different sets of ports from one another, so that they can actually be differentiated by outside connections.
-
Got it. You have been incredibly helpful and I'm so hoping this works. One last question. Clearing the cache in the gateway.. should unplugging if do this. Ive also read that the router/modem Combo can be an issue. Any advice on this.
