{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/24/2016 1:50:07 AM
9
Playing destiny with two different Xbox ones in the same house
I know blah blah blah go to the network trouble shooting page, Me and my room mate have been having this problem for 2 days now just got back into the game. We can not get into the same fire team, well ever once in a blue moon it will work. I have done everything the networking page said my UPnP is on. we are pulling a steady 100 Mbps and we are both using a wired connection.
PLEASE HELP FOR THE LOVE OF GOD we can not play the game like this I know it is an issue bungie is having and not fixing so FIX IT
If anyone has any idea I love to know
-
I had this problem for months with my roommate and finally gave in and chucked the ISP equipment out... got myself a new netgear nighthawk AC1900.. as soon as I had it setup and we got on destiny the problem was solved! Not only that but the connection stability and error codes are yet to come back after I have changed it and crucible has become a far better experience! Looking forward to the IB.. that'll be the proving grounds!!
-
Make sure both Xbox`s have different names, it seems to have fixed mine and I have three Xbox consoles in my house with no more problems.
-
Edited by mja calg: 10/25/2016 12:45:23 AMA friend of mine had the same issue. Tried opening ports, enabling / disabling UPnP and it would work once in a blue moon. Even with 1 person playing, Xbox One always reported Moderately Strict and with 2 playing in the same house, it was a Fecal Storm of no connectivity and drop outs. I had him log into the router and then have him reset it to factory defaults, wait for it to reboot, then unplug it for 5 minutes. After it restarted (the default had UPnP enabled), no problems at all. So apparently the more tweaking he did, the worse it got.
-
Edited by OvertArtifact38: 10/25/2016 12:41:03 AMUsually shutting down and unplugging my xboxes get it to work. If that didn't work I do it again but this time shut and unplug router. Very rare if I have to do it but that clears it up for me
-
1 ReplyGet a new router if you've done everything on your end - which has already been stated via guides and links. I'll provide mine regardless. There is one that was just discovered recently and a User on here figured it out. Had to do with splitters from his ISP. [url=https://www.bungie.net/en/Forums/Post/212910177?page=0&sort=0&showBanned=0&path=0]Here is his post.[/url] At this point I'd expect everyone to know how to or at least already have re-configured their home networks. [spoiler]Otherwise, here are the ones I tell people to at least double check on. [quote][url=https://www.bungie.net/en/Help/Troubleshoot?oid=13612]UPnP and NAT/Port-forwarding guide.[/url] [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Troubleshooting guide.[/url] Try [url=https://www.bungie.net/7_Clearing-cache-on-a-console/en/Help/Article/12539]clearing your Cashe[/url] as well. Another [url=http://www.thetechgame.com/Archives/t=706497/how-to-open-nat-set-dmz-forward-ports.html]HOW-TO-OPEN your NAT guide[/url]. (it hasn't been updated since 2010 with he new console names. Other than that, it still works).[/quote][/spoiler] [quote][b]-QA Test Engineer (a.k.a. AR IS4 NUBS)[/b][/quote]
-
Day 2: Still stuck in orbit.. can't join fireteam.. need help
-
Edited by The Dude: 10/24/2016 2:29:18 PMNighthawk Multiple bands/channels. Each console connects to own band/channel. You're welcome.
-
6 RepliesHey there, Currently, Bungie is aware and actively investigating the issue. You can find current updates and information in the [url=https://www.bungie.net/en/Forums/Post/210716770?sort=0&page=0]Marionberry, Canary, and Local Network Fireteam Issues[/url] pinned thread. Make sure your home network is properly configured by following instructions in the [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13612]'Allowing Destiny Connections' KB article.[/url] After attempting the above, you can provide Bungie additional information by following instructions in the pinned thread, Apologies for the inconvenience. Hope this helps! [spoiler][i]Death is not The Sickness unto death. ~ Soren Kierkegaard[/i][/spoiler]
-
2 RepliesHave you checked your router for some sort of hardware or NAT acceleration setting? The features it can enable can bypass certain functions in the network layers that can break port forwarding, especially when UPnP is used...which is critical for the game to function 100% for this game with multiple consoles on the same network. Also make sure UPnP support is enabled in each console"s network settings if the option is present. Might want to run the network test on them as well to refresh the interface and synch up with the router. There was actually a sort of bug in PS3 back in the day where you had to do that periodically to get UPnP to behave properly.
