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.
-
I am on a PS3 and every time I go on any mission be it the earth, moon, or venus i get kicked out after 5 min. always error bee. I have reset my router multiple times and tested other games and video services. same problem
-
-
I was getting constant disconnects on my ps4. Luckily my roommate has one too and is away on vacation, so I decided to try it out on his ps4. I have not encountered and issue yet on his system, Granted his is in the living room (where the router is) and mine is in my room upstairs but we have an excellent router with 65+ dl nat open. I don't know what the issue is. Debating on reformatting my ps4 to see if that works because using his system is not a long term fix.
-
I only get the bee and lion error codes my connection strength is one hundred percent and my other games connect to online no problem so it must be the servers
-
I'm getting it the bee about 99% of the time. My console is connected to a wireless router, I dont get connection issues with my other games, my NAT is Open, so I know it's not on my end.
-
Looks like they found a little error as things got a little better. Still getting booted in five minuets but that beats 1 minuet. Now new codes like lion. Sucks!!
-
yeah man i keep getting the bee error. cant play coop or mp without getting kicked. bungie says i have to mess with my router settings. ive never had to mess with router settings to play a game. this is bs. im type 2 nat. Hulk is getting angry
-
i keep getting error codes first it was beaver, now its bee i even got one called mullbery i belive i thought it was just me but glad to see its not!
-
same gig. PS3, bee error everywhere. followed the networking guide and got rid of the centipede issue, now it's all bee.
-
This is all Bullshit!!! My system worked perfectly until the Destiny servers could not keep up with traffic. I have checked my speed, I have checked my access. I can track all users on my network. The problem is not my device or my connection. It is The Destiny servers or their software glitch. It is like Obama Care all over again!!!. If this keeps up, I am contacting my credit card company and requesting a full refund.
-
Not just bee I get a plethora I've tried all of the fixes and none have worked. Destiny why have you forsaken us
-
I seem to be getting plagued by the Bee error now, specifically. Crucible matches without getting it are few and far between, very rare that I can actually complete a match. Beta ran pretty damn well, other games run with my net fine, but for some reason it's acting up with Destiny now? Pretty weird.
-
I get the bee error every time I'm in a mission. If I'm on patrol I tend to get lion. At most I get 45 minutes of uninterrupted play. Because of check pointing the error is not game breaking for story missions, though it can be infuriating when it happens after less than a minute. However, it completely prevents me from finishing strikes, and most pvp matches. It may be a result of my isp (not my router) blocking certain ports, and I'm talking to them about fixing that. However, this is the only game I've ever had this sort of issue with, and it feels like if there is any hiccup in the connection the game just boots me. I guess it means I never see any lag, but I'd rather a stutter and death on my end than an instant disconnect. This would be so much better if the game allowed you to rejoin whatever group or match you were just in! For me, this would be the best change Bungie could make to the game.
-
[quote]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.[/quote] Exactly the same as you op. Also given my xbox a static ip and that didn't work.
-
Xbox one and Bee error.. Mi aggiungo anche io alla lista.. :-(
-
Edited by delapug: 9/11/2014 12:55:18 AMJust now started getting it going to the tower. It's getting worse lol instead of better. Omg we can hardly play the game and they're tweeting about adjusting your sound for the best experience.
-
Edited by Dariosniper: 9/11/2014 12:50:36 AMI have xbox one with wired connection And open Nat But i have error bee :-(
-
bee error.. I'm italian and for first I tought was a problem of my router because my nat is not open. But i play every game with no problem and open the nat problably doesn't solve this problem. Bungie can sell a game, that the gamers can't play, sorry 4 the bad english
-
I was getting the fly error for awhile yesterday but last night it was constantly a bee And this only happend when I was doing missions except one in the tower and it was every 5 mins on the moon. PS3 btw [spoiler]sorry about the long post[/spoiler]
-
Edited by Blue marksmen: 9/11/2014 12:16:56 AMI'll break the mold, since everyone seems to be having crucible problems, I'm getting them during a mission. I'm getting a Bee error EVERY. SINGLE. TIME. I try to play the endless steps mission on Venus (the idea of an entire planet getting turned into a machine sounds more ridiculous each time). I have played other strikes. Other strikes on Venus (every other strike in fact). It only happens here. I have rebooted my PS4. I have deleted and Re-installed Destiny. It still happens every time. Here is the really weird thing: it seems to be tied to a specific location. At the point where you reach the non-baryonic mater stream or whatever, and deploy your ghost. I also got it while trying to do the vex sacrifices public event. I did not try to activate my ghost. A side note, this is also the place where I always pass another player or two. So, possibly this also is a part of the problem. Yesterday I had smooth playing, alone, with friends, in a fire team, etc. Although my PS4's wireless problems reared there head a couple of times, this can't be the same things, since those seemed random, and this has consistent, reproducible behavior. I've gotten the "Bee" error 4 times now, and the "Centipede" error twice. All in the same small area. I'm on a PS4, connected over WiFi, my NAT type is 2.
-
Can't finish the Devils Lair because of it. Constantly kicks me out during the mission.
-
Ye I've been getting this error "bee". I have an open NAT and a wired connection and have been kicked out of my last 20 crucible games. I gave and tried to play a mission but I lost connection to that too.... There's no word to describe my frustration right now
-
Yep multiple times among other errors, this should have been hashed out long ago.
-
Ditto making me want to quit before I've even started good job bungie.
-
Inb4 a mentor posts that useless networking guide again.
-
Same here, although xbox is in the DMZ. Only getting the error in the crucible games really though, rarely in the tower, never in story missions or strikes.