Thats not helpful at all. There are lot of people having this issue. If your not move on... dont troll. My connection is fine so bugger off fool.

I help people that will accept help. I do it all the time. If you're not willing to accept responsibility to do everything on your end, then there's no helping you. Good luck.

Wtf you idiot. I have done everyrhing hence my post its helping those that have the issue. All ur doing is trolling and telling me i havent check my details. Stop being a troll and move on.

Think you are missing something though...you apparently have a stability issue somewhere in the route, otherwise you wouldn't be getting dropped. It can also be the source of your previous time-outs as well. You can have up to a dozen or more hops between yourself and any other host on the internet...be that a server or another player (players act as hosts for this game, not actual servers). Any one of those hops can be a potential point of error---or failure. It needs to be flushed out...especially when it is only affecting a small segment of the users. Could be local, could be elsewhere in your state/country---or one, two...six hops over. You simply don't know for certain until is it checked out. All we can know for certain is there is something uniquely different with your routing that is different than others. Verify you are configured properly on your end. That means using a wired connection for your console, and only ONE approach to opening/forwarding traffic to your console: Either direct connect/DMZ, UPnP, or manually port forwarding the entire range of potentially needed ports to your console. Not a mix of those methods---only one should be in play. Mixing things up can create problems. As stated in their guides...UPnP should be all that is needed...and it is in fact the method you need to use with multiple consoles in play. Should be noted that some consoles may actually have an option in their network configuration for enabling UPnP--may not see it unless you manually configure your connection, and when doing that you need to bind that address in your router's DHCP tables or you may cause a conflict on your local network. Ideally you should be doing this anyway, as it allows you to set specific DNS server address in your console's configuration--otherwise you might be querying your router for DNS, which can be problematic for consoles. Slow/unstable DNS has been a problem for consoles for nearly a decade now. You may even need to disable IPv6 on your router, as it isn't implemented very well in some environments and you may need to reclaim some resources by disabling it. Once you have confirmed you are configured properly on your end, then you need to bring your ISP's Tier3 team on board to monitor data as you are having issues. With any luck they may capture an exception that will allow them to escalate it to the proper party for further investigation. You would be surprised how many times those guys find issues upstream that either they can address internally or with their peering partners.

Omg seriosuly ive done all this i wouldnt be posting here if i havent stop treating me like an idiot that im not. Bungie fanboys. If you havent been there before go read reddit there are numerous post about these issues. I know there are peer to peer issues. My main point here is the -blam!-ing boar errors for missing dlc ffs. The other errors are most likely network related but the boar errors and missing dlc are NOT !!! People consistantly replying saying oh it must be your connection and not knowing what the -blam!- i or other people have already done are not helping the issue. To say that destiny has no Network related issues is being blind and a -blam!-ing Bungie Fan Boy. The point of my post are to try and help other fix the -blam!-ing boar errors. As for the other errors they arent all the time and can live with it. My fix for boar errors works ive not had the error sonce removing the addtional useless dlc so if you and anyone else cant see that i dont care. You probably dont have 8-9 different dlcs as i and others do being a year 1 player. So shut ya -blam!-ing mouth and move the -blam!- on... Last post this forum is bullshit anyways too many trolls and fukheads that think exactly the same as bungie and refuse to admit there is soem serious network related issues at there end.

Dude... you need to relax a bit. You have posted nothing in here about what you have tried. was just glossing over a few of the general, more obvious things that could be in play. Some of which can and often will contribute to instability that causes you to get timeouts. If your sessions were responsive and stable enough, verifying 8 or 9 DLC codes would not time out. You are talking about raw text strings that easily fit inside a single packet of data with a 1500 byte MTU setting. The fact that it is not happening to EVERYONE is an indicator there may be something specific to your sessions that may be an issue. That applies to your Boar as well as any network related error. There are plenty of people not getting them, so there is obviously something amiss somewhere. We have to start somewhere to investigate what that something may be. Start with the known knowns, look for the known unknowns, and then you can start speculating about the unknown possibilities. All I was doing was trying o give some guidance on where to start. Not usually a good idea to jump down the throat of someone trying to help you resolve your problems with instability across the internet. Have you tried disabling IPv6? Have you researched your router's features for things like Secure NAT, FAST-NAT, Nat Acceleration, etc. to see if there are options you may be able to toggle? Have you made yourself pingable and run tests from remote locations to guage localized stability issues? Have you monitored signal and noise levels within your modem's admin pages to see if there may be some signalling issues in play? Or has your ISP monitored this data? Have you checked all your local connections for signs of wear/corrosion? Have you made sure the contacts are clean and fitments are all tight? Tested to confirm there is no excessive loss at splitters? Or has your ISP checked all this out for you? These kinds of things and more need to be flushed out. ANYTHING...even something as seemingly impossible to be causing problems as a flourescent bulb, a fan, or even your cell phone can cause a problem with your internet. But you have to start going down a list somewhere. If you aren't willing to heed someone's advice about such a list, then that is your problem. Don't go throwing it back on someone who is trying to pass on ideas in case there may be something you missed in your troubleshooting---that you have made no mention of, not even a general run-down of your config was provided...so we basically HAVE to start from scratch.

As i said im done on this forum as the only ever given reason for any issue is that IF YOU HAVE AN ERROR ITS YOUR NETWORK. thats a crock of shit... And my orignal post was to help those with the boar error and what do i get tards telling me to check my network. Again. Same generic bullshit responce. Laters enjoy your error free game you have :)