JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will be temporarily offline today for scheduled maintenance. Please stay tuned to @BungieHelp for updates.

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
  • Edited by scrylite: 11/21/2014 4:08:47 AM
    Ok... First of all start with your connection device. Is it a RAW modem or a combo (modem/router) unit? If it's a RAW modem then try connecting only your Xbox directly to the modem and be certain it's getting a public IP, not a 192.168 number. This will at least allow you to isolate your own stand alone router as a culprit if you maintain connection fine. If you have a combo unit (modem/router) you need to put it into bridged mode and go buy a decent router that supports UPNP and preferably DD-WRT firmware which you can google. I'd recommend Linksys/Cisco E1200 unit. if you can't afford a router or won't buy one, then unfortunately your at the whim of the crappy device combo your ISP gave you. The problem with using these devices is that typically they are running some modified version of firmware that either removes options, disables them or worse makes them irrelevant given that most use a script upon boot from your ISP to designate all the settings back to what they want them as. One other thing to check is that you disabled port scan detection and ip flood detection. Also do not use UPNP, DMZ, and port forwarding together. It's one or the other not all three. Also many routers prefer that you use DHCP rather than static with services like UPNP and port forwarding but be sure that you reserve a static IP through DHCP reservation tables (done by MAC address; this is also on the router usually in "advanced or routing section). This is a way of ensuring a static IP while maintaining transparency to the gateway through the DHCP server of the router. Many devices if given a static IP on said device will not be seen by the router in UPNP SERVIces. One final note be sure your home network is on IPv4 protocol unless you have some significant reason to use IPv6. It should work regardless but in my personal experiences I've run it to many anomalies with the tunneling from ipv4 to ipv6. If you personally want some assistance or have a question regarding networking the Xbox feel free to send me a message in Live!.

    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
    1 2
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon