{{
`${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.
-
PS4 - wired connection - ports forwarded - DMZ on - NAT 2 ( I can't get NAT 1 due to my provider) - works just fine with other games I keep gettin kicked off the crucible matches (sometimes at the beginning, sometimes I managed to play more than half of the match). I rarely incur the Bee error code in the tower, too. Otherwise I never got connection issues in the other modes (story, strike etc.). The most frustating thing is that I had all those problems playing the beta, both on PS4 and Xbox One console.
-
I've been counting ever since I noticed the disconnects becoming noticeably frequent on launch night... I've had 56 disconnects ranging from bee, fly, lion, baboon, centipede, etc. since the midnight launch. I've tried all suggested fixes. My info: PS4 Wifi NAT 2 Ports open
-
Have tried wired & wifi but keep getting bee error either way. My NAT is open, my internet is fine, my ping is good etc.Have had other animals but it's mainly bee. Only have issues in crucible so far it seems in either Control or the Team Deathmatch (Clash?) games. On Xbox One but I did play a lot multiplayer of the beta on my PS4 without a hint of a problem. I can play all my other games fine online and there is no lag when I can actually play. Problem seems to be getting worse as well it used to be the odd game but now it's in pretty much every game I play. Sort it out Bungie. I have to say with all of these stupid animal names for errors it's like they were anticipating this. From Halo multiplayer to this? What a joke!
-
1 ReplyEdited by Eralev: 9/11/2014 7:34:13 AMXbox One - Wired Connection - Open NAT - Port Forwarded - Static IP Playing online since 2006, no problem until Destiny. Same issue here.
-
I have a PS4 and can't seem to stay in a mission for more than 7 mins. I have NAT type 2 or whatever but apparently people are getting the #bee error even with open NATs... Really hoping that these problems get solved soon.
-
Ps4-wired-forward-open
-
i have the same problem .. what i have to do ? my nat is ALWAYS OPEN
-
1 Replyxone - cable ethernet - nat open I have the prbolem only in cruciable
-
Exactly the same. Xbox one, open NAT, ports forwarded, runs all other games eg titanfall with no lag. I'm fine everywhere but the crucible. 30 seconds to 2 minutes in I get booted
-
Yeah I'm on Xbox One and I can barely complete a pvp match. Half way through the game I just get disconnected with the "bee" error. Yesterday I even got kicked out of the tower with the "beetle" error. This is really aggravating and my NAT is open. I have tried to port forward but I am struggling to do so. If anyone could help me out with port forwarding that would be great. I have a NETGEAR.
-
1 ReplyEdited by Kodax: 9/11/2014 3:58:00 AMYep I'm constantly getting disconnected on my ps3, 5-10 minutes and I'm kicked off :(
-
PS4. Wired connection like 2 feet away from the router. Static IP. Ports forwarded. Getting Bee and Fly error codes every 5-10 minutes. Pretty much unplayable. Haven't been able to complete the first mission.
-
5 Repliesseconded, same thing, i got the game on demand, if that means anything
-
Xbox one. Wired connection, open nat and ports forwarded for Xbox live and destiny recommended ports. I get the error after 2-3 mins in tower and crucible. Everywhere else is fine I also lag on my mic terribly supposdly when I enter those areas according to my friends.
-
Xbox 1 ,open nat , wireless , fast internet , no lag in crucible yet get disconnected randomly with error bee , other instances where I get error code bee: tower and occasionally when I'm in orbit for more than 10 minutes
-
Edited by Enzan: 9/11/2014 6:57:48 AMJust adding mine to the list. PS4, I started with wireless, and then bought a 50ft Ethernet cable to connect my router to my PS4(In a room down the hallway where the router is), and got it some more. I got "lion" once or twice as well. Seems to go on once every 30 minutes. Oh, and I'm with ports forwarded like they said, open nat, and I don't have any issues on BF4, and DCUO.
-
I'm also getting it. Ps4 wired connection, open NAT, and my internet works fine in every other game.
-
2 Replies[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] I get it every mission at least three times
-
Xbone, open Nat, Wired, works in any other game.
-
Edited by iQuINcEy: 9/11/2014 2:02:44 PMYup same here, only in pvp tho, like every game! Was worried it was my connection but don't normally have issues. Moderate nat, wired x1 Please fix ASAP edit* ported and now have open nat but same probs
-
Well I believe they are adding servers or fixing bugs as I went from 1 minuet of access to 10 to 30 to long enough to complete one whole level. No changes on my side just reboot after the boot me or reboot their server
-
Was playing fine all day yesterday and today on Xbox One. Around 11:30pm I started getting kicked out and getting different error codes. One was "lion" and last one was "bee". All I was doing were bounty missions. Get maybe 3 minutes into it before it kicks me out. My internet is working fine. No other games affected.
-
averages about 3 times per hour; 3 times tonight on the Moon Home network; Murfreesboro TN IrwinFl3tch3r / smrkngrvnge Comcast Linksys Router / Motorola Modem ping 47 ms and 4 ms jitter
-
1 ReplyMaybe Bungie or Activision better get their business in order with some internet providers. The problems is not on my end. It's probably on theirs. Some server issues. Incompatibility issues?
-
Just got it for the first time here. Only had about 3 errors so far in 16.5 hours of play. PS3 with wireless FiOS here.
-
1 ReplyI 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
