{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/2/2014 8:12:45 PM
2
Nobody home
Hi,
I tried going on 6 strikes, all of which sent me in on my own after timing out during "Searching for Guardians". I've been stuck waiting to join the crucible for 15 minutes, nobody is in the tower and I haven't seen anyone on patrol.
I thought it might be network issues, but my NAT is open and all ports are being forwarded.
I'm on Xbox one and have only seen the 'mongoose' error message when joining the crucible timed out.
Could it be me still? And is there any way to do some network diagnostics from within Destiny?
Thanks,
ein23
-
Gametag, suckerpunch509 Xbox1 Error code mongoose Haven't been able to find any info on this error code. Cant get into crucible cant see other players unless on their fire team. I am hard wired to router, have open nat, and have port forwarded. Any help is appreciated. I still think this is a great game despite issues.
-
1 ReplyNAT2 Works for me, in my 2-3 weeks I've never had a single issue. In my opinion it's a fault of Where you Live [spoiler]No joke, strike with European Friends = Breezing through with laughter and dancing vs. Strike with American Friends = Disconnects and Rage Quits[/spoiler] I like both ways, always entertaining.
