[u][b]UPDATE[/b] [/u]
Got Bee, Weasel, Fly, and Lion last night. It definitely happens more when there is more action going on in the game or I am in a larger group of players (6v6 or Tower). When checking my "connection" in the roster panel, I almost always have a red connection even if everyone else is green. I went through troubleshooting again with Comcast last night and despite finding nothing wrong through virtual testing, I convinced them to send a tech out to test the wiring between the pole and my building and the building junction and my unit. The appointment is between 5-7pm tomorrow, so I'll expect them to show up at 9pm and be done at Midnight!
English
-
While I wait for Comcast to come do testing, I just wanted to post some additional troubleshooting steps that most people don't realize they should check: Check your downstream signal on your cable modem if you are running Cable if it is out of spec it is likely your in home wiring or the wiring coming into your home. Check for any damaged/passive splitters in line between your ground block and your modem. Check for any equipment that is connected to your cable connection that does not have a three prong plug or is not plugged into a properly grounded surge protector (it is likely using the RG6 as a ground and dirtying up the signal if not). Make sure you have all RG6/RG11 cable if possible between your junction box and your modem. Make sure all hardwired ethernet connections are Cat5e/Cat6 and not Cat5.
-
Edited by Shaaablagoo: 11/25/2014 5:48:40 PM[u][b]FINAL UPDATE[/b][/u] I have been MOSTLY Bee/Fly free since Saturday and can honestly say, without a shadow of a doubt, it was [u][b]NOT[/b][/u] Bungie's fault. Comcast ended up having to replace the node (where the main fiber lines get converted to Coax) for the entire neighborhood to the tune of ~$250,000 in equipment and labor. Once that was done the only time I still get a Bee/Fly is when I am in a fireteam with a fireteam leader who has a "poor" connection to Destiny's servers and they get dc'd. While I do now believe that Bee/Fly is NOT a Bungie issue for the most part, I also believe there are some additional things they can do to help their customers, the entire Destiny gaming community, to have a better experience. 1. During "matchmaking" when guardians are being evaluated, the system should automatically switch the fireteam/strike team leader to the member with the best connection to their servers. I'm not aware of any benefit of being the fireteam leader, but if there is, the likelihood of not getting booted certainly outweighs whatever benefit that is. 2. Better troubleshooting instructions for Bee/Fly and other general networking errors. Frankly, the NAT instructions and port forwarding instructions are great, but for the people who are still getting constant issues, there are better steps to take, that can quickly determine whether there is anything that they can do as an end user, whether they need to get their ISP involved, or whether there is truly nothing they can do. 2a. Troubleshooting for CABLE INTERNET users should include the following FIRST steps before changing any settings in your modem or router: 2aa. Check the actual signal being received by your cable modem. If it is not within spec the customer will need to contact their ISP to have line testing done, possible new lines run, or in my case, maintenance work to their ISP's actual transfer hardware. (http://www.speedguide.net/faq/what-cable-modem-signal-levels-are-considered-good-78) While most ISP's consider -15 to +15 to be in the acceptable range, you really want to be between -7 to +7. My signal was +12 to +15 and after changing the node I am at +7 on all 16 channels. [u][b]To be clear, I am talking about the signal strength coming into your MODEM from your coaxial cable (likely your wall connection), not your WiFi signal from your router.[/b] [/u] 2ab. Use pingtest.net as a baseline to check for packet loss between you and MULTIPLE servers around the country. Even if you are getting a 0% packet loss you should still use your PC's operating system to check for packet loss as well. I am not sure what the application is called in windows, but in MacOS it is called network utilities. Send your ping test to a larger server like google.com or yahoo.com. Make sure you sent AT LEAST 300 ping samples in order to better assess packet loss. If you have a packet loss issue contact your ISP to discuss line/splitter maintenance options as there is likely nothing you can do to your personal modem/router to correct the issue. 2ac. If you have an older cable modem, consider upgrading your modem to a newer unit with a greater number of banded channels. While this won't increase your bandwith (unless you are on VERY fast internet and your current modem is obsolete) it can assist with channeling data through your system, especially if you use other internet connected devices on the same network. 2ad. Begin with the network troubleshooting steps provided by Bungie (http://www.bungie.net/en/Help/Article/11931). Best of luck to everyone!
-
[u] [b]UPDATE[/b][/u] Well it looks like my cable modem was getting a pretty bad single from the pole so Comcast ran a new drop from the pole, and tested my existing in wall wiring which all checked out fine. We got great signal at the modem but when dong a hardwired packet test I still have some packet loss, and I still got dropped with a BEE error from the first strike I tried to play. The next steps are the Comcast "Maintenance" department to come out and work on the actual node on the pole if necessary and replace the actual cable modem. I went out and bought the newest Motorola Surfboard SB6183. I'll be installing that tonight and testing again. If that doesn't work, and the maintenance on the node doesn't work, then frankly, this must be on Bungie's end. I hope that isn't the case!
-
Doesn't hurt to try, well in 2 months