Can’t fully login. Screen stuck on “Battle.net Update Agent went to sleep. Attempting to wake up.” Friend list stuck on loading. This is instantly fixed with a VPN…
I only seem to be able to login to Battlenet and play with the use of a VPN. Few days ago I could login in, but would get the lag spikes of 3k-5k ms like others with East Coast Verizon Fios. (also fixed with VPN)
Now if i start WoW.exe itself, i get a Critical Error/Fatal Condition with “unable to establish signaling pipe” “Error 134 (0x85100086)”. VPN again solves this.
Do I need to reinstall Battlenet? Is this strictly a FioS ISP routing isssue?
Looking Glass for Battle.net Authentication:
TRACEROUTE:
1 Blizzard Blizzard 0.410 ms 0.400 ms 0.397 ms
2 24.105.18.130 (24.105.18.130) 0.850 ms 0.938 ms 1.124 ms
3 137.221.105.10 (137.221.105.10) 1.103 ms 1.107 ms 1.106 ms
4 137.221.66.20 (137.221.66.20) 0.893 ms 0.898 ms 0.897 ms
5 137.221.83.84 (137.221.83.84) 845.734 ms 845.767 ms 845.766 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.199 ms 6.076 ms 6.426 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.871 ms 5.878 ms 5.868 ms
9 ae-2-3601.edge7.LosAngeles1.Level3.net (4.69.219.45) 5.949 ms 5.957 ms 5.929 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 6.316 ms 6.304 ms 6.283 ms
11 ae199-21.NYCMNY-VFTTP-362.verizon-gni.net (100.41.23.125) 62.408 ms 62.426 ms 62.380 ms
12 * * *
13 * * *
14 * * *
15 * * *
03/01/2022 13:48:36 UTC
--------------------
So, now sometimes Battle.net opens.
Without VPN:
WoW - Critical Error/Fatal Condition with “unable to establish signaling pipe” “Error 134 (0x85100086)”.
Overwatch - perfectly fine. Can play multiplayer no issues.
With VPN:
Both are fine.
How can it be that Overwatch is fine but WoW gives an error? I’ve done a full reinstall of WoW, completely fresh.
Also, Battle.net fails to load most times without a VPN.
I actually just figured it out. It was some sort of weird behavior from a new VPN feature.
Some VPN’s have been rolling out this “tunnel feature” for separating which programs get the tunnel and which don’t. When Verizon FIOS was performing badly for a few days with the routing, I put Bnet and WoW into the VPN tunnel; but I had no idea this would mess with settings when the vpn program was closed. This is PIA VPN btw. So, when it was closed/edited to include Bnet/WoW into tunnel, it must have been editing something (firewall?) to block WoW completely and get in the way of Bnet. Probably related to a “kill-switch” I usually run on VPN’s. I just never expected it to influence programs when it’s completely off/not running the application. So either it’s making a registry edit/firewall rule/running service.
I’d delete this, but maybe there is that 1 in a million chance someone did the same thing and reads this. =) Probably not though.