{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by DigitalGoomba:
8/8/2016 12:12:43 AM
34
"Unable to join target player. Please try again."
Wife and I gameshare on the Xbox 1, we've played together since TTK dropped with no problems. After the last patches and updates with the beaver/ weasel problems, we can't join up in a fireteam anymore. We can join on other friends all we want, just not at the same time. One of us has to leave before the other can join up. Anybody know of any fixes? I've heard of this issue before, but haven't heard of any fixes, except maybe a complete factory reset. Any info would be great, but Nat type is not the issue.
Update: Hook one of your consoles up with an ethernet. It worked for me. Hopefully it will work for others.
Update: Ethernet wired network worked for one night. Today I can't fireteam with my wife again. Thought it would at least be a temporary fix until Bungie fixed their end.
-
1 ReplyDid anyone get to you from bungee? I'm having this problem now that I'm playing again with my roommate.
-
I was having the same issue just now, but we, like others, we're able to play a mere month ago with no issues whatsoever. We just got the ability to join, and i wanted to tell you what i did. Comcast gateway device with 100mb connection -> Wi-Fi to both ps4 consoles-> not joinable in game. Gateway Wi-Fi to one console, Ethernet cable to other-> still no luck. Comcast gateway to Netgear Nighthawk Wi-Fi router Wi-Fi to console 1, Comcast gateway Wi-Fi to console 2, no dice. The one that finally worked was Comcast gateway connected to the wan port of the Nighthawk, then connected both PlayStation 4 consoles to the Nighthawk Wi-Fi, and we were joinable right away. Doesn't make a damn bit of sense to me, especially since the traffic has to pass through an extra device (the Nighthawk) but it works. Good luck!
-
We've been having the same issue daily since July too. We are both connected to the router via ethernet cables and have always been able to join each other's fireteams without issue - until the beaver/weasel problems. The only way we can get around it is to close and restart the destiny app - sometimes we have to do it more than once. It then usually comes up with an error message saying we can't access destiny servers, but then it will usually work. We both have to do this though, which can be really annoying if one of us has already started a prison run or nightfall or something. Would be great if they fixed this already! It must be something on their end!
-
FIXED! we've been having this issue at my house with 2 ps3 consoles, one was wired and the other was wireless and it wouldn't allow us to join each others fire team....this is what I did to fix it: turned on my laptop and downloaded virtual router once you set up the program (its free, and its safe) you turn your laptop into a router which creates a different IP Address for the second ps3 console connect 1 of the consoles to the laptop wifi and it worked like a charm! good luck!
-
FIXED! we've been having this issue at my house with 2 ps3 consoles, one was wired and the other was wireless and it wouldn't allow us to join each others fire team....this is what I did to fix it: turned on my laptop and downloaded virtual router once you set up the program (its free, and its safe) you turn your laptop into a router which creates a different IP Address for the second ps3 console connect 1 of the consoles to the laptop wifi and it worked like a charm! good luck!
-
3 RepliesSame thing happened to me. My son and I played destiny together since launch. Now after the last update; can't join. It's really frustrating to do the kabooky dick dance of multiple console and router/modem resets just to try and play together. Every other game we join up seamlessly. Stop investigating your problems and start fixing them Bungie. Thanks.
-
This has just started happening with me as well, and just like you Ethernet tricked worked for like 2 days and now back to unable to find target player.
-
Is there any news on this getting fixed? I'd like to play my game again.
-
17 RepliesHi DigitalGoomba, We are aware of player reports on this issue and are currently investigating. Thank you for your report.
-
2 RepliesI have an idea to try as a workaroud. Before I tell you what it is, here what I think might be the cause of the problem: Bungie plays, hosts, and tests Destiny on a LAN. The code to do this is in the game, but this feature is not accessible to us, it's essentially "locked". I believe this coding may be somehow causing the errors. Basically, the game is recognizing that we have two consoles on a LAN, and attempting to establish a connection, however, it wont work. The Destiny we play must connect to other players through the internet. Here's what I suggest to try: note: - before trying this, you will need a second router, or a laptop. - I'm assuming we know how to connect our consoles to a router. 1.) Connect one console to your primary router (router 1), preferably wired. 2.) Take a second router (router 2) or laptop, and connect it to your primary router via ethernet cable. -Note: We want both router's DHCP turned on. Do not place either router in bridge/no NAT mode. 3.) Connect your second console to router 2, preferrably wired. If you are using a PC/laptop instead of a second router, you'll need to know how to share it's internet connection. Essentially, you will be using the pc as router 2. Note: -Doing the above will double NAT your second console. This is normally bad, but being able to play is better (if it works). If someone can try this, and it works, please reply back. Good luck.
-
10 RepliesEdited by jnikoley: 8/6/2016 2:05:36 PMThe problem is mostly occuring when you have more than one console sharing the same internet connection. When sharing a connection, you must use UPnP, NOT port forwarding or DMZ. Sometimes your router's firewall causes problems. Another possible cause is if you are Double NAT. Double NAT results from connecting through a router that is connected to a combo modem/router. Most ISPs provide a combo modem/router, even though they may refer to it as a "modem". The easiest way for you to tell if it's really just a modem, is to look at the back. On a cable modem, it will have only one ethernet port, while combo modem/routers will have two or more ports. Here's what I would do to potentiall fix the issue: If you are Double NAT, log into your modem (not your router), and make sure it is in Bridge mode/No Nat. Save the settings, and re-boot. Log into your router. Make sure you turn off port forwarding and DMZ. Make sure UPnP is enabled. I suggest you turn off any router firewall settings other than for the ident port firewall. After the settings are saved, re-boot your router. Turn on your xbox, and verify your internet connection, and NAT type is "open". On playstation, an open NAT is Type 1 or Type 2.
-
Same problem.... Pfff :(
-
1 ReplyCome on, Bungie. This error has occured for us since the last update. It has NEVER been an issue until now. Please let your fans know when this will be fixed. I'm not about to sink more money into the new expansion until I know that I will be able to play with my son as before.
-
1 ReplyEdited by NewClearSnake: 8/4/2016 7:28:40 PMSpouse and I play on the same network connection as well (with a shared game license like you), and while we haven't noticed any uptick in this problem lately, it does happen on and off for us. When it does, one of us soft resetting our box usually fixes it. If that doesn't work, the other tries the soft reset. If that doesn't work, one of us hard resets, and if that doesn't work then the other does the same. If we tried all that and it still doesn't work we reset our router, and if that doesn't fix it we do something else that evening. N.B- Our router configuration is NOT the same as Bungie recommends. We had to figure something out back in Y1 when there was no help article guiding the settings for UPnP and port forwarding, and used people's general recommendations for the Xbox One we found online plus a call or two to Xbox Live Support. So, despite what Bungie says here: https://www.bungie.net/en/Help/Troubleshoot?oid=13612 we DO have UPnP enabled as well as port forwarding rules set up for one of our two Xboxes (the ports to forward were gleaned from some old help forum for people in two-console households who have trouble playing and/or party chatting together). We used to have the second Xbox in the router's DMZ as well, and that setup works for another couple we play with, but it did not work for us. Spouse (who I suspect is somewhat better than me with networking) says "routers are different enough, with differing implementations of UPnP that it's crazy to think that that the same setup would work for all routers."
-
Same. Repeatedly. For 2 weeks I've been unable to join a fireteam in orbit. I could sometimes join if already in an event (Challenge of Elders, Raid, etc...). Please Fix.
-
My wife and I are having the same issue. We were able to play without any problems until recently. I have 3 Xbox1's in the house and no matter which one I try from we get the same issue when trying to play together. I have tried it all. Wired, Wireless, NAT checked....nothing works. It is frustrating since we enjoyed playing together. I guess it also answers my questions on if I should get the new expansion or not.
-
I'm having the exact same issue. I've never had any problems that couldn't be fixed with a simple reset of either the xbox or my router. This is extremely dissapointing as I just got done working over 50 hours this week and was looking forward to jammin after work with my friend. Now we cant.
-
Easier solution buy a network booster for unknown $ but cheaper then a new router.
-
We actually resorted to connecting one PS4 to 4g mobile hotspot, it's NAT 3 so no chat but at least we can join each others' fireteams. Hoping Bungie sorts this out before I run out of bandwidth! One run througn of CoE ran to nearly 200MB.
-
I have reduced the frequency of this error, but not stopped it totally, by changing one of the two XB1's default names so that their names on the network are different, and by quitting/reopening the game, sometimes on one console and sometimes on both. Say again, this is still a huge issue, but hope this helps some more people play together again.
-
My boyfriend and I were playing together last night but tonight we can't! We were gonna do nightfall together and his spindle quest. We have a third that wants to come too and even with the third as leader we can't join him if the other is with him. It's really annoying.
-
Same thing here. Unable to play with my kids since the update. I've tried many things and am getting pretty frustrated. Shame on you Bungie.
-
This morning I gave up after 24 attempts to join my son's fireteam and vice versa. :-(
-
My wife an I are still having problems . is there any work around yet?
-
Any update on this? Has been going on for ages now, you'd think this sort of thing should take priority over new releases..?
-
Having same issue; husband and I have to keep restarting PS4s until it works.
