{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/15/2016 6:18:48 PM
34
Hey, would you people listen to me for once? You're ignoring me, and I'm fed up. I want my rise of iron money back. My boyfriend and I game together on the same network and we can't connect to each other in any fashion while playing your game. Thanks to this, I will not be able to complete my Triumphs this week. I need him in my fireteam for hard mode raid, but because no one wants to complete hard mode raid, I can't just hand him my controller and ask him to game, because we never have a full fire team. So I'm stuck at daughters with a bunch of scrubs or randos from lfg, that are only trying to troll instead of game.
But now, since your update that was designed to fix the LAN issues, only made it worse, not only can he and i not connect without other people, we can't even connect to an almost full fireteam if one of us is in it.
I get it, you people don't even care. You sit back in your thrones and laugh because either way, you get paid. Either way, you still find ways to get money. Right before the biggest game of the year, now that everyone has preordered, and you have your money, you break one of the biggest things that keeps people playing your game. But you don't care, because you already got all the money for it. You don't care about us. You won't do jack shit to fix it. You broke it on an update that took all damn day, on an update you had to continuously extend for an additional 4 to 6 hours.
I hope you're proud of yourselves. When your loyal fan base refuses to buy your next "glorious" expansion, because they will remember what happened during this one, I'm curious as to who you're going to pander to.
Do something for those of us who got affected for WEEKS by this issue, then when you claim to fix it, you in fact make it worse and impossible to combat entirely. Either give us our rise of iron money back, or give us all triumphs tshirts for free. It's not for lack of trying. We're trying. You just won't let us.
Do something to make it right, bungie. If you claim you care about us.
English
-
Edited by GOTHICMYSTIK: 9/19/2016 8:08:11 AMhope you realize its your PlayStation right not the game lol but its ok your self entitled self ( clearly i censored that one ) google how to fix it if you want i will gladly link my paypal so you can pay me for fixing for you no joke i am a network engineer. i fixed mine my brothers and sisters and freinds alike LAN and NAT issues it is your router BTW. like i said GOOGLE RETARD or fork over 75$ for me to fix it
-
I don't own a gaystation. I have self respect. Thank you. Bye <3
-
My boyfriend and I had this problem also..the only way we resolved it was by hard wiring both consoles? If one of us goes wireless we can't connect again, dunno wtf causes it but it only happens on Destiny😠
-
There's a hot fix coming in tomorrow. I hope that fixes it because you are scary when you're mad.
-
You dont even know me
-
Thank goodness.
-
Haha lol
-
There's plenty of people out their who would be happy to help you with your Raid, me included. Have you joined the xbox raid groups? They are always full of people wanting to complete Raids/ KF/ PoE etc. Give it a go.
-
I did finally get it completed. Had to have my boyfriend play on my account, and join a group of five. So i didnt complete the raid specifically, but it got done. The amount of people offering to assist is phenomenal. I think I'll come to the forums for help over lfg (;
-
Yay! Glad you got it done. The bungie community in general are extremely nice and willing to help those struggling to get a task done. I'm on my weekend now so send me a friend request If you're on xbox one and I'll be happy to help out.
-
[quote]Hey, would you people listen to me for once? You're ignoring me, and I'm fed up. I want my rise of iron money back. My boyfriend and I game together on the same network and we can't connect to each other in any fashion while playing your game. Thanks to this, I will not be able to complete my Triumphs this week. I need him in my fireteam for hard mode raid, but because no one wants to complete hard mode raid, I can't just hand him my controller and ask him to game, because we never have a full fire team. So I'm stuck at daughters with a bunch of scrubs or randos from lfg, that are only trying to troll instead of game. But now, since your update that was designed to fix the LAN issues, only made it worse, not only can he and i not connect without other people, we can't even connect to an almost full fireteam if one of us is in it. I get it, you people don't even care. You sit back in your thrones and laugh because either way, you get paid. Either way, you still find ways to get money. Right before the biggest game of the year, now that everyone has preordered, and you have your money, you break one of the biggest things that keeps people playing your game. But you don't care, because you already got all the money for it. You don't care about us. You won't do jack shit to fix it. You broke it on an update that took all damn day, on an update you had to continuously extend for an additional 4 to 6 hours. I hope you're proud of yourselves. When your loyal fan base refuses to buy your next "glorious" expansion, because they will remember what happened during this one, I'm curious as to who you're going to pander to. Do something for those of us who got affected for WEEKS by this issue, then when you claim to fix it, you in fact make it worse and impossible to combat entirely. Either give us our rise of iron money back, or give us all triumphs tshirts for free. It's not for lack of trying. We're trying. You just won't let us. Do something to make it right, bungie. If you claim you care about us.[/quote] Get a grip on reality
-
If you still need help with anything, my group and I should be on most of the day Saturday, send a message or invite, we are experienced adult players who get stuff done efficiently and have fun.
-
Hey wicket long time no see (it's GoS VoLt) If you ever need an extra to help with sherpa runs let me know
-
Any chance you'd help me and a friend out with the kings fall raid norm and hero?
-
Everybody in our house is having this same problem. This is the situation: Fibre to the premises Layer 2 internet connection, routed through vendor supplied specific (Netcomm NF12) router, uPnP enabled. No upstream filtering of any kind which should affect this problem has been confirmed with network provider. Four players, Three Xbox Ones All Xboxes report Open NAT (Cone) All tests report fine, all other functionality and software running on the Xboxes and every other of the myriad of devices in the house have no connectivity problems of any kind, on the fly port forwarding by uPnP works nominally as intended, including Teredo tunnelling - no filtering option enabled or present in the Router. There are two manual port forwards configured: TCP/UDP on 12345 and 1194, which should not be even in the realm of possibility of impacting what Destiny should be trying to use? Since a Destiny update that occurred sometime approximately in the last month or two, nobody can join each other in the house in a fireteam, whereas it used to work flawlessly. Internal network configuration has not been modifed for many months and is close to best practice as possible for consumer grade connection. Xboxes have had their cache cleared, soft and hard reboots, alternated MAC addresses, all switching and routing gear checked and rebooted just in case it magically helped somehow, many other things tried. The only thing not yet done is to completely erase the game on each machine and completely redownload many GigaBytes on each machine. This is probably the next thing that will be tried even though it seems unnecessary for so many reasons, if that resolves the issue then this only makes the problem worse - for that to be required. Setting up multiple public IPs with multiple NAT is also a possibility, as is manual port forwarding/DMZ etc, but will not be entertained and should not be required either. Your help page specifically states that in this configuration of multiple consoles behind NAT, uPnP must be used - It is, and works correctly for everything, it also worked correctly for Destiny until recently. On to the impact: Destiny is played together whenever possible, which is not a great deal due to work commitments. Interest in the game had been lagging for some months but was invigorated by the potential for the Rise Of Iron expansion, which has been preordered by two players in the house already. Players in the house not being able to connect to each other's fireteams was only discovered within approximately the last fortnight due to said lack of recent interest, it has already created frustration, hence this post. If this continues after Rise of Iron has been released then frustration will turn to Anger. Interest in Destiny (and likely any other Bungie title) will be significantly impacted, perhaps irrecovably. This is not some threatening rant, only reality. Playing Destiny is a choice, there are many others available. From all the posts in the forum I can see and the lack of mention in the official Known Issues, there appears to be denial about this clearly widespread issue affecting many, which only make this worse. Impact for this issue could be limited to certain vendor's routers - but that could still be a lot of players, and they may have little choice about the infrastructure used for connection.
-
Edited by Sherpa: 9/18/2016 3:31:42 PMOkay I might be able to help Are you aware of how to put your console (console ONLY) in the DmZ? There's no risk to having the console in it at all as long as it's only applied to the consoles and not the entire network. Try doing that for 2 consoles and see if you can connect. If you can't switch it back. If you can connect then contact your ISP and let them know. See if there's anything they know that might help seeing how it's working in the DmZ [spoiler]this worked for me when I was having that issue. I portfowarded 1 Xbox and DmZ'd the other. Have had zero issues since then. You just need to make sure it's only the Xbox going into the DmZ and no computers etc. I had a friend somehow manage to put 4 laptops into the DmZ instead of just his Xbox lol so that's why I'm stressing the JUST the Xbox part. [/spoiler] Here's a link if you need it http://www.xb1.co.uk/features/how-to-set-up-a-dmz-for-your-xbox-one-router/
-
Thank you for this. Here is to everyone telling me it is "just my connection". I am probably not using the same ISP as this valiant guardian yet we are having the same issues. So now, bungie, time to own up.
-
I know the problem you're experiencing, I had it when I first started on my game. Me and a friend play Xbox at his house and we all link in through the same router. The problem isn't actually with Destiny or your Xbox it's actually the problem with the router because some routers aren't optimized to handle more than one gaming system at a time. I myself had to go buy a $280 router before I started to have no problems no matter how many times I attempted to fix the connections. If you're not running a router with at least a 20 megabit upload and a 40 megabit download, you're probably going to run into this. One solution we found was to move an Xbox to outside of the firewall zone for the router, also known as the DMZ.
-
Let me YET AGAIN reiterate to those of you who can't read, we DID NOT have issues before update 2.3.1.1. So if all of the sudden we are just having issues, it is not my system. For the love of all things holy, please learn to read
-
You're a really nice person (sarcasm)
-
Edited by Kell of Kellogs: 9/16/2016 3:07:37 AMBungie has a stickied official thread regarding local network issues here that includes known information and a possible temporary workaround https://www.bungie.net/en/Forum/Post/210716770/0/0
-
Known and disclosed being investigated, meanwhile using ambiguous wording to downplay, all in a sticky. Meanwhile, no mention in the Known Issues post that most people will see when searching for a solution. That is a nice way to waste a lot of people's time trying to fix an issue that they cannot or should not have to. I have some ideas about why this tact would be taken, in addition to many of the reasons why this is difficult. However, the forums appear to have evidence of similar issues prior to TTK release as well, in addition to so much more which seems pretty clearly evident now to me that I have looked because of this issue, I have spent too much time on this already though.
-
Edited by HaggisHelper: 9/15/2016 11:29:06 PMGreetings, As a network administrator and a player of Destiny since launch I have run across your issue multiple times and it is often an internal hardware issue. I understand you feel taken advantage of but understand that there are others that are playing Destiny in multi console environments. If the issue was at the Destiny level then no one would be able to play with two boxes in the house. There are routers/modems which are unable to serve two consoles by UPnP simultaneously. There is a list with routers in the network hardware section of this forum: [url]http://forums.xbox.com/xbox_support/networking-hardware/default.aspx[/url] where you can check if your router is listed. Please keep in mind, that port forwarding or using a console in the DMZ will not resolve a multi console issue, regardless if it is an XboxOne or a 360. I will be happy to answer any questions you may have, message me on XBL. P.S. I also encourage you to check out [url]www.the100.io[/url] , this is an alternative to the LFG forums where you can find "similar" players. My group Charlie Company 776 is very active in helping others complete their MoT. In the meantime perhaps this avenue might help you complete your tasks without your signification other. XBL: HaggisHelper
-
I have had 3 xbox ones running just fine on my router for 2 years since Destiny dropped on day one. The only issue we ever had was being in voice chat because the port for voice communication doesn't always switch efficiently mid-speech. That was ok because we are all in the same house and otherwise we could connect and play as a full fireteam. Using Xbox Party chat usually fixed that issue when we were in a Raid, though. The update made it so connecting and staying connected is impossible. It's not a perception on our part or that all of our hardware simultaneously stopped providing functionality that was working before. I can still play COD:BLOP III just fine with everyone, and Elder Scrolls Online, and Halo 5 (though we rather not) or various other multiplayer games. The alternative is to go out and pay my ISP for an additional 2 IP addresses so that we aren't sharing 1 IP. Destiny is the only game effected by this situation in my collection and only as of recently. So while I can agree that hardware can contribute to the issues (like the voice chat issue) because of the fact that the router is switching data transfer over the various ports, but it worked well enough for 2 years to play a full fireteam from my single IP until the update. The only factor that has changed in my environment is the update last week, so that is the most likely source of the issue.
-
My internet for a couple months has handled mutli consoles just fine. It wasn't until Bungies updates that it started screwing up.
