JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by NeckPUNCHattack: 3/7/2015 3:27:17 PM
116

MARIONBERRY FIX plus BANJO FIX (If you used Google DNS fix and you get Banjo, try this)

I'm making a new topic to reach out to people using the google DNS fix. Keep in mind, the google fix will not work for everyone since some people will receive banjo error codes. I've included ways to get back online, along with the google DNS method. Okay, so you can use OpenDNS OR google in place of you current ISP's DNS to get you back on destiny if you keep receiving error codes & servers are down messages. Go into Settings > Network > select manual DNS. If you want Google DNS, enter 8.8.8.8 as the primary number and 8.8.4.4 as the secondary (it can be reversed and it'll work just the same). If you want to use OpenDNS, enter 208.67.220.220. into primary and 208.67.222.222 into secondary. Some people are now receiving BANJO errors after using the google DNS values, so I recommend the OpenDNS if you fall into that category. Once the values have been entered, your xbone, ps4, etc. will check connection after you hit B to back out to the dashboard and it'll say the connection is good. Restart your xbone (or ps4) BEFORE trying to jump back into destiny otherwise it won't work. Google might be a bit faster, but OpenDNS is more secure and has been around a bit longer (if that sort of thing matters to you). Hope this info helps and gets you back online Guardians!! btw..... this is sounding like a comcast/xfinity issue, so if you can't get online and you have this ISP, you might wanna manually change your DNS to the values listed above. Good Luck!! [b]EDIT:[/b] OpenDNS seems to be more reliable than google DNS. If it doesn't work for ya after you've entered the primary/secondary numbers, try swapping secondary for primary and primary for secondary. That seems to be able to resolve the issue in some cases. Hopefully that'll work for everyone who's still unable to get it goin. EDIT #2: I'm glad to know that these methods have helped out a bunch of people!! Now, keep in mind that changing your DNS to one of the provided numbers is only meant to be a temp fix for when you can't get online due to these error codes & should be changed back to your original DNS settings (done by selecting automatic settings in the DNS menu) after the problems go away. This is a helpful fix to get back online in Destiny when certain cable companies experience ip/dns problems or when Bungie's servers act up with error codes, but this shouldn't be a permanent fix. Just want everyone to be aware of that. Also, [u]please keep in mind that this won't fix everyone's problems[/u]. Some people who have been messaging me from around the world have said it works great (more so using OpenDNS), but some people will still experience the same error codes. This could be due to your location or a variety or other factors. I just want to make some people aware that this temp fix might not help everybody. Sorry, but that's just how these things work sometimes :(

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • [quote]I'm making a new topic to reach out to people using the google DNS fix. Keep in mind, the google fix will not work for everyone since some people will receive banjo error codes. I've included ways to get back online, along with the google DNS method. Okay, so you can use OpenDNS OR google in place of you current ISP's DNS to get you back on destiny if you keep receiving error codes & servers are down messages. Go into Settings > Network > select manual DNS. If you want Google DNS, enter 8.8.8.8 as the primary number and 8.8.4.4 as the secondary (it can be reversed and it'll work just the same). If you want to use OpenDNS, enter 208.67.220.220. into primary and 208.67.222.222 into secondary. Some people are now receiving BANJO errors after using the google DNS values, so I recommend the OpenDNS if you fall into that category. Once the values have been entered, your xbone, ps4, etc. will check connection after you hit B to back out to the dashboard and it'll say the connection is good. Restart your xbone (or ps4) BEFORE trying to jump back into destiny otherwise it won't work. Google might be a bit faster, but OpenDNS is more secure and has been around a bit longer (if that sort of thing matters to you). Hope this info helps and gets you back online Guardians!! btw..... this is sounding like a comcast/xfinity issue, so if you can't get online and you have this ISP, you might wanna manually change your DNS to the values listed above. Good Luck!! [b]EDIT:[/b] OpenDNS seems to be more reliable than google DNS. If it doesn't work for ya after you've entered the primary/secondary numbers, try swapping secondary for primary and primary for secondary. That seems to be able to resolve the issue in some cases. Hopefully that'll work for everyone who's still unable to get it goin. EDIT #2: I'm glad to know that these methods have helped out a bunch of people!! Now, keep in mind that changing your DNS to one of the provided numbers is only meant to be a temp fix for when you can't get online due to these error codes & should be changed back to your original DNS settings (done by selecting automatic settings in the DNS menu) after the problems go away. This is a helpful fix to get back online in Destiny when certain cable companies experience ip/dns problems or when Bungie's servers act up with error codes, but this shouldn't be a permanent fix. Just want everyone to be aware of that. Also, [u]please keep in mind that this won't fix everyone's problems[/u]. Some people who have been messaging me from around the world have said it works great (more so using OpenDNS), but some people will still experience the same error codes. This could be due to your location or a variety or other factors. I just want to make some people aware that this temp fix might not help everybody. Sorry, but that's just how these things work sometimes :([/quote] Thank you for the fix, I never tried the google dns but the open works fine for me :) will pass this thread on to anyone experiencing the same problems. Again thank you.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • [quote]I'm making a new topic to reach out to people using the google DNS fix. Keep in mind, the google fix will not work for everyone since some people will receive banjo error codes. I've included ways to get back online, along with the google DNS method. Okay, so you can use OpenDNS OR google in place of you current ISP's DNS to get you back on destiny if you keep receiving error codes & servers are down messages. Go into Settings > Network > select manual DNS. If you want Google DNS, enter 8.8.8.8 as the primary number and 8.8.4.4 as the secondary (it can be reversed and it'll work just the same). If you want to use OpenDNS, enter 208.67.220.220. into primary and 208.67.222.222 into secondary. Some people are now receiving BANJO errors after using the google DNS values, so I recommend the OpenDNS if you fall into that category. Once the values have been entered, your xbone, ps4, etc. will check connection after you hit B to back out to the dashboard and it'll say the connection is good. Restart your xbone (or ps4) BEFORE trying to jump back into destiny otherwise it won't work. Google might be a bit faster, but OpenDNS is more secure and has been around a bit longer (if that sort of thing matters to you). Hope this info helps and gets you back online Guardians!! btw..... this is sounding like a comcast/xfinity issue, so if you can't get online and you have this ISP, you might wanna manually change your DNS to the values listed above. Good Luck!! [b]EDIT:[/b] OpenDNS seems to be more reliable than google DNS. If it doesn't work for ya after you've entered the primary/secondary numbers, try swapping secondary for primary and primary for secondary. That seems to be able to resolve the issue in some cases. Hopefully that'll work for everyone who's still unable to get it goin. EDIT #2: I'm glad to know that these methods have helped out a bunch of people!! Now, keep in mind that changing your DNS to one of the provided numbers is only meant to be a temp fix for when you can't get online due to these error codes & should be changed back to your original DNS settings (done by selecting automatic settings in the DNS menu) after the problems go away. This is a helpful fix to get back online in Destiny when certain cable companies experience ip/dns problems or when Bungie's servers act up with error codes, but this shouldn't be a permanent fix. Just want everyone to be aware of that. Also, [u]please keep in mind that this won't fix everyone's problems[/u]. Some people who have been messaging me from around the world have said it works great (more so using OpenDNS), but some people will still experience the same error codes. This could be due to your location or a variety or other factors. I just want to make some people aware that this temp fix might not help everybody. Sorry, but that's just how these things work sometimes :([/quote] It works

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Comment so I can come back when I get home please!

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    1 Reply
    • No idea what I'm doing wrong. My internet has been fine for so long with rarely and error codes and now this. I tried OpenDNS i tried GoogleDNS and neither worked and now it's the day of HoW and I may not be able to play... Thanks bungie...

      Posting in language:

       

      Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    • So does this work with errors such as weasel also? Would love for it to fix that

      Posting in language:

       

      Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

      1 Reply
      • Take care when changing your DNS server. For example the Open DNS and Google services you provided are both based in California ... which is fine if that is a short number of hops from your router. However for customers further away in the US, or even worse outside of the US, may end up worse off given the extended number of hops required to resolved host names. An easy way to test ... run a ping test between these two addresses and that currently used by your router. And part 2 of this change ... If your ISP has a data cap, and part of that cap includes "free" addresses ... for example a bundled movie/entertainment package ... that this may now use up your cap as these "free" site can be masked through the alternate DNS lookup. And remember this is just a simple DNS lookup ... after that the game should be using the resolved address. However it would be nice to hear from bungie if this is recommended/required ... and if so for which hostnames.

        Posting in language:

         

        Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

        5 Replies
        • Somebody bump this please

          Posting in language:

           

          Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

          1 Reply
          • Does this only work with these error codes? I've just installed a new modem through Comcast yesterday and everything was fine both then and this afternoon. Tonight it all went to hell and I got 7 Caterpillar errors and disconnected from LIVE 5 times. All within two hours.

            Posting in language:

             

            Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

            3 Replies
            • This game has become unplayable for me. Receiving numerous error codes, such as Anteater, bee, weasel, currant etc. My router is plugged directly into my ps4 and im being booted after several minutes. Going to toss this game.

              Posting in language:

               

              Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

              2 Replies
              • Bump will try. Have always used Google dns servers, but last 2 months I've been getting all sorts of error codes I've never gotten. In fact never had an error code up until January other than the xmas ddos bs

                Posting in language:

                 

                Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                1 Reply
                • Check this out a full raid team just about to grab 2nd chest on CE. The entire team got booted with caterpillar, then no one was able to log in because of banjo error.

                  Posting in language:

                   

                  Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                  1 Reply
                  • I suggest for everyone to use namebench and/or dns benchmark to find the best local dns servers for their area. Once you perform a namebench test it will give you all the servers in a local area with fastest and most reliable at the top. I always use the top 2 choices as primary and secondary. I also experiment and go down the list if I don't feel like anything has changed. I used this method back when mw3 1st came out and the lag and hit detection were horrible and it helped reduce alot of the bs I was having. The Google servers I was using weren't the best for my area, some local Verizon server 110 miles away was like 24 percent faster with less errors. I'm only saying to use these sites to help find servers that are local or closer to where you are located. Having a server across the country usually makes things a bit worse due to ping time and packet loss due to the long distance traveled and back. Granted this communication is faster than the mind can comprehend and happens in hundredths and thousandths of seconds (pretty cool when you think about a signal from your computer hitting a server like 2k miles away and back in like 30 miliseconds. Not actual speed but using as an example, would probably be more like 100ms + unless on like Google fiber)

                    Posting in language:

                     

                    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                    2 Replies
                    • It didn't help. But thanks anyways.

                      Posting in language:

                       

                      Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                    • *sigh* Nope not working for me but hey I didn't have much hope to begin with. I've had Marionberry for 3 months now. 3 Destinyless months. PS4-Central Canada

                      Posting in language:

                       

                      Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                      1 Reply
                      • OMFG you are a[u] [b]LEGENDDDDDDDD[/b] [/u]

                        Posting in language:

                         

                        Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                        1 Reply
                        • Great advice, absolutely absurd that a solution has to come from a community member when there's been absolutely nothing helpful from bungie at all. I've been using 8.8.8.8 8.8.4.4 for a while but still get the errors, tomorrow I will give the open DNS's a go.

                          Posting in language:

                           

                          Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                        • It worked dude!! Thanks

                          Posting in language:

                           

                          Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                        • Edited by Rush: 3/4/2015 5:04:05 PM
                          Servers imploded a moment ago; banjos playing weasels abound.

                          Posting in language:

                           

                          Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                        • Just did open dns (xbox one, charter internet) worked great. Thanks man

                          Posting in language:

                           

                          Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                        • Whats a banjo error?

                          Posting in language:

                           

                          Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                        • I'm on Comcast and entering the open DNS was what fixed the error for me. Thanks man.

                          Posting in language:

                           

                          Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                          1 Reply
                          • May work for some ... many make it worse for many more. The location of your DNS will depend on how quickly it resolves the host, and a slow resolution could mean more errors - not less. Be best to test the IP of the DNS before changing it within the router ... just saying. Does bungie support or recommend this change ... and more importantly why?

                            Posting in language:

                             

                            Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                          • [quote]I'm making a new topic to reach out to people using the google DNS fix. Keep in mind, the google fix will not work for everyone since some people will receive banjo error codes. I've included ways to get back online, along with the google DNS method. Okay, so you can use OpenDNS OR google in place of you current ISP's DNS to get you back on destiny if you keep receiving error codes & servers are down messages. Go into Settings > Network > select manual DNS. If you want Google DNS, enter 8.8.8.8 as the primary number and 8.8.4.4 as the secondary (it can be reversed and it'll work just the same). If you want to use OpenDNS, enter 208.67.220.220. into primary and 208.67.222.222 into secondary. Some people are now receiving BANJO errors after using the google DNS values, so I recommend the OpenDNS if you fall into that category. Once the values have been entered, your xbone, ps4, etc. will check connection after you hit B to back out to the dashboard and it'll say the connection is good. Restart your xbone (or ps4) BEFORE trying to jump back into destiny otherwise it won't work. Google might be a bit faster, but OpenDNS is more secure and has been around a bit longer (if that sort of thing matters to you). Hope this info helps and gets you back online Guardians!! btw..... this is sounding like a comcast/xfinity issue, so if you can't get online and you have this ISP, you might wanna manually change your DNS to the values listed above. Good Luck!! [b]EDIT:[/b] OpenDNS seems to be more reliable than google DNS. If it doesn't work for ya after you've entered the primary/secondary numbers, try swapping secondary for primary and primary for secondary. That seems to be able to resolve the issue in some cases. Hopefully that'll work for everyone who's still unable to get it goin.[/quote] It worked for me thanks

                            Posting in language:

                             

                            Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                          • Open DNS worked for me. Thank you!!

                            Posting in language:

                             

                            Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                          • Edited by Toanman: 3/3/2015 12:20:49 AM
                            Worked like a charm thanx man.. good stuff

                            Posting in language:

                             

                            Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                          • I changed it to open then it suddenly decided to pop up with, "not so fast, your account has been disabled due to parental restrictions" so I went for a beer, tried again and it worked. Beer solved it.

                            Posting in language:

                             

                            Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

                            1 Reply
                            You are not allowed to view this content.
                            ;
                            preload icon
                            preload icon
                            preload icon