JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Scionyde: 9/18/2014 2:41:58 PM
281

Post Your Connection Issues/fixes Here - Home Networks

I have seen many of these threads, but it seems that most of the posts are just people ranting and complaining. I will say that I am quite guilty of that as well, and my patience is growing thin, but I think we should try to provide Bungie with more specific information so they can get our issues fixed as soon as possible. Please post your specific issues in here, and try to keep it short-ish, to the point, and present it in a professional manner so they don't have to comb through garbage to find what they could possibly need. I'll start by saying: I'm on the Xbox 360. I am on my home network. I get mostly just BEE and CENTIPEDE after entering any game zone. I can sit in orbit and stare at my ship for hours, but even entering a mission, strike, crucible match, or the tower nets me a BEE error within 2-10 minutes. I'VE HAD THESE ISSUES SINCE DAY 1. I've tried all the workarounds mentioned on this site (NAT Type, opening ports, QoS, disabling flood protection, DMZ server, static IP for router and console, hard resetting everything multiple times, deleting system cache, deleting and reinstalling the game, using a VPN, going wireless and wired, and multiple combinations of all of these) Any help/reply would be appreciated. We must keep hammering them until we are heard. Also, pass this around the forum: http://arstechnica.com/gaming/2014/09/eight-days-later-bungie-leaving-disconnected-destiny-players-stranded/ ^This is getting ridiculous. We are not a tiny portion of the community.

Posting in language:

 

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

View Entire Topic
  • Had the same weasel errors as everyone else (before that previously known as centipede) to be honest been getting problems pretty much since launch although not as often as I once did it's still bloody annoying Few things I have noticed though other might find helpful!! 1. Achievement lag seems to cause a boot 2. Tuesday reset day where players seem to on different versions causes issues I.e cannot join parties through friends etc. try getting all of party to restart the game especially for raids 3. Xb1 and ps4 maintenance periods always hurts destiny more than other games 4. Those resetting their routers in frustration be aware of dynamic line management aka DLM (uk anyway) this won't be helping your connection stability I was doing this it's a ball-ache for days after (until I researched its impact) go easy on your ISP Beucause in UK all ISPs use BTs exchange, with exception of Virgin. DLM is run through BT most ISPs have no control over it!!! 5. I requested my isp to turn my interleaving switch off my ping is 10 to London. I now get a consistent 74 Mbps down and 19 Mbps up although this might not be an option for most unless you have a pro package. 6. If you are on xb1 take the detailed network stats with a pinch of salt, it's getting data from the Microsoft Seattle centre not one from the local azure server to you 7. Port forwarding did nothing for me and to be honest The standard UPNP should be enough for most especially if you have a few devices connected! This should be reserved for people on campus or some other shared site most domestic users need not apply! 8. Obviously a no brainer but if you can connect to your router via Ethernet cable rather than wirelessly do so. If it's the latter play around with the channels using speedtest.net until you find the best channel. Most routers set this to auto which might pick up interference. 9. I have found a hard reset(holding xbox button for 8 seconds) helps also before turned off kinect which also seemed to stabilise for a time 10. Most routers have detailed network statistics check for noise margin and attenuation stats. Below a 6 is not good for noise... again research both of these, if anything you might squeeze a bit more speed out of your line when you do, will also give you ammunition with your isp 11. In uk those using fibre or adsl who are non virgin and wired to their router, look into using a splitter faceplate rather than filter with the master socket. You should see a more reliable connection. BT have just released mk3 VDSL filtered faceplate look this up as a first starting point and go from there. 12. My ISP is sky don't for a second Believe the bullshit they come out with, its clear after week or so of research I am now able to have a full debate and break down their poor scripting arguments with ease, and this is with their supposed "pro team" (I don't profess to be an expert in any sense). They also have very little in the way of diagnostics tools to help you, again the monopoly BT have in the uk by owning pretty much everything! Now if it's none of these sorry boys and girls your shafted like me :) ..... can it be anything other than bungie servers? Although some of these have seen me get fewer errors. Whether that's a result of my antics or Bungie who knows? The silver lining though is you might have learnt a bit along the way like I have:)

    Posting in language:

     

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

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