- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So I have everything resolved, except all the port forwarding rules I created were for an IP address that has since fallen off my desktop. I will need to assign it a static IP.
I found a link on fios forums on how to do that so I will try and take care of that later, unless Port Forwarding rules are assigned to the gateway and not the IP address?
I am connected via wireless, I live in a large house and it is impossible to get a physical cable to my room unless it's over 500 feet and blocking doorways and such.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ah, I should have emphasized the need for a static IP for just the reason you found out about. One of those videos mentions it, but only in passing. Most DHCP servers give the same IP to the same device over and over again. I guess the one built into the G1100 is not one that does that. As far as I can tell, port forwarding is set to a specific IP on your internal LAN - that is the PC you are playing the game on.
Wireless QoS settings might help you somewhat though voice chat is such a low bandwidth strain, it really shouldn't make a difference.
You don't happen to have coax running nearby your computer do you? If so, you might consider buying a single Actiontec Bonded MoCA 2.0 Ethernet to Coax Adapter (ECB6200S02). The problem is, I'm not 100% sure that would work with the G1100. It might be the ACTIONTEC Home Theater Coax Network Adapter (ECB3500T01) instead. Or even something else. (There's also an ECB2500, that's similar to the ECB3500, but with only one Ethernet port where the ECB3500 has four.)
I didn't see if your home is provisioned with Ethernet or coax from your ONT to the G1100. The basic idea is that there is already part of the coax frequencies being reserved for Internet data. This data is needed by the STB for the program guide and for VOD.
If I understand it right, for coax provisioned Internet service, you have (only) coax from the ONT to your router. The built-in MoCA adapter in the G1100 separates out the Internet portion that's on the coax signals and delivers that to the LAN ports. The WAN port of the G1100 remains unused.
On the other hand, if you are provisioned for Ethernet, you would have an Ethernet cable from the ONT into your router's WAN port and also, have a coax cable connected (to a splitter combined with the coax coming from the ONT). The ONT still provides all the frequencies used to deliver video, but the portion reserved for Internet signals is left unused at the ONT. In this case, the MoCA adapter on the G1100 is converting the Ethernet signal from the WAN port (which originated from the ONT Ethernet cable) and inserting on the coax at the frequencies reserved for Internet traffic. There are others here in this forum that understand this better than I do and might even know exactly which adapter would do the job.
The proper MoCA adapter should let you use the same frequency range to get Ethernet next to your PC. That's assuming you have coax cable close by and all the coax is connected somewhere in the house.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Blizzard provides a looking glass server which can help troubleshoot the problem some more. Besides tracing from your computer to a Blizzard server, also include the traces/MTRs/Ping results seen from this website: https://us-looking-glass.battle.net/
That should help identify if we also have a bad return route.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Smith6612 wrote:Blizzard provides a looking glass server which can help troubleshoot the problem some more. Besides tracing from your computer to a Blizzard server, also include the traces/MTRs/Ping results seen from this website: https://us-looking-glass.battle.net/
That should help identify if we also have a bad return route.
Thanks, @Smith6612. I wonder how long that Looking Glass server has existed? I never knew about it. I played WoW for many years spread through almost a decade, and I thought I knew all the tricks. BTW, the URL is http://us-looking-glass.battle.net/ (that is http, not https). I get a This site can’t be reached error if I use https.
My results from the WoW Bronzebeard server (my old haunt for most of my characters) for the MTR and traceroute tests (which are very similar) are:
TRACEROUTE: traceroute to 108.44.193.140 (108.44.193.140), 15 hops max, 60 byte packets 1 24.105.30.3 (24.105.30.3) 0.548 ms 0.678 ms 0.733 ms 2 * * * 3 137.221.66.4 (137.221.66.4) 1.271 ms 1.327 ms 1.395 ms 4 137.221.68.72 (137.221.68.72) 1.260 ms 1.281 ms 1.298 ms 5 137.221.68.34 (137.221.68.34) 0.915 ms 0.926 ms 1.117 ms 6 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 0.827 ms 0.826 ms 0.820 ms 7 * * * 8 Verizon-level3-50G.LosAngeles1.Level3.net (4.68.63.246) 0.841 ms 0.842 ms 0.868 ms 9 * * * 10 ae203-0.CLPPVA-VFTTP-304.verizon-gni.net (130.81.221.133) 61.402 ms 61.440 ms 61.338 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 07/01/2018 14:01:39 UTC -------------------- TRACEROUTE: traceroute to 108.44.193.140 (108.44.193.140), 15 hops max, 60 byte packets 1 24.105.30.3 (24.105.30.3) 1.054 ms 1.060 ms 1.079 ms 2 * * * 3 137.221.66.4 (137.221.66.4) 1.164 ms 1.254 ms 1.330 ms 4 137.221.68.72 (137.221.68.72) 1.235 ms 1.263 ms 1.288 ms 5 137.221.68.34 (137.221.68.34) 0.859 ms 1.054 ms 1.068 ms 6 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 0.859 ms 0.834 ms 0.831 ms 7 * * * 8 Verizon-level3-50G.LosAngeles1.Level3.net (4.68.63.246) 0.838 ms 0.844 ms 0.844 ms 9 * * * 10 ae203-0.CLPPVA-VFTTP-304.verizon-gni.net (130.81.221.133) 61.381 ms 61.416 ms 61.415 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 07/01/2018 14:01:39 UTC -------------------- TRACEROUTE: traceroute to 108.44.193.140 (108.44.193.140), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.625 ms 0.726 ms 0.846 ms 2 * * * 3 * * * 4 137.221.69.72 (137.221.69.72) 6.231 ms 6.258 ms 6.279 ms 5 137.221.69.34 (137.221.69.34) 1.737 ms 1.743 ms 1.839 ms 6 xe-11-3-0.edge4.Chicago3.Level3.net (4.53.98.45) 6.399 ms 4.485 ms 4.470 ms 7 MCI-level3-ae.chicago3.level3.net (4.68.110.186) 1.473 ms 1.487 ms 1.497 ms 8 * * * 9 ae203-0.CLPPVA-VFTTP-304.verizon-gni.net (130.81.221.133) 21.048 ms 21.081 ms 21.082 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 07/01/2018 14:01:39 UTC -------------------- TRACEROUTE: traceroute to 108.44.193.140 (108.44.193.140), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.767 ms 0.795 ms 0.848 ms 2 * * * 3 * * * 4 137.221.69.72 (137.221.69.72) 1.921 ms 1.947 ms 1.969 ms 5 137.221.69.34 (137.221.69.34) 1.750 ms 1.761 ms 1.774 ms 6 xe-11-3-0.edge4.Chicago3.Level3.net (4.53.98.45) 1.509 ms 1.533 ms 1.515 ms 7 MCI-level3-ae.chicago3.level3.net (4.68.110.186) 1.439 ms 1.462 ms 1.460 ms 8 * * * 9 ae203-0.CLPPVA-VFTTP-304.verizon-gni.net (130.81.221.133) 21.108 ms 21.144 ms 21.060 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 07/01/2018 14:01:44 UTC -------------------- MTR: Start: Sun Jan 7 14:01:39 2018 HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev 1.|-- 24.105.30.3 0.0% 10 0.7 0.8 0.5 1.7 0.0 2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3.|-- 137.221.66.4 0.0% 10 1.3 1.4 1.3 1.5 0.0 4.|-- 137.221.68.72 0.0% 10 1.4 1.9 1.2 4.8 1.2 5.|-- 137.221.68.34 0.0% 10 1.0 1.0 0.9 1.1 0.0 6.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 1.0 0.9 0.9 1.0 0.0 7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 8.|-- Verizon-level3-50G.LosAngeles1.Level3.net 0.0% 10 0.9 2.5 0.9 16.9 5.0 9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 10.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net 0.0% 10 61.4 63.4 61.4 80.4 6.0 11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 07/01/2018 14:01:39 UTC -------------------- MTR: Start: Sun Jan 7 14:01:39 2018 HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev 1.|-- 24.105.30.3 0.0% 10 0.7 0.8 0.4 1.7 0.0 2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3.|-- 137.221.66.4 0.0% 10 1.3 1.3 1.1 1.6 0.0 4.|-- 137.221.68.72 0.0% 10 1.4 2.0 1.2 4.8 1.2 5.|-- 137.221.68.34 0.0% 10 1.0 1.0 0.9 1.1 0.0 6.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 0.9 0.9 0.8 1.0 0.0 7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 8.|-- Verizon-level3-50G.LosAngeles1.Level3.net 0.0% 10 0.9 2.5 0.8 16.8 5.0 9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 10.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net 0.0% 10 61.4 63.3 61.4 80.4 6.0 11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 07/01/2018 14:01:39 UTC -------------------- MTR: Start: Sun Jan 7 14:01:39 2018 HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev 1.|-- Blizzard 0.0% 10 0.6 0.5 0.5 0.6 0.0 2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 4.|-- 137.221.69.72 0.0% 10 2.2 2.7 2.0 7.3 1.5 5.|-- 137.221.69.34 0.0% 10 1.8 2.2 1.7 5.4 1.1 6.|-- xe-11-3-0.edge4.Chicago3.Level3.net 0.0% 10 1.6 1.6 1.5 1.6 0.0 7.|-- MCI-level3-ae.chicago3.level3.net 0.0% 10 1.5 1.5 1.5 1.5 0.0 8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 9.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net 0.0% 10 21.1 24.2 21.1 51.5 9.6 10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 07/01/2018 14:01:39 UTC -------------------- MTR: Start: Sun Jan 7 14:01:44 2018 HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev 1.|-- Blizzard 0.0% 10 0.6 0.6 0.5 0.6 0.0 2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 4.|-- 137.221.69.72 0.0% 10 1.9 2.6 1.9 7.5 1.7 5.|-- 137.221.69.34 0.0% 10 1.9 1.8 1.8 1.9 0.0 6.|-- xe-11-3-0.edge4.Chicago3.Level3.net 0.0% 10 1.6 1.6 1.5 1.6 0.0 7.|-- MCI-level3-ae.chicago3.level3.net 0.0% 10 1.5 8.2 1.5 68.4 21.2 8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 9.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net 0.0% 10 21.1 24.3 21.1 52.5 9.9 10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 07/01/2018 14:01:43 UTC --------------------
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you find a solution please share it. I'm experiencing the same thing with Heroes of the Storm currently. Horrible lag from packet loss.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm currently experiencing very high latency when trying to connect to or use any Blizzard server, including any of their games or websites.
Apparently this issue is only being reported by Verizon FIOS users on the East coast, specifically in the Maryland/Virginia area
Originally reported about four hours ago.. by a few hundred people in this thread alone:
https://us.battle.net/forums/en/wow/topic/20760937159?page=1
Or if you dont want to use my link you can find the thread by going to:
WoW Forums -> Technical Support -> Connection issues 1/20/2018
This isn't listed as an outage or issue anywhere I can find on the FIOS site, and the fact that it's gone on for so many hours is concerning.. a large reason I pay for FIOS is for the reliable and fast connection to be able to play Blizzard games.
If I can expect service degredation this bad for periods of time this long, I'll have to move on to a different internet provider.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For the past few hours, there have been massive reports on Blizzard forums about disconnects on the east coast for FiOS customers. I have experienced this as well, and it's very random!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Blizzard games are currently crashing for many, many verizon internet users in the eastern united states. Blizzard says this is not on their end, and we need to compain to you all to fix it. Please fix it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am experiencing the same thing in the Buffalo, NY area. My Fios speed test is right at my max speed (150/150Mbps), but Blizzard games like World of Warcraft have latencies over 1000 (also causing disconnects).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This problem has reoccurred 01/21/2017 at approximately 10:30AM EST.
When I run the Blizzard Battle.net Looking Glass tool, it's showing 20% to 40% packet loss rates for the last 2 hops to me.
Those routers are:
ae203-0.WASHDC-VFTTP-309.verizon-gni.net 20.0%
pool-108-31-123-14.washdc.fios.verizon.net 40.0%
Please fix these obviously malfunctioning routers.