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
  • Edited by Mud Turkey 3: 9/15/2014 9:34:29 PM
    Still having the problem Bees most of the time with some Lion and Centipedes mixed. Sometimes Vulture will follow up a Bee kick when I'm in a fireteam. Xbox 1 NAT - Open Ports - Open Internet - DSL Connect - Directly to router Pack loss/ping - B I find a couple things odd. I still get centipede although rarely. Those ports are open. I've tested many of them using port scans and that sort of thing. Other strangeness. The way the error actually works. In PVP, I can almost always play 2/3 of a match before the drop. If it were network limatations or a normal networking error, why would I be able to play for that long? Shouldn't a major error prevent play, period? Why does it work for a while and then flame out? Strikes are typically stable. I've only been dropped from those a handful of time and mostly at the start. When you're in areas with lots of other people. Overworld questing is typically stable until I run into a zone with lots of people connecting. It doesn't always drop but this seems to be the main scenario that causes it. Tower. The Tower is weird. Sometimes it crashes right off the bat. Other times, not at all. I have noticed that sometimes while interacting with vendors I get lag and then the contact servers. It typically resolves itself but sometimes Bees me out. I do not have a blazing connecting. I live in the mountains and there's no cable or wifi options. Just baisc DSL. I've run lots of other games with maybe some occasional lag or ping problems but never any stability problems. This game's errors bother me because one moment everything is fine and the next it is an instant boot. So annoying.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

1 2
You are not allowed to view this content.
;
preload icon
preload icon
preload icon