JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by delapug: 9/12/2014 10:33:01 PM
308

Could everyone getting bee error post in here

Please if you're getting this error post in this topic. No stupid remarks about get better internet or other childish remarks. I'll start off. Xbox one - wired connection - ports forwarded - open nat - no problems on any other game. [u]UPDATE[/u] I don't want to be the one to say this but I went and bought a new modem/router(DSL) just plugged it in and no errors for the past 5 hours in the pvp which I couldn't play at all before. Don't know if that means anything but it seems to have taken care of me. [u]UPDATE 2[/u] I've been asked a few questions so I thought I'd do another update with my settings I switched from a netgear combo unit supplied by my isp to an Actiontec GT784WN wireless N DSL Modem. Like I said when I first hooked it up I just made sure plug and play was enabled on the router and started up the xbox and destiny I went straight to the crucible and began playing and haven't stopped since, no more errors at all the only problem was that my nat type was strict. To fix that I forwarded the following ports Port 88 (UDP) Port 3074 (UDP and TCP) Port 53 (UDP and TCP) Port 80 (TCP) Port 500 (UDP) UDP Port 3544 (UDP) UDP Port 4500 (UDP) Port 3075 (UDP and TCP) *for call of duty Ports 7500-17899 (TCP)*from bungie Ports 30000-40399 (TCP)*from bungie Ports 35000-35099 (UDP)*from bungie I now have an open nat and no more errors and even though I suck I can play PvP. I really hope this helps this is exactly what I have done, I compared the settings on each modem/router and other than a few years difference in manufacturing there was no difference.
English
#Help #Error #bee

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
  • I have exactly the same problems. Xbox One, open NAT, ports forwarded, runs all other games without any problems. I'm fine everywhere but the tower or the crucible. Right when I get there or after 2-5 minutes I get booted all the time. Couldn't even one match. Only this 3vs3 modes work. Allready switched from WiFi to ethernet cable.. but I surely wont buy a new router/modem for Destiny. As I said.. every other game works perfectly with my internet connection. There are no lags, no disconnects.. everything is fine. Only Destiny gives me these wonderfull disconnects all the time. If this is not going to be fixed I consider Destiny as a waste of money. I also consider this: http://www.bungie.net/en/Help/Article/11791 as a slap in my face. All I read there is "you are on your own, customer.. thank you for your time and money :P". When they at least post something like "we are looking into this issues" everything would be okay. But all I could find was "Error Code BEE: Bee is caused by packet loss or disconnections between your connection and Bungie. It can be caused by certain wifi setups. It can also be caused by general disconnections between you and the various routes your traffic takes across the internet to get to Bungie. If you hit this frequently, please follow the suggestions at http://bungie.net/networking".. and this starts making me angry.

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