{{
`${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.
-
Tried wired, wireless, opening nat and I've given up. I can't even play it. Really pissed off.
-
1 ReplyXbox One, wired connection, all necessary ports forwarded, open NAT, never had any connection problems with literally any other game. Bee Error every single crucible match I play. Once in awhile during story missions but crucible matches are by far the biggest offender.
-
Couple of youtubers are figuring it out now, One solution is to take off your UDP and TCP flood protection? not sure how you do that Supposdly everything in the game is based off P2P. So people are hugging off each others connections 500 million and were using that system.
-
(Xbox One) Getting same Bee Error, haven't managed to complete a single game on the crucible out of about 20, I can play online with my fireteam in story, but occasionally get disconnects during game or in the tower due to the same Bee Error. Ports are open, triple checked (using BT Homehub). Hope we can have a solution soon!
-
I had this problem in the beta and still do now. Can't finish a single crucible match without disconnecting. I'm playing on the xbox one. Funny thing is I played the beta both on xbox one and 360 and only got disconnected every 5 games or so on 360 but every game when playing on xbox one.
-
Friggan annoying getting bee...
-
Also getting this error. No problems at all with other aspects of the game except PVP, getting this error. Played about 10-12 games so far and haven't played a single one start to finish. My setup and NAT and all of that is perfectly fine/normal.
-
Edited by Bwolf04: 9/11/2014 10:57:05 PMI'm getting the error and did everything, no problems with other games/apps they need to fix this. I want to end at least an effing match without getting bee error :(
-
I get all the error posible i this game baboon,bee,centipede,kingfisher, etc.
-
I got it once earlier today when connected via wireless and shortly after got canary.
-
Haven't been able to finish a single crucible game. always get disconnected half-way through.
-
Same here. I even ran the wired connection and am still getting it. They need to fix this ASAP or I am filing with PSN to get my money back and claim against bungie. New or not, this is unacceptable for a game of this calibre with no solution.
-
I got the same problem. I hope its fixed soon I can't even finish a match of crucible
-
Exact same, xbox one, wired, ports forwarded, open nat, fast internet, never lag just disconnected from EVERY online crucible game with stupid bee error. Whats most annoying is the fact that the exact same thing happened in the beta and it was 'supposedly' reported when it happened and would be fixed for launch, not like bungie to disappoint like this...
-
Tried all kindsa crap. I've recieved just about every error they list. Opened ports, everything. I'm about to move my modem around to try a wired connection.
-
Edited by Coban: 9/11/2014 8:18:45 PMhaving the same problem on ps4, it worked fine when i switched to wifi
-
Edited by Hannibal: 9/11/2014 8:17:35 PMSo since day one 10mins into the game i got a #error #code #bee looked it up on the #Bungie website and due to my Nat Type I can't play for more than 10mins. This #Bee error code is getting old. I've called my internet provider and had my ports open like psn told me to do. Nothing still the same. U would think a 500m dollar game would have better connection then this for there players. I have yet to see any differences in my connection since day one. Come on Bungie I spent 90$ on my game and I can't even play. I get up to 40mbps and I can't even stay connected. Doesn't sign me out just kicks me off what ever I'm playing. I have yet to ever have a connection problem on any other game i've played on my ps4. This is some BS bungie!!
-
I came across this once on ps4 with a wired connection
-
Same: Wireless, open NAT, every other game is fine
-
1 ReplySame here. Open nat. No problems in games like Titanfall or Battlefield 4. 64 player multiplayer works fine. Very, very annoying.
-
I've had this problem on occasion on PS3. My internet is not the best nor is my connection wired. I've gotten lion a few times as well, usually bee though. I've put it down to my internet for the majority, but given people with better connections get disconnects I figured I'd at least post. There's no better ISP in my area so I can't really help that anyway, and destiny has run better than most online games I've played. The fact that it played so smoothly during the beta was a big factor in me buying it at all. It's rare enough that it doesn't really bother me.
-
x1 wired open nat type mostly when in multiplayer but just happened to me on the moon in story mode
-
Up! Cruciabile is unplayble!!
-
1 Reply[quote]"Xbox one - wired connection - ports forwarded - open nat - no problems on any other game"[/quote] Saaaame
-
I'm having the same issue, and have the same setup, Xbox One, with a wired connection. I keep getting kicked out of strikes right before they end and don't get the rewards for beating it. I also get kicked out of free roams very often as well!
