{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/21/2016 5:22:24 AM
46
Two consoles in the same house can not connect to destiny since The Dawning came out.
So I have 2 XBOX ONES in my household and my wife and I love to play destiny together. But ever since the new update that included The Dawning, we have been having a lot of problems joining each others fire teams. once or twice we can join our fire teams but for the most part we cant. we have reset our router, reset our XBOX'S and unplugged our XBOX'S and plugged them back in with no success. If anyone has a solution or anyone from Bungie sees this please help. I have spent hundreds of dollars just to play this game with my family.
English
#Destiny
-
This is a known issue I've had problems playing destiny on the same network since the April update . In fact we haven't been able to connect once since then and the problem still persists. We've had engineers out. tried different routers . Surfed countless hours of tech forums including bungie support forums and have not yet found a solution. It's been mentioned in a couple of different updates from bungie and some people's problems have been fixed . I hope you get yours sorted it's been so long weve given up on ours now.
-
1 ReplyI have a Netgear Nighthawk R7000 and with the Upnp on we can run 2 consoles at the same time on the same game.
-
Edited by CDRGreyGoose78: 12/23/2016 2:48:47 AMCheck your router settings. As long as UPNP is set you can hardware as many as your bandwidth can handle. If your router doesn't handle UPNP, like UVERSE routers, you can set one PS4/XBOX to DMZ plus on the router and start it first when you want to play multiple consoles. My son and I play two PS4s hard wired with zero issues. No restarts or other shenanigans.
-
If you can, change the 'channels' each PS4 runs on. Like, there are specific WIFI channels ranging from 1 to 14 I believe, I don't know how to do it myself but if you make it so that one console is on a good connection channel and the other is on another, it reduces the amount of bandwidth you take away from each other which promotes better connectivity. ... a quick google search would give ya more than I can, but I hope I helped in some roundabout way!! :)
-
1 ReplyTwo PS4s in my house, and we've been dealing with this since TTK. Tried hardwiring one, both, ended up putting both on wifi. Only thing that works reliably is to open the game, select character, try to join the other person, fail, then you both kill your respective consoles' network simultaneously. You'll get error code CANARY, then it works. Sounds more complicated than it is.
-
Don't have them both hard wired. My friend and I run two Xboxs and other friends have 3 in the same house with no problems because all are connected wirelessly
-
3 RepliesIt's not just you, it's not just Xbox, and it is not just since the Dawning. My wife and I have had issues joining in to the same Fireteam for months (two PS4's) In the Bungie notes they say they are 'aware' of the issue, but there hasn't been any progress that I have seen (not for weeks etc)
-
OK, I'm not sure if someone posted this below but I have the same issue but with two ps4s. They are both hardwired in. I find if you both quit the game completely and then start it at the same time if you join up as soon as you both get to orbit you can usually join into a fireteam. This works 99% of the time for us. Hope it helps.
-
2 RepliesEasy fix = buy a PS4 😂
-
I personally have had no issues doing this, playing on wifi at a friends place.
-
Got same problen with my gf solution one on wifi and one on hard wire wirked 4 us
-
5 Repliesthats what you get for buying xbox
-
12 RepliesGet 2 PS4s, works fine since it's the better console.
-
Are you hard wiring the consoles to your router or WiFi. Hard wire both if you can or at least 1.
-
1 ReplyPut one on ethernet & the other on WiFi.
-
I had the same problem. I don't know exactly what fixed it because I changed a lot of things at once but here's what I did: 1. I went through Bungie's checklist in the help section (making sure you have the right NAT settings etc.) 2. I changed my SSID and reset my router after making the changes. 3. I connected one console via WiFi and one via hard wire. After this we were able to join the same fireteam. I did not test if both would operate at the same time via WiFi. Hope this helps!
-
My wife and I have this exact same problem with our ps4's. Except it started happening for us when TTK came out. Still no fix in site.
-
Edited by StrikeKing023: 12/22/2016 2:13:08 PMWe have 3 xbox ones in the same house. We have a router and modem. They can all connect if they are on the same network. If I have 2 xbox's on the modem and 1 on router the one don't connect. And for the clowns saying it's an Xbox thing, it's the same with my ps4.
-
It also happens with PS4 too. Ever since ROI.
-
Edited by PuertoRocGrip: 12/22/2016 1:14:40 PMOne of my Xboxs is tied in with Ethernet and the my son is on wifi, No problem. I brought my own wireless cable modem though, got tried of my IPS modems, they always seem to have fluctuating NAT issue, I was always having to reset, of course this issue only happen when we both was log on destiny. Now it flows great, even when streaming. FYI: I brought Ethernet cable and tool off of eBay and routed my own line. Save a lot of $$$ over buying the length needed.
-
Me brother and I have this problem. What you do is both of you load up the tower and then quit the game at the same time and restart. If it works you should get weaseled when you sign back in and then you can join each other.
-
2 RepliesHave had 4 xbox ones on a home network running at the same time and 3 of them on destiny in the same fireteam without any problems.
-
I've had this issue since RoI launched... only work around I could make work is to try to join, get the cannot join message, go out to console (on both at as close to the same time as possible - has to be both although doesn't have to be exactly the same time) and close game, restart game and get Weasel error code (optional: join party at this point) get kicked back to Destiny title screen, restart from there and THEN join party... by that point it should all be good. Hopefully this helps, sorry about the wall of text.
-
Had this problem recently as well. Initially it didn't connect but we turned an XB1 off and relogged/ invited again. Worked then, if only for a couple hours. After we both started having shitty connection and I ended up being dropped from the IB match we were playing in. Couldn't join the fireteam period after the other player finished that last match. I gave up and went back to modding the fck out of Skyrim.
-
As soon as Rise of Iron came out this has been happening every week, it's honestly infuriating. I've had a few successes working around it. Turning off both xbox's then inviting again seems to work quite often. Sending an invite and accepting while picking your character at the same time has had some success too
-
Welcome to it. It's been that way for my house since august update....good luck getting a response that's anything but it's your fault
