{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by ddn489:
12/11/2014 5:25:40 PM
10
ERROR - Lost Connection to Destiny Servers. "banjo" error code [ps4]
PS4
British Columbia, Canada, Telus internet service provider. 50mb download/10mb upload
It's 0915 hrs PST and I can't seem to connect to the destiny servers in my game.
I haven't really had any significant issues overall in my destiny experience, and I was playing just fine 12 hours ago. this morning when I logged on, I am getting an ERROR code: "Lost connection to Destiny servers. Please try again Later. For more information go to help.bungie.net and search Banjo"
Well I've done that, and I have a NAT type 2, I have all the ports open, static IP, port forwarded all destiny game ports to my console, and I've exited and resigned into my PSN account, rebooted my router. I've even tried de-militarizing my consoles ip address and closing all firewalls...
... and I'm totally lost. Not sure what's going on.
Oh not to mention, my friend who's in the same area, just different service provider (shaw) is playing right now, so I take it it's not maintenance...
-
I fixed this today! Close destiny then sign out. After that open up destiny then log in when the screen comes up. It should be fixed after that.
-
I fixed this today! Close destiny then sign out. After that open up destiny then log in when the screen comes up. It should be fixed after that.
-
The same -blam!-ing thing is happening to me! my roomate is playing destiny on his one right now! I even signed in on my account on his xbox and was able to play, what the -blam!-!?
-
1 ReplyEdited by Veselka: 12/11/2014 11:51:34 PMSurrey BC, also on a similar wired Telus connection, but on Xbox One. Also getting banjo errors at every attempt to log in. Couldn't play since around 2AM PST early this morning, Wednesday December 11. Own The Dark Below DLC, if it makes a difference. Followed every help step but still no luck. EDIT 1: Just got a 76.87 MB update (second update of the night) and I can now connect. The first update also allowed me to connect after my first signs of trouble but only temporarily, for about half an hour. I'll report back with my findings for this one.
-
1 ReplyHi Darius, I'm very sorry about the BANJO errors you are seeing. In some cases, this is a temporary network congestion issue that will clear itself up. You can test this by following the steps here: http://www.bungie.net/en/Help/Article/12147 In all cases, Bungie continues to investigate reports like yours in an effort to improve everyone's Destiny experience. Thank you for being patient while we that.
-
Damn even Rednecks are playing this game?
-
Just a quick update: I just downloaded an Update for Destiny right now and I am no connected, no problems at all.
-
1 ReplyIm in bc on a ps4 also, last night at 1 it kicked me with banjo errors but now its switched to cattle. I have a wired telus connection that nearly matches your download upload speeds
-
1 ReplyI can confirm this in Vancouver as well. I'm on the Xbox One on Telus and I'm getting the same error. I was able to play last night without a problem
-
3 Replies[quote]PS4 British Columbia, Canada, Telus internet service provider. 50mb download/10mb upload It's 0915 hrs PST and I can't seem to connect to the destiny servers in my game. I haven't really had any significant issues overall in my destiny experience, and I was playing just fine 12 hours ago. this morning when I logged on, I am getting an ERROR code: "Lost connection to Destiny servers. Please try again Later. For more information go to help.bungie.net and search Banjo" Well I've done that, and I have a NAT type 2, I have all the ports open, static IP, port forwarded all destiny game ports to my console, and I've exited and resigned into my PSN account, rebooted my router... and I'm totally lost. Not sure what's going on.[/quote] Same here. Close to 30 hours game time then last night boom. Cattle error. Can't be my network as its been solid whole time. Ddos perhaps?
