JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by DoomGuy: 1/26/2019 10:19:53 PM
5

Should Bungie liaise with ISPs regarding network DC | P2P Transfer?

Resolved.
English
#Help

Posting in language:

 

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

  • Hey, I'm also on Talk Talk fibre optic and got the game yesterday. To my frustration I've been greeted by lions and flys and bees oh my! I literally got disconnected every few minutes so today I thought I'd have a mess around with my connection. I'm not incredibly technical or anything but basically what solved my issue was to change some settings on my modem, not my router, the actual BT Openworld modem. I signed into it with username and password as admin and then went onto advanced settings. I noticed that there was a power saving mode on which I have switched off and also on the firewall the settings were set to "Talk Talk" which I changed to low. Since doing this I haven't seen a creepy crawly or a big cat message since, running absolutely perfectly. I think the issue may have been with the talk talk firewall. Have a go with that as it worked for me!

    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've thought about it a lot, and this seems like it's the best way to go. I've tried everything to the point that I'm fairly certain the problem isn't on my end. That leaves Bungie's networking and the ISP itself. But our ISP has tried to fix it twice and couldn't find any problems; Bungie knows what their game needs better than anybody, maybe they could issue a general statement of what the game requires forwarded/opened/etc that we could individually get to our ISP in hopes of them finding the problems and fixing them. Or, like OP said, maybe our ISP is just full of blithering idiots. It wouldn't be the first problem we've had with them...

      Posting in language:

       

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

    • Your post is very well written and you make an excellent point although as someone else mentioned here I don't know how practical it would be for Bungie to contact all ISPs. I have a suspicion that there is some sort of security conflict between different users sharing the same always online world. I have noticed that the tower or busier patrol areas with lots of other players seem to have the most disconnect issues for me.

      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
      • I think they just need to take the responsibility for more of these errors... For example, I am receiving the Caterpillar error constantly. The Bungie help website states that if this error is received, one should try the action again, if the error persists, restart Destiny, if the error STILL continues, Bungie is running tests on their end. "Pardon our dust." However... I've had this error since Sept. 15th, the first time I popped the game in my machine! Oftentimes when this error would occur, I would be disconnected from Xbox Live (xbox 360). Now, when I play other games, near the middle of matches, I'll get disconnected from Xbox Live. Before the 15th, I had zero issues with Xbox live, which leads me to believe Destiny corrupted something within my Xbox or changed some setting in my Xbox which then corrupted something further. This is not okay, and Bungie's help website does not "help" at all. So, I believe Bungie needs to step up and take some responsibility... Or give some kind of information that I don't have.

        Posting in language:

         

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

        9 Replies
        • Edited by mikelimtw: 9/20/2014 6:23:51 AM
          I had not read this post by Bungie till just now. It seems I've independently come to the same conclusion as they have regarding the potential fault in connectivity, so I can't in all honesty trash this response. But for most users, if they haven't spent time thinking through this issue like I have, then the response will seem a bit shallow and flip. In hindsight, my own personal experience now suggests that Bungie's network and the Destiny servers are actually quite solid. I say this with a caveat which I will address shortly. But the evidence certainly suggests that if the servers weren't solid, there would not be as many people saying they've had no problem on the Bungie forums. The internet being what it is, the overwhelming weight of posts would have been negative if this were the case. Having said this, I think it is grossly negligent for Bungie to be downplaying the issue of home users by saying this is a problem faced by a small minority of people. [b]I don't believe that one bit![/b] The whole world isn't located behind a university firewall, and I suspect the larger population of Destiny players are actually home users. Furthermore, while I see comments from both sides of the issue with some having no issues and others handicapped to the point of not being able to play, most of these posts seem to originate from North America. I think that the rest of the world is also being grossly under-represented. What Bungie is essentially saying is the best way to determine where the fault lies, ie with your ISP or with your own networking equipment is to first eliminate your connection through your home router and connect directly to the internet via your broadband router. The assumption being made here is that Destiny servers are actually stable - which my own experience now points to this as fact. If your connection becomes stable when connecting your console directly to your broadband cable/DSL modem, then there is something going on in your router causing dropped packets leading to connectivity issues. If connecting directly to your broadband modem doesn't resolve the issue, then it is something in the way your ISP has set up your service causing dropped packets. This is a good test because it allows you to exactly pinpoint the origin of the problem.[b] If you want to quickly test whether your router or your ISP is the problem, you can just disable your router's built in firewall if it is enabled. This should tell you everything you need to know without having to disconnect and reconnect your router/console equipment. [/b] In my case, the problem was actually in my router. I have an ASUS RT-AC68U. It is a very expensive WIFI router and is among the highest rated in terms of performance. I actually upgraded to this router in preparation for Destiny, so my own personal investment in this game goes way beyond just purchasing the game itself. In Taiwan (which is where I live), ISPs don't block or otherwise filter internet packets. They also don't have data caps. The average 100mbps broadband connection goes for about US$30 per month. Internet connectivity in this country is very, very good. I reasoned that if my ISP isn't the problem, then my router was. I checked through my settings and the only thing I could think of was that the router firewall was possibly filtering packets. So on a guess, I turned off my router's firewall and I also disabled DDoS packet filtering. Like MAGIC, all my connectivity issues went away. I was able to connect with Destinty servers and have had only one disconnect (no error code, just lagged out) in about 7 hours of playing now. This is why I can say with near absolute certainty that Destiny servers are actually quite solid. If you went to the trouble of connecting your console to your broadband modem and it still doesn't clear up your connectivity issues, it doesn't mean that your own equipment isn't contributing to the problem. It only means that your ISP is also part of the problem. To get around this, you have several possible solutions. The first is to talk to your ISP to see about placing your broadband modem into BRIDGE mode. In this case you are given a static IP address from your ISPs servers and the broadband modem's firewall should be turned off. If this is not an option, then your next best bet is to use a VPN service that guarantees fully open internet access without any P2P filtering. Ostensibly it is due to your ISPs packet filtering that is causing connections to drop. There are two ways to go about setting up a VPN, directly and indirectly. For the indirect method, you can configure your home PC for a VPN connection; then you can search this forum for configuring ICS (Internet Connection Sharing) on your home Windows PC and get your console to connect to it. The direct method requires you to spend a little bit of money, but is in my mind worth it. Many of the newest ASUS N-routers are VPN enabled, meaning they can be configured so that the WAN connects directly to a VPN server. You can get an Asus N-16 very cheap and it will have this capability. The upside to configuring your router to access a VPN directly is that all your devices that will connect to your router automatically get a VPN connection as well. This helps to get around the one device limitation that many basic VPN packages have. Now to my caveat: While Destiny's servers seem to be solid, there is really no excuse for Destiny causing problems on networks such that you need to turn off your router's firewall and go through all sorts of gymnastics with your ISP. If this was the norm for online MMO games, then I'd have nothing to say about this. But the fact is, this is not the case. Everything I have works fine with my router's firewall enabled, and with my ISPs service. This should also be the case for Destiny.

          Posting in language:

           

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

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