{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/12/2016 12:35:41 AM
19
Consoles on same network (LAN) fine before patch with me and two sons on same network. I am a senior network engineer working with major global companies. It isn't the local network and the firewall shows no blocks or dropped packets. I have not taken the time yet to run a sniffer trace, but really shouldn't have to troubleshoot a network at home to run a game. If running a trace and sending you all the packet captures to look through would help, i will do so.
- This all happened Friday evening with same gamertag.Could not play so went to overwatch which is where we have spent our weekend.
- Error message is to the effect that the 3rd person trying to join could not go to target as not all members are a part of a fireteam.
- I have no issues with two on the same network. They join every time and have done so since i made changes so that all Xbox Ones have a different name. Adding the third is where the issues sits for me.
I am willing to help if we can get this resolved for the rest of the folks wanting to play.
English
-
Just to be clear: All Xbox One consoles All caches have been cleared All Destiny ports are opened and verified in firewall and by packet trace All Xbox's have different names All Xbox's test fine as Open NAT (type 1) No issues with any other games - played Overwatch all weekend together with no issues. Affected gamer tags: The1NOnlyMrPie - (me) AnxiousGrain07 LeatherySafe90
-
So i have done some initial testing. The traffic is all encrypted in SSL/TLS so I am not able to let you know whats in the payload (which would make this easier, but would also make it easier to hack , so completely agree). The payload i could see I will not post. When i begin trying to join fireteam of local LAN user, the following is what i found: - My Xbox connected to miscrosoft server #1 - Probably for XBOX live - My Xbox connected to a Bungie server IP address: 205.234.119.83 on port 7501. Could be coincidence, but each time i tried to join the fireteam, that request went to port 7501. This network is NET-205-234-118-0-1 as noted by ARIN. There were only 3 total packets - 2 sent to Bungie and 1 reply - My Xbox connected to microsoft server #2 Received error that i could not join - "Unable to join target player. Please try again". Now, if i try to start from orbit and connect to them in orbit, i immediate get the error. if i am in an activity, or at the tower and try to join, the system will take me to orbit first and then give me the error. When going to the tower from orbit, the same sequence of events happens as above, with the exception that i get several more packets from the Bungie server, i get a couple more MS server connections, and then i get the IP of the folks i am joined with via matchmaking at the tower and connect to them on Port 1200 UDP. All other connections to MS and to Bungie use TCP. I did notice that the Xbox's would actually try to join a multi-cast address on the local LAN, but am not sure if that is a mechanism bungie wanted to use for connectivity, or if it is just a pure XBox usage. I am happy to share my packet captures if it will help.
-
And the thing that I was most looking forward to with ROI was custom matches with my son..... Well that's gone now LAN is stuffed up. Such a shame.
-
This now seems to one of many major issues post '12GB' 2.4.0 update. I have been reading a lot of post today. But, the fact that things have gotten to the point that someone like 'MrPie' has offered to help Bungie fix these issues makes me want to check to see if it is too late for me to cancel my pre-order for the 'Rise of Iron'.
-
We thought about it, honestly. But we've put so much time into the game and we still enjoy it that we thought to give them a few more days before before dropping everything. Hopefully the fix it and give us enough time to get ready together
-
But, that seems be the ultimate problem with Destiny, we keep hoping and they keep disappointing....
-
Maybe it is time to move on with other games. Such high hopes for this game when it came out, now look at the state they left it
-
"Maybe it is time to move on with other games" Well, that's the reason I'm here. To see what's going on and to judge what I should to do about the 'Rise of Iron'. But, as it stands now, from what I am seeing and not seeing from Bungie, I have no interest in any future games from them. So, the question is am I willing to give the 'Rise of Iron' a chance to turn that around....
-
Here's to hoping they get their shit together before they lose more loyal fans that have been here for years (I see that Reach character hahaha)
-
You should be working fur Bungie. They must've forgotten that Halo's popularity came from LAN and split screen matches...
-
i normally get paid well to figure out and fix network issues. I will do this for free just to get it working for me and all the other folks! Halo parties were the bomb with multiple xboxs .... the good ol days...
-
Do you think they'll get this fixed soon? It's pretty much a game killer if my girlfriend and I can't get to play together, especially since we just pre-ordered Rise of Iron last night to play together... There'll be no point in bothering with Destiny and I'm sure a lot of people feel the same. Cheers
-
Agreed. I've been playing since day one and I have a group of players i play everything with. And none of them can join each other and no one on my local network can join. I just hate how silent they are being on the issue. Its just seems like they aren't doing anything about it.
-
That's what really bugged me, how incredibly silent they have been about it post patch. Even a simple "hey guys, we messed up, it didn't work the way we intended. But we'll get it fixed before Rise of Iron". That would make things so much better for everybody. They really need to get better at things like that
-
-
I would hope so, but they have been looking into it for a while. Not sure where it is on the priority list. I think there are a lot of folks that play with family or friends on the same LAN. It works for other games, as we played overwatch all weekend since we couldn't do any destiny. It isn't an xbox/ps4 or network issue. Its how Bungie has implemented destiny for fireteams and what they are using for information to setup, track, and breakdown the connections around a fireteam. If they take me up on my offer of help, i will push it as hard and fast as i can.
-
Oh absolutely no issues with any other games. It's 100% on their end due to the fix they tried to implement. But not only are they going to lose a massive amount of players if this doesn't get fixed, but the fact they haven't even commented on it is incredibly unnerving
-
Completely upsetting. I am with you - at least tell us you hear us and are trying to figure it out, even if there is no fix date. Just acknowledging the fact you know, you have heard, and are working on it would make things so much better for the players and the mood. Of course, the "you" in all that (after the I am with you part) is Bungie - no one on the thread, just Bungie
-
^^^^^^This
