Hello Bungie hope your listening, Still cannot connect to a fireteam and it's on the same server....Have a NVG599 from AT&T U-verse, they do not have a UPnP..
Resolution: opened ports you specified for Xbox 1 on modem restarted both consoles factory reset, (Did not WORK)
Set modem back to original default settings changed region on Xbox 1 consoles ( Did not Work)
Set consoles back to original changed them to static IP addresses (did not Work)
Set one Xbox 1 to wifi while other was wired, then both on WiFi both options, (Did not Work)
Tried having another player invite us both (Did Not Work)
The only option I have at this point is to get a gaming router however with the company I have there are only 2 compatible one for $259 which is the Nighthawk AC1900 and another from Arrise for $189 wtf..Bungie fix this I don't feel I should have to spend money on a router when before the update it was working fine..Any other options are welcome thanks..
-
3 RepliesHello, Thank you for your detailed report! 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. Additionally, below I have listed two [u]possible[/u] solutions that may be able to get those Guardians back on the field! Solution One: -Restart both games at the same time. - Be sure to only select your characters and do nothing else. - As soon as it loads, try joining together. This is a commonly used method, but usually doesn't have much success. Solution Two: - Leave one console connected via Wi-Fi. - Connect the other via Ethernet cable. - Try joining together. Sorry to hear any inconvenience this may cause. Hope this helps!
-
Edited by jnikoley: 3/1/2017 12:53:55 PMAnother forum user it attempting to configure his arris 589 and add a router to solve the same issue. I'd check up on that thread and see if he gets it working: https://www.bungie.net/en/Forum/Post/222810977/0/0
-
It's been a problem for over half a year now, I doubt it'll ever get fixed...
-
7 RepliesOk as per your request I had opened your ports as said in my detailed report, it still doesn't work as for buying a separate router to do this is insane your basically telling your loyal customers you cannot fix the update nor do you have any idea what caused it, so therefore by admitting fault of your own accord you want us as fans and loyals to pay out of Pocket our own money to buy the routers we need to fix this ourselves..Wtf..Are you kidding me at this point t I will be filing a formal class action suit against you and the company for what you are doing..Again not something I would like to do as I love halo and destiny but at this point t you are letting millions down by doing this, also as far as for some events you are doing for destiny and leaving xbox1 players behind and only going to PS4 or PC is bullshit..Again why all of a sudden do you not want Xbox players to play your games anymore why punish ppl who obviously love your games even though they own Xbox..Well sir for you I do not agree..Thanks again for the fond memories you have created for me but I will not have to stop supporting a company that doesn't take care of their ppl and are only in it for the money anymore..What happened to you Bungie..