 | Error 3007 3005. Quick d/c(1) | Category: Technical SupportJanuary-23-2016 12:31 AM PST (9 years ago)  |
| -I get d/c while playing for a brief moment but then I'm able to reconnect right after but only after I have left my game and relogged into my account. I have a wired connection. I have completed the links listed here: battle.net/support/article/611 battle.net/support/article/7500077 edited my ip for privacy -Monmouth/Independence, Oregon, USA -ISP is MINet fiber -Tracert: Tracing route to 12.129.222.10 over a maximum of 30 hops 1 2 ms 2 ms 12 ms 192.168.1.1 2 3292 ms 1023 ms 1864 ms 209.237.92.1 3 7 ms 7 ms 18 ms 206-192-227-33.lsnetworks.net [206.192.227.33] 4 15 ms 16 ms 15 ms 12.118.34.26 5 29 ms 29 ms 29 ms 12.118.34.25 6 35 ms 34 ms 31 ms cr1.st6wa.ip.att.net [12.122.146.78] 7 45 ms 31 ms 43 ms cr2.st6wa.ip.att.net [12.122.1.78] 8 31 ms 31 ms 31 ms 12.123.244.69 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. -Pathping: Tracing route to 12.129.222.10 over a maximum of 30 hops 0 Desktop-PC.minetfiber.net [192.168.1.110] 1 192.168.1.1 2 209.237.92.1 3 206-192-227-33.lsnetworks.net [206.192.227.33] 4 12.118.34.26 5 12.118.34.25 6 cr1.st6wa.ip.att.net [12.122.146.78] 7 cr2.st6wa.ip.att.net [12.122.1.78] 8 12.123.244.69 9 * * * Computing statistics for 200 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Desktop-PC.minetfiber.net [192.168.1.110] 0/ 100 = 0% | 1 4ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% | 2 7ms 0/ 100 = 0% 0/ 100 = 0% 209.237.92.1 0/ 100 = 0% | 3 9ms 0/ 100 = 0% 0/ 100 = 0% 206-192-227-33.lsnetworks.net [206.192.227.33] 0/ 100 = 0% | 4 17ms 0/ 100 = 0% 0/ 100 = 0% 12.118.34.26 0/ 100 = 0% | 5 30ms 0/ 100 = 0% 0/ 100 = 0% 12.118.34.25 100/ 100 =100% | 6 --- 100/ 100 =100% 0/ 100 = 0% cr1.st6wa.ip.att.net [12.122.146.78] 0/ 100 = 0% | 7 --- 100/ 100 =100% 0/ 100 = 0% cr2.st6wa.ip.att.net [12.122.1.78] 0/ 100 = 0% | 8 --- 100/ 100 =100% 0/ 100 = 0% 12.123.244.69 Trace complete. -Looking Glass: traceroute to ***.**.**.*** (***.**.**.***), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.423 ms 0.635 ms 0.738 ms 2 * * * 3 12.129.199.181 (12.129.199.181) 0.431 ms * * 4 206.16.68.41 (206.16.68.41) 0.450 ms 0.462 ms 0.509 ms 5 12-122-254-225.attens.net (12.122.254.225) 1.115 ms 1.134 ms 1.140 ms 6 cr2.la2ca.ip.att.net (12.123.132.210) 2.442 ms 5.120 ms 5.112 ms 7 ggr2.la2ca.ip.att.net (12.122.129.97) 3.820 ms 3.830 ms 3.831 ms 8 los-brdr-01.inet.qwest.net (63.146.27.101) 1.439 ms 1.457 ms 1.550 ms 9 * * * 10 216-111-122-122.dia.static.qwest.net (216.111.122.122) 28.698 ms 28.989 ms 29.080 ms 11 206-192-227-33.lsnetworks.net (206.192.227.33) 31.322 ms 31.338 ms 31.399 ms 12 206-192-227-34.lsnetworks.net (206.192.227.34) 37.561 ms 37.688 ms 36.626 ms 13 * * * 14 * * * 15 * * * PING ***.**.**.*** (***.**.**.***) 56(84) bytes of data. HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev 1. Blizzard 0.0% 10 0.3 0.4 0.3 0.9 0.2 2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3. 12.129.199.181 0.0% 10 0.5 0.4 0.3 0.5 0.1 4. 206.16.68.41 0.0% 10 0.6 9.9 0.4 95.3 30.0 | ||
 | Error 3007 3005. Quick d/c(2) | January-23-2016 2:23 AM PST (9 years ago) |
1 2 ms 2 ms 12 ms 192.168.1.1 This values are a little bit higher than usual (normally it stays at 1ms or less). 2 3292 ms 1023 ms 1864 ms 209.237.92.1 The latency goes super high and irregular on this hop. - Reset all your network devices (switch them off for couple of minutes and then switch them back on) - Refresh your DNS by pushing Windows key R at the same time and writing ipconfig /flushdns on the Run window. If the tracer keeps showing values like this after doing that, I would recommend contacting your internet provider. Make sure you provide them with the traceroute so they can check what's happening in that hop that has extreme latency. ______________________________________________________ Got feedback about the support I'm providing? Leave your comments here! | ||
