{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
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.
-
1 ReplyI'm having the same problem as everyone else, I play on Xbox one all ports forwarded wired connection everything that bungie has suggested and still not working. I've been able to play 3v3 with greater success but whenever I try to play 6v6 I always get the bee error. I've been playing games on Xbox live for years and never had a problem this frustrating, I payed over $100 to play this game and can't really enjoy it because I can't play crucible. Bungie needs to fix this problem or at least acknowledge that there is a problem and not blame it on the gamers packet loss.
-
Yep started with zebra now bee it sucks cant have a good go all week
-
Yup I get bee and a whole bunch of others,dont see how they can narrow the problem down if people are getting the entire range of error codes tbh =\
-
Did everything with the ports, my router and connection are great and I even had at&t come out to check. Connection is strong, and all of my other games play flawlessly. It's not my connection to my wifi or anything, it's on your end bungie. Whatever you did last Thursday boned the servers, and you need to fix it.
-
1 ReplyAlright. I was one of the many getting a flux of errors, bee, fly, lion, centipede to name a few and blamed the Bungie/Destiny servers. I tried opening port, creating a static IP. As I was doing more to help the issue, more connection errors would start showing up and more often. Decided to turn off every wireless item that connects to my router just to test, reset all my changes to my normal settings and was able to enjoy hours of gaming without connection issues. I then started to turn items on 1 by 1 and notice as soon as I turned on my main PC, I started getting disconnected again. I switched from wireless to LAN cable, turned off my wireless connection from the main PC and BAM, able to enjoy hours of Destiny without errors. So set your settings back to normal and disconnect wireless items from your router. It fixed my issues, hope it fixes yours.
-
1 ReplyEdited by Mud Turkey 3: 9/21/2014 6:20:32 AMSo for three consecutive strike missions tonight, I've been Bee'd during the boss fights. I was unable to complete a single one today. My internal router diagnostics are reporting very minimal packet errors. I reset my router an hour ago. I've had 4 bee hours in this span. My router is not reporting a single drop or packet error out of close to 100,000 packet sents. *So note this please* The packet loss is minimal to zero. I have recieved the bee error 3 or 4 times in this span. I don't deny that packet loss could cause this error -- as you folks assert. But why am I getting it constantly with minimal to zero packet loss on a fuly open nat and forwarded ports on a private network? Things have been WAY worse since the first patch too.
-
7 RepliesIt's totally unreal and frustrating. Only game in the WORLD that does that. Now, I think it's time to get real and admit that this game is BROKEN. When you think about it, it might be the biggest modern gaming flop. Whorse than GTA5 on launch. And we're not given a single word on the topic. NOT. A. SINGLE. WORD.
-
Bee errors, sometimes one of the other animals. Totally random intervals and times, but it seems like they occur more often in the afternoon (when more people are online probably). Didn't have one disconnect for the first week after launch. Tried everything: NAT is open, reboot modem, disconnected all other devices, but no success. Common Bungie, you did create the best gaming franchise of all time, but I'm rapidly losing respect for you guys.
-
1 ReplyDear Bungie, NTS Internet users are now approaching one week of not being able to access Destiny due to the Cattle error on the sign in screen. Could you please provide some feedback as to where you and NTS are in the process of solving this issue? Most, if not all, of the people affected by this bug are beyond the point of frustration with this situation. I believe the ultimate fix to this problem resides in your hands at this point. If that is not the case, I apologize. Every aspect of my internet service works fine except for Destiny. That includes other online games. I know you deal with many, many problems each day, but I implore you to take some time and resolve this issue. It would seem to me that errors like this would take priority over whether or not somebody can see their ship, or similar cosmetic bugs like this. At least those people are in the game playing. Those of us with the Cattle error cannot even access the game to play! Please make this issue a TOP priority if it is not already. I have no way of knowing if it is being worked on due to the lack of information you are providing. Your attention to this important function will be much appreciated!
-
1 ReplyStill getting BEE 24/7. DC'd every 5 minutes when in the crucible. All other games are fine, just destiny losing connection. This sucks.
-
I just wanted to offer my update. I am now able to play the Crucible with no lag, warning signs or disconnects. Thank you once again Bungie, now if you'll excuse me, I have some catching up to do.
-
Anyone else unable to sign into play station network?
-
3 RepliesOk i've been having the same problem as everyone else mainly with anything thats 6v6 pvp... Is anyone here in the uk with ISP BT? my friend lives very close has no issues and has the same set up only difference is sip's...
-
1 ReplyFor some reason I'm getting booted out a LOT on my current play session. Which I'm doing the story and getting that bee error. It's pretty frustrating.
-
Edited by Mustard Tiger: 9/20/2014 10:02:49 PMSame problem Bee error. NAT is open and all ports are forwarded. I was fine just until recently, two days ago I get a bee error and I can`t get through a raid or a pvp match. Thanks so much Bungie. Every time Activision joins a company, it somehow turns to SHT. I hate you Activision. Somehow I blame you for this and Bungie read your damn forums and give us at least something to go by. Are you trying to fix the problem or are you just not going to address this? I would like to know if I should wait or just sell my game off and get some money back you a$$holes. Talk to your fans Bungie! We made you! Without us you would be nothing. Right now your giving yourself a very bad reputation. Look what happened to EA. Keep this type of stuff up and you will find yourself in the same boat. Bad enough I see that you already show us that you have two expansion packs for this game before you even released it. Way to send out a unpolished small version of a game so you can exploit your buyers into giving you more money. This has Activisions greedy hands all over it. I cannot wait for the 50 dlc's I'll have to buy for this. You sold out big time. I'm only so angry because you where a company I looked up to before this.
-
Add me to the list. I've followed every piece of advice Xbox Live support has given me. Even they are probably getting frustrated and stumped. It's getting ridiculous. Tried everything. NAT is open, Xbox is DMZ. Nothing else to try. Bungie obviously doesn't care.
-
1 ReplyI have been fine since launch and today which is sept 20th, I can not stay in a pvp match more than half a game then I get booted. My nat is open and all test prove my internet is running smooth. Very little support with Bungie, it is not our fault, if other games didn't run then I might think something was wrong, but just this game. They have their money now, part given to shitvision and now they don't care, on to the expansions.
-
Ports open, Still getting the bee. Unreal. Brutal
-
-
This sucks. I am beed off.
-
Edited by Magyman: 9/21/2014 6:38:57 AMBought it about a week ago, just started getting booted about 24 hours ago. Everyone in a while I can play a short mission or a PvP match, but it's rare.
-
Had no probably im beta. But I get bee...caterpillar...and some other c bug everyday all day. Its a lil ridiculous yall know? ISP is ok. Ports forwarded. Nat type open. No packet loss. Yet I cant play half of this get cause of disconnects. I love the game but damnit I wanna play it to
-
I get bee 24/7 I can never finish a crucible match or strike.
-
I've been playing since launch day (almost two weeks now), and I haven't had a single problem aside from one disconnect about 3 days after release. It was a no name error that kicked me to my ship. I restarted the match, and everything has been fine up until yesterday. Then, I started getting Cattle errors for about a half hour or so, and I couldn't even log in. That seemed to have fixed itself after a couple hours, and then I played for maybe 4 straight hours that night after I got off work, along with the 2 or 3 I played after the Cattle errors subsided before I had to go to work. I thought I was in the clear. Oh, how wrong I was. Now, I'm getting the Bee error after about 10 minutes into a strike. It's really aggravating. I would say that it was on my end if this had been happening from the start, but I've been playing nearly everyday for at least a few hours for nearly two full weeks. If it's on my end, how could this just start happening now? Nothing has changed in my home network between then and now. Even the beta ran just fine for me. I had maybe two or three disconnects the whole time I played, and that was a beta. Now, I've played nearly flawlessly for almost two weeks on the full game (which I've been enjoying), and it's going to choose now to start giving me issues? Just to add insult to injury, I'm actually off on a weekend, and I have all day to do whatever I want. Well, I guess it's not going to be playing Destiny.
-
What I ended up doing is just moving my modem and router out to the living room where my PS4 is and hardwiring my PS4 directly to the router. Ever since that I've had minimal issues.
-
Get bee error, can't finish a crucible match, so bad
