Banjo errors? (Destiny)
by narcogen 
, Andover, Massachusetts, Sunday, January 10, 2016, 01:30 (3335 days ago)
Anyone have experience with resolving a persistent banjo error?
After a few weeks hiatus from Destiny, I tried to login a few days ago and started getting Banjo errors on my Xbox One.
An Xbox 360 on the same network and with the same profile, also with Taken King installed, has no trouble connecting.
But the Xbox One cannot connect no matter what I do-- reboot the box, reboot the router, restart the game, etc.
The only advice from Bungie is with regards to wifi (my connection is wired) or to the PlayStation platform.
My Xbone is DMZed and has Open NAT. The built-in network test and multiplayer test both show no issues.
Playing other online games is not a problem, Playing online games from 360 consoles or computers on the same network is not a problem. The only problem appears to be Destiny, and it has persisted for several days now.
Anybody have any suggestions?
Banjo errors?
by Blackt1g3r , Login is from an untrusted domain in MN, Sunday, January 10, 2016, 01:31 (3335 days ago) @ narcogen
Try reinstalling?
Banjo errors?
by narcogen , Andover, Massachusetts, Sunday, January 10, 2016, 01:34 (3335 days ago) @ Blackt1g3r
Try reinstalling?
As a last resort, maybe, but since I have no discs that means redownloading the entire game plus patches and expansions.
I had it when there were profile issues.
by Funkmon , Sunday, January 10, 2016, 01:52 (3335 days ago) @ narcogen
On my nephews Xbox, it screwed with me like this. I deleted my profile and added it again. Solved problem.
I'll try that
by narcogen , Andover, Massachusetts, Sunday, January 10, 2016, 07:56 (3335 days ago) @ Funkmon
On my nephews Xbox, it screwed with me like this. I deleted my profile and added it again. Solved problem.
Just deleted and reinstalled.... still banjo errors.
Although it happens on my wife's profile on the same box, but not either of our profiles on either of two 360s, so I don't know. It's also not affecting other games, online or offline. Just Destiny.
- No text -
Last resort time.
Sadly, it may be your only hope.
Or play on 360. *shudder*
by Funkmon , Sunday, January 10, 2016, 17:22 (3335 days ago) @ BlackstarBSP
- No text -
Last resort time.
by narcogen , Andover, Massachusetts, Monday, January 11, 2016, 00:53 (3334 days ago) @ BlackstarBSP
Sadly, it may be your only hope.
Well, still no luck.
I've uninstalled and reinstalled the entire game (35+ GB), I've changed my MAC address, and I've deleted and recovered my Xbox Live profile.
Still nothing but banjo errors. Looks like my time with Destiny is over. It's been fun.
Try posting in Bungie support forum.
by Funkmon , Monday, January 11, 2016, 03:24 (3334 days ago) @ narcogen
- No text -
Port forwarding?
so you have 2 360's and an xbox one? Are the ports all forwarded correctly in your router? Could you move the XBONE to the DMZ?
My Xbone is DMZed and has Open NAT. The built-in network test and multiplayer test both show no issues.
doh. reading comprehension fail
- No text -
Port forwarding?
by narcogen , Andover, Massachusetts, Tuesday, January 12, 2016, 00:41 (3333 days ago) @ Schedonnardus
so you have 2 360's and an xbox one? Are the ports all forwarded correctly in your router? Could you move the XBONE to the DMZ?
Xbone is DMZ. I have the 360s and the One but they are not connected at the same time.
I'ved tried with and without DMZ, with explicit port forwarding and with none. It changes the reporting from "strict NAT" to "Open NAT" when I use the DMZ, but the banjo error occurs regardless.
Destiny has been working with the same configuration since launch; I've never had more than the occasional error. Something upstream of me has changed, and now all I get are banjo errors.
It's probably due to a Phalanx
by uberfoop , Seattle-ish, Sunday, January 10, 2016, 17:54 (3335 days ago) @ narcogen
- No text -
Banjo errors?
by MacAddictXIV , Seattle WA, Monday, January 11, 2016, 13:39 (3334 days ago) @ narcogen
I thought Banjo Errors were only a Midwest problem...
Teredo/IPv6 Problems?
by Beorn , <End of Failed Timeline>, Monday, January 11, 2016, 14:09 (3334 days ago) @ narcogen
The only other thing I can think is that the XB1 is able to utilize IPv6, but the 360 is locked to IPv4. If your ISP made (?bad) IPv6 routing changes, that might cause some issues. You could try disabling IPv6 altogether to force an IPv4 connection, maybe?
Teredo/IPv6 Problems?
by narcogen , Andover, Massachusetts, Tuesday, January 12, 2016, 00:45 (3333 days ago) @ Beorn
The only other thing I can think is that the XB1 is able to utilize IPv6, but the 360 is locked to IPv4. If your ISP made (?bad) IPv6 routing changes, that might cause some issues. You could try disabling IPv6 altogether to force an IPv4 connection, maybe?
No option in my router for IPv6 configuration. Pretty sure my ISP is not using it; no other devices on my network are getting IPv6 addresses from it.
UPDATE: Yeah, just checked, IPv6 in the router is already off.
I seem to have found it.
by narcogen , Andover, Massachusetts, Tuesday, January 12, 2016, 01:00 (3333 days ago) @ narcogen
Well, turns out this was something simple and stupid and obvious.
Poking around the router I noticed the primary DNS was not the usual one. And although the Xbox was supposed to be getting its DNS automatically from the router, for whatever reason, that wasn't working.
I put in the new primary DNS number manually, got a Destiny update right away, and now I can login. Does Destiny give explicit version mismatch errors? I'm wondering if maybe the IP for the update server was not resolving, and my Destiny client could not connect because it did not have the latest update (it was a small one, about 2 Mb.)
Thanks to everyone for their suggestions!
DNS!
by Beorn , <End of Failed Timeline>, Tuesday, January 12, 2016, 01:02 (3333 days ago) @ narcogen
Go figure. Glad it’s working!
I wonder why the other games worked.
Holy moly.
by narcogen , Andover, Massachusetts, Tuesday, January 12, 2016, 02:34 (3333 days ago) @ Funkmon
I wonder why the other games worked.
I think the ISP left the old DNS server up, but wasn't updating it. So it was missing some entries relevant to Destiny, but Elder Scrolls and Halo worked.
I dunno.