无法登录暴雪游戏平台登不了

暴雪游戏平台无法启动,求助_百度知道
暴雪游戏平台无法启动,求助
我有更好的答案
选择管理模板-网络-Qos数据包计划程序,选择后在右侧的窗口选择限制可保留带宽选项,调出组策略进行设置,双击。启动类型设置成手动,然后下面的服务状态停止掉点确认,就OK了,并将带宽限制将默认设置的20更改为0。方法2:打开搜索运行(WIN键+R)输入services。系统保留网速设置,运行的对话框方法1:打开360安全卫士,工具里,打开修复lsp,然后立即修复,在输入文字的位置,输入命令gpedit.msc.msc找到WINDOWS FIREWALL,将未配置的选择更改成已启用
采纳率:97%
来自团队:
为您推荐:
其他类似问题
您可能关注的内容
换一换
回答问题,赢新手礼包
个人、企业类
违法有害信息,请在下方选择后提交
色情、暴力
我们会通过消息、邮箱等方式尽快将举报结果通知您。您当前所在位置: →
导读:守望先锋与游戏服务器失去连接,显示我们无法让你登录战网,很多玩家都不知道吧,就让小编我来告诉你们吧。很多玩家点进入游戏蓝色按钮之后,守望先锋与游戏服务器失去连接...
守望先锋与游戏服务器失去连接,显示我们无法让你登录战网,很多玩家都不知道吧,就让小编我来告诉你们吧。很多玩家点进入游戏蓝色按钮之后,守望先锋与游戏服务器失去连接 显示我们无法让你登录战网,这个其实是因为启动失败的缘故,启动失败有很多可能性,玩家可以更新一下自己的显卡驱动,看看是不是最新的,然后关掉杀毒软件和防火墙,可能防火墙会阻止守望先锋启动。以上就是守望先锋与游戏服务器失去连接 显示我们无法让你登录战网的原因介绍了,希望能够帮助到大家。
文章很赞,分享给朋友
6-106-96-96-96-96-96-75-285-275-24请完成以下验证码
暴雪游戏登录战网提示无法连接服务器解决方法
查看: 8300|
评论: 0|原作者: 游戏小哥
问题现象:暴雪游戏登录战网提示无法连接服务器问题截图:使用工具:网易UU加速器路径指向:易乐游处理的暴雪游戏都是将游戏目录映射到C盘根目录下的,一般以游戏首字母缩写命名,这次演示的为守望先锋,所以在C盘下 ...
问题现象:暴雪游戏登录战网提示无法连接服务器问题截图:使用工具:网易UU加速器路径指向:易乐游处理的暴雪游戏都是将游戏目录映射到C盘根目录下的,一般以游戏首字母缩写命名,这次演示的为守望先锋,所以在C盘下面可以看到SWXF这个文件夹,这个就是守望先锋在C盘的映射目录,游戏执行程序直接指定这个文件夹即可。 解决方法:使用网易UU加速器对游戏执行程序进行加速,然后通过UU加速器启动游戏登录战网就OK了。 PS:目前测试发现网易UU加速器针对暴雪游戏加速效果是最好的,也许是网易暴雪一家亲原因,这个方法屡试不爽,各位童鞋可以尝试一下。
刚表态过的朋友 ()
上一篇:下一篇:
内存价格暴涨近2年后如今没货也降价!《绝地求生》正式版更新慢的解决办法 瞬间SSD 120G杀入200元!国内SSD价格2018年要变腾讯推《绝地求生》官方APP 能绑定Steam查警惕:伪装成破解+去广告,实则连接云端发
Powered by无法登录暴雪游戏平台,无法登录暴雪任何游戏 - 《魔兽世界》论坛
110 德莱尼 圣骑士
TRACEROUTE:traceroute to 202.104.208.46 (202.104.208.46), 15 hops max, 60 byte packets 1
114.113.217.146 (114.113.217.146)
1.012 ms 2
115.238.7.29 (115.238.7.29)
0.604 ms 6
220.191.196.77 (220.191.196.77)
1.426 ms 7
220.191.200.9 (220.191.200.9)
3.382 ms 8
202.97.85.101 (202.97.85.101)
29.135 ms 9
183.57.114.21 (183.57.114.21)
27.675 ms10
218.15.239.234 (218.15.239.234)
30.617 ms11
46.208.104.202.broad.zq.gd..cn (202.104.208.46)
35.696 ms07/04/:53 UTC--------------------TRACEROUTE:traceroute to 202.104.208.46 (202.104.208.46), 15 hops max, 60 byte packets 1
114.113.217.146 (114.113.217.146)
4.262 ms 2
115.238.7.29 (115.238.7.29)
0.712 ms 6
220.191.196.77 (220.191.196.77)
0.811 ms 7
220.191.200.9 (220.191.200.9)
3.459 ms 8
* 202.97.85.101 (202.97.85.101)
30.936 ms * 9
183.57.114.21 (183.57.114.21)
25.990 ms10
218.15.239.234 (218.15.239.234)
30.299 ms11
46.208.104.202.broad.zq.gd..cn (202.104.208.46)
35.736 ms07/04/:53 UTC--------------------TRACEROUTE:traceroute to 202.104.208.46 (202.104.208.46), 15 hops max, 60 byte packets 1
114.113.217.146 (114.113.217.146)
1.328 ms 2
115.238.7.29 (115.238.7.29)
0.578 ms 6
220.191.196.77 (220.191.196.77)
0.665 ms 7
220.191.200.9 (220.191.200.9)
3.577 ms 8
202.97.85.101 (202.97.85.101)
31.293 ms 9
183.57.114.21 (183.57.114.21)
29.072 ms10
218.15.239.234 (218.15.239.234)
30.233 ms11
46.208.104.202.broad.zq.gd..cn (202.104.208.46)
35.850 ms07/04/:55 UTC--------------------PING:PING 202.104.208.46 (202.104.208.46) 56(84) bytes of data.--- 202.104.208.46 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 3005ms07/04/:53 UTC--------------------PING:PING 202.104.208.46 (202.104.208.46) 56(84) bytes of data.--- 202.104.208.46 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 2999ms07/04/:53 UTC--------------------TRACEROUTE:traceroute to 202.104.208.46 (202.104.208.46), 15 hops max, 60 byte packets 1
114.113.217.146 (114.113.217.146)
1.091 ms 2
115.238.7.29 (115.238.7.29)
0.568 ms 6
220.191.196.77 (220.191.196.77)
0.790 ms 7
220.191.200.9 (220.191.200.9)
3.296 ms 8
202.97.85.101 (202.97.85.101)
31.433 ms 9
183.57.114.21 (183.57.114.21)
27.184 ms10
218.15.239.234 (218.15.239.234)
30.331 ms11
46.208.104.202.broad.zq.gd..cn (202.104.208.46)
36.749 ms07/04/:58 UTC--------------------PING:PING 202.104.208.46 (202.104.208.46) 56(84) bytes of data.--- 202.104.208.46 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 2997ms07/04/:58 UTC--------------------PING:PING 202.104.208.46 (202.104.208.46) 56(84) bytes of data.--- 202.104.208.46 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 2998ms07/04/:01 UTC--------------------TRACEROUTE:traceroute to 202.104.208.46 (202.104.208.46), 15 hops max, 60 byte packets 1
114.113.217.130 (114.113.217.130)
1.401 ms 2
115.238.7.5 (115.238.7.5)
0.601 ms 6
220.191.196.77 (220.191.196.77)
0.654 ms 7
220.191.200.1 (220.191.200.1)
3.449 ms 8
202.97.85.117 (202.97.85.117)
24.251 ms 9
183.57.113.21 (183.57.113.21)
29.941 ms10
218.15.239.235 (218.15.239.235)
78.439 ms11
46.208.104.202.broad.zq.gd..cn (202.104.208.46)
30.964 ms07/04/:06 UTC--------------------MTR:Start: Fri Apr
7 07:04:53 2017HOST: Blizzard
Wrst StDev
1.|-- 114.113.217.146
5.|-- 115.238.7.29
6.|-- 220.191.196.77
7.|-- 220.191.200.9
8.|-- 202.97.85.101
9.|-- 183.57.114.21
0.9 10.|-- 218.15.239.234
0.0 11.|-- 46.208.104.202.broad.zq.gd..cn
36.2 107.0
22.307/04/:53 UTC--------------------MTR:Start: Fri Apr
7 07:04:53 2017HOST: Blizzard
Wrst StDev
1.|-- 114.113.217.146
5.|-- 115.238.7.29
6.|-- 220.191.196.77
7.|-- 220.191.200.9
8.|-- 202.97.85.101
9.|-- 183.57.114.21
1.1 10.|-- 218.15.239.234
2.8 11.|-- 46.208.104.202.broad.zq.gd..cn
36.2 107.4
22.407/04/:53 UTC--------------------MTR:Start: Fri Apr
7 07:04:55 2017HOST: Blizzard
Wrst StDev
1.|-- 114.113.217.146
5.|-- 115.238.7.29
6.|-- 220.191.196.77
7.|-- 220.191.200.9
8.|-- 202.97.85.101
9.|-- 183.57.114.21
7.3 10.|-- 218.15.239.234
0.0 11.|-- 46.208.104.202.broad.zq.gd..cn
0.007/04/:55 UTC--------------------TRACEROUTE:traceroute to 202.104.208.46 (202.104.208.46), 15 hops max, 60 byte packets 1
114.113.217.130 (114.113.217.130)
1.921 ms 2
115.238.7.5 (115.238.7.5)
0.594 ms 6
220.191.196.77 (220.191.196.77)
2.234 ms 7
220.191.200.1 (220.191.200.1)
3.324 ms 8
202.97.85.117 (202.97.85.117)
21.527 ms 9
183.57.113.21 (183.57.113.21)
31.029 ms10
218.15.239.235 (218.15.239.235)
35.338 ms11
46.208.104.202.broad.zq.gd..cn (202.104.208.46)
31.140 ms07/04/:09 UTC--------------------PING:PING 202.104.208.46 (202.104.208.46) 56(84) bytes of data.--- 202.104.208.46 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 3001ms07/04/:08 UTC--------------------MTR:Start: Fri Apr
7 07:04:58 2017HOST: Blizzard
Wrst StDev
1.|-- 114.113.217.146
5.|-- 115.238.7.29
6.|-- 220.191.196.77
7.|-- 220.191.200.9
8.|-- 202.97.85.101
9.|-- 183.57.114.21
1.4 10.|-- 218.15.239.234
0.6 11.|-- 46.208.104.202.broad.zq.gd..cn
0.507/04/:58 UTC--------------------TRACEROUTE:traceroute to 202.104.208.46 (202.104.208.46), 15 hops max, 60 byte packets 1
114.113.217.130 (114.113.217.130)
1.057 ms 2
115.238.7.5 (115.238.7.5)
0.604 ms 6
220.191.196.77 (220.191.196.77)
0.894 ms 7
220.191.200.1 (220.191.200.1)
3.406 ms 8
202.97.85.117 (202.97.85.117)
25.380 ms 9
183.57.113.21 (183.57.113.21)
28.944 ms10
218.15.239.235 (218.15.239.235)
35.274 ms11
46.208.104.202.broad.zq.gd..cn (202.104.208.46)
30.849 ms07/04/:13 UTC--------------------PING:PING 202.104.208.46 (202.104.208.46) 56(84) bytes of data.--- 202.104.208.46 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 3004ms07/04/:11 UTC--------------------TRACEROUTE:traceroute to 202.104.208.46 (202.104.208.46), 15 hops max, 60 byte packets 1
114.113.217.130 (114.113.217.130)
1.088 ms 2
115.238.7.5 (115.238.7.5)
0.582 ms 6
220.191.196.77 (220.191.196.77)
0.872 ms 7
220.191.200.1 (220.191.200.1)
3.540 ms 8
202.97.85.117 (202.97.85.117)
23.631 ms 9
183.57.113.21 (183.57.113.21)
31.345 ms10
218.15.239.235 (218.15.239.235)
35.267 ms11
46.208.104.202.broad.zq.gd..cn (202.104.208.46)
30.435 ms07/04/:16 UTC--------------------MTR:Start: Fri Apr
7 07:05:03 2017HOST: Blizzard
Wrst StDev
1.|-- 114.113.217.130
5.|-- 115.238.7.5
6.|-- 220.191.196.77
7.|-- 220.191.200.1
8.|-- 202.97.85.117
9.|-- 183.57.113.21
1.1 10.|-- 218.15.239.235
1.8 11.|-- 46.208.104.202.broad.zq.gd..cn
0.307/04/:03 UTC--------------------PING:PING 202.104.208.46 (202.104.208.46) 56(84) bytes of data.--- 202.104.208.46 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 3002ms07/04/:14 UTC--------------------PING:PING 202.104.208.46 (202.104.208.46) 56(84) bytes of data.--- 202.104.208.46 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 2998ms07/04/:18 UTC--------------------MTR:Start: Fri Apr
7 07:05:09 2017HOST: Blizzard
Wrst StDev
1.|-- 114.113.217.130
5.|-- 115.238.7.5
6.|-- 220.191.196.77
7.|-- 220.191.200.1
8.|-- 202.97.85.117
9.|-- 183.57.113.21
1.0 10.|-- 218.15.239.235
0.0 11.|-- 46.208.104.202.broad.zq.gd..cn
31.0 104.2
23.807/04/:09 UTC--------------------MTR:Start: Fri Apr
7 07:05:11 2017HOST: Blizzard
Wrst StDev
1.|-- 114.113.217.130
5.|-- 115.238.7.5
6.|-- 220.191.196.77
7.|-- 220.191.200.1
8.|-- 202.97.85.117
9.|-- 183.57.113.21
0.7 10.|-- 218.15.239.235
0.0 11.|-- 46.208.104.202.broad.zq.gd..cn
3.107/04/:11 UTC--------------------MTR:Start: Fri Apr
7 07:05:15 2017HOST: Blizzard
Wrst StDev
1.|-- 114.113.217.130
5.|-- 115.238.7.5
6.|-- 220.191.196.77
7.|-- 220.191.200.1
8.|-- 202.97.85.117
9.|-- 183.57.113.21
1.1 10.|-- 218.15.239.235
0.0 11.|-- 46.208.104.202.broad.zq.gd..cn
0.007/04/:15 UTC--------------------
110 德莱尼 圣骑士
登录战网的错误代码:BLZBNTBGS23)登录魔兽世界错误代码: BLZ
110 德莱尼 圣骑士
技术人员呢
110 德莱尼 圣骑士
这个是战网的测试PING:PING 202.104.208.46 (202.104.208.46) 56(84) bytes of data.--- 202.104.208.46 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 4998ms07/04/:46 UTC--------------------TRACEROUTE:traceroute to 202.104.208.46 (202.104.208.46), 15 hops max, 60 byte packets 1
122.198.65.2 (122.198.65.2)
0.905 ms 2
115.238.7.69 (115.238.7.69)
0.801 ms 4
220.191.196.29 (220.191.196.29)
1.139 ms 5
220.191.200.21 (220.191.200.21)
3.554 ms 6
183.57.113.17 (183.57.113.17)
30.063 ms 8
218.15.239.235 (218.15.239.235)
31.625 ms 9
46.208.104.202.broad.zq.gd..cn (202.104.208.46)
35.145 ms07/04/:46 UTC--------------------MTR:HOST: Blizzard
Wrst StDev
1. 122.198.65.2
3. 115.238.7.69
4. 220.191.196.29
5. 220.191.200.21
6. 202.97.85.109
7. 183.57.113.17
8. 218.15.239.235
9. 46.208.104.202.broad.zq.gd..cn
0.607/04/:46 UTC--------------------
想说点什么吗?登录即可加入讨论。}

我要回帖

更多关于 暴雪游戏平台登录不上 的文章

更多推荐

版权声明:文章内容来源于网络,版权归原作者所有,如有侵权请点击这里与我们联系,我们将及时删除。

点击添加站长微信