It looks like you're new here. If you want to get involved, click one of these buttons!
Just came back to wow and am getting dc from the game quite often. I ran a couple of test but dont know how to read them, thought someone could read them for me.
<p "="">
1 Human Paladin
0 |
|
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 98 | 25884 | 674 | 0 | 0 | 10 | 0 |
| blk-137-116-1.eastlink.ca - 98 | 30200 | 676 | 13 | 27 | 436 | 30 |
| blk-212-126-45.eastlink.ca - 98 | 24833 | 674 | 7 | 12 | 136 | 11 |
| ns-hlfx-dr002.ns.eastlink.ca - 98 | 32027 | 676 | 19 | 25 | 59 | 25 |
| ns-hlfx-br002.ns.eastlink.ca - 98 | 32739 | 676 | 17 | 25 | 62 | 25 |
| te-9-1.car2.Montreal2.Level3.net - 98 | 33169 | 669 | 39 | 68 | 273 | 44 |
| ae-11-11.car1.Montreal2.Level3.net - 99 | 35303 | 485 | 37 | 69 | 278 | 253 |
| No response from host - 100 | 23758 | 0 | 0 | 0 | 0 | 0 |
| ae-72-72.csw2.NewYork1.Level3.net - 99 | 35617 | 545 | 40 | 45 | 71 | 43 |
| ae-2-70.edge3.NewYork1.Level3.net - 98 | 31760 | 676 | 40 | 47 | 114 | 45 |
| 64.208.110.153 - 98 | 31644 | 674 | 39 | 45 | 142 | 47 |
| po5-20G.ar2.CHI2.gblx.net - 98 | 29111 | 674 | 58 | 68 | 253 | 63 |
| 192.205.33.245 - 98 | 29670 | 676 | 59 | 65 | 92 | 68 |
| cr2.cgcil.ip.att.net - 98 | 32473 | 669 | 67 | 73 | 121 | 74 |
| gar6.ipsin.ip.att.net - 98 | 26552 | 674 | 64 | 83 | 266 | 69 |
| 12.122.251.18 - 100 | 23797 | 52 | 68 | 89 | 290 | 72 |
| No response from host - 100 | 23751 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23762 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23750 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23761 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23751 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23762 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23758 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23750 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23761 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23757 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23750 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23754 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23753 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 23754 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Comments
Looks like you loses connection to the server.
Does this happen in other games as well?
Have you tried to disable the firewall to see if it changes anything?
Also, there might be a malware affecting your computer. Try downloading and running Add-aware, it might help or not but it certainly doesn't hurt if you havn't done it already or have a really good antivirus that takes care of malware as well.
I'm not sure what to make of the first program output.
The second looks like a typical traceroute. As I read it, you're sending out massive numbers of packets, and nearly all of them are getting dropped somewhere. Traceroutes basically say, go n hops out, then if you haven't reached the end, stop and report back. But you're not seeing a report back about 98% of the time. That strikes me as very odd, but assuming it's correct (which is a big assumption, and might not be true):
192.168.0.1 is a private IP address, not part of the public Internet. That it's losing most of your packets, too, means that your problems come before you actually connect to the public Internet. It's probably your router, but at a bare minimum, it's a problem on your end.
Are you on a wireless connection? If so, try using ethernet to eliminate wireless problems and see if that changes anything.
One could read that information and deduce that he's in Canada, using the ISP Eastlink. But I doubt that one could do anything more dangerous than tracing him to Halifax, as his profile says.
I did post on the wow forums but there are a lot of smart people here so I thought I might be able to get some help here.
It wasn't happening in other games before, but like I said when I got dc just now I also got dc from mumble. Yes firewall is disabled. Havnt checked for maleware.
Not to worry, trace route shows us the nearest sever but not his actually location. Closest we can see is...
Which is an address for eastlink telephone company. Nice multistory building on the corner of the street. Looks like other businesses have a shared address.
Do some research on how NAT (Network Address Translation) works. The OP is behind a NAT, which is built into the router. That alone makes it nearly impossible for someone to send an attack to his computer from the internet. Traffic will simply be dropped at the router.
A firewall is the last thing I would suspect for intermittent connection drops. I would only suspect a firewall if you can't connect at all or if you are trying to host something.
This looks like a router, modem, or ISP issue. Some ISPs provide a router which is built into the modem. If yours has two separate pieces of equipment, try bypassing the router and connect directly to the modem. Test to see if you get disconnected from anything over a period of several days. If you don't, add the router back and test again. If you do get disconnected from multiple services at the same time without the router in the equation, it might be time to call your ISP.
As has been pointed out above - the problem is in your house.
Your getting 0% traffic out to your router in this test, and 98% packet loss in the other test. You obviously have some connection - DNS servers were able to get out, and tracert could get something out to see what the hops were, but you aren't getting any actual usable traffic.
192.168.0.1 is typically your home modem or bridge.
It could be as simple as a bad or loose ethernet cable. Check the cable, check that you can connect to something else with the ethernet card in your computer. Take the router out of the equation if possible. If both of those check out ok, then it's time to call your ISP. Most ISPs lease or sell the modem, and as such will repair them.
Can you run IPv6? If you can, turn it on and run with it, see if it helps.
To me, it looks like you're running across the issue with Level 3's network. It's an ongoing issue that they are working to fix, and for a very short story on what happened, they didn't upgrade the memory of their switches, and new routing tables that deployed kinda blew up their IPv4 tables (resulting in massive packet loss across their whole network).
Wrong.
Factor in DMZ in the equation and it's easy to attack the host. If router is in the way, run reaver for an hour and own the router, failing that use project obi-wan to brute force the router, set the host as DMZ, THEN own the host.
Call ISP and get a line test done, set DNS to 8.8.8.8 and 8.4.4.4 (google =P) to bypass any possible ISP side errors, since dropped packets aren't a guaranteed 'at the client' problem. As stated above, try ditching the router if you can (only possible if you're using a separate router after the provided modem. if it's an all-in-one, not much you can do). Get malwarebytes and hijackthis and check for malware or other crap (adaware is old news and doesn't work for sh!t). Good luck.
If you're putting your computer in the DMZ, you are clueless and deserve to be attacked. I can't think of a single game which would require your computer to be in the DMZ for playing it or hosting it. Port forwarding is the appropriate answer when a game doesn't take the measures to bypass NAT, not the DMZ.
I now see the OP has massive packet loss to their router.
192.168.0.1 - 98 | 25884 | 674
Test with a different computer if you can. Eliminate the computer and the network cable from the equation. You could have a bad NIC on your computer, a bad port on your router, or a bad network cable.
Yea there was a message on the launcher the other day.
Missed the whole point. He doesn't have to have his comp in the DMZ. 99% of uneducated home computer users that don't know how to swap firmware get put in DMZ by anyone that wants to put them there. Blame the government for limiting 'legal' encryption levels to things that were cracked in the '90's lol
I did read the wow was having issues but i can hit any server and get alot of loss. I did this one on my laptop and i hit google.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 98 | 98 | 1 | 4 | 14 | 2 |
| blk-137-116-1.eastlink.ca - 3 | 91 | 89 | 20 | 36 | 62 | 41 |
| blk-212-126-45.eastlink.ca - 2 | 95 | 94 | 10 | 21 | 53 | 26 |
| ns-hlfx-dr002.ns.eastlink.ca - 3 | 91 | 89 | 25 | 35 | 59 | 49 |
| ns-hlfx-br002.ns.eastlink.ca - 3 | 91 | 89 | 26 | 34 | 50 | 29 |
| ns-hlfx-br001.ns.eastlink.ca - 3 | 91 | 89 | 24 | 34 | 54 | 31 |
| gw-google.torontointernetxchange.net - 48 | 34 | 18 | 55 | 60 | 68 | 55 |
| 209.85.255.232 - 48 | 34 | 18 | 55 | 61 | 70 | 60 |
| 216.239.46.162 - 70 | 26 | 8 | 77 | 84 | 97 | 77 |
| 72.14.239.190 - 59 | 29 | 12 | 80 | 94 | 108 | 97 |
| 64.233.174.95 - 59 | 29 | 12 | 87 | 97 | 117 | 95 |
| 209.85.255.223 - 95 | 20 | 1 | 118 | 118 | 118 | 118 |
| google-public-dns-a.google.com - 4 | 87 | 84 | 87 | 112 | 127 | 104 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Death is nothing to us, since when we are, Death has not come, and when death has come, we are not.
Maybe but i get a loss even if i hit google servers. Also why is my test resut different when i do pathping in dos compared to winmtr? This is my dos test on various servers
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:Windowssystem32>tracert 63.240.161.189
Tracing route to 63.240.161.189 over a maximum of 30 hops
1 7 ms 9 ms 9 ms 192.168.0.1
2 56 ms 29 ms 39 ms blk-137-116-1.eastlink.ca [24.137.116.1]
3 26 ms 29 ms 19 ms blk-212-126-45.eastlink.ca [173.212.126.45]
4 31 ms 49 ms 49 ms ns-hlfx-dr002.ns.eastlink.ca [24.215.102.129]
5 36 ms 39 ms 39 ms ns-hlfx-br002.ns.eastlink.ca [24.215.102.221]
6 56 ms 59 ms 59 ms te-9-1.car2.Montreal2.Level3.net [4.59.178.77]
7 51 ms 59 ms 59 ms ae-11-11.car1.Montreal2.Level3.net [4.69.141.2]
8 * * * Request timed out.
9 * * * Request timed out.
10 53 ms 59 ms 59 ms ae-3-80.edge3.NewYork1.Level3.net [4.69.155.145]
11 58 ms 59 ms 59 ms 64.208.110.153
12 64 ms 70 ms 79 ms 192.205.33.13
13 89 ms 89 ms 89 ms cr1.n54ny.ip.att.net [12.122.131.86]
14 79 ms 79 ms 79 ms cr2.cgcil.ip.att.net [12.122.1.2]
15 74 ms 69 ms 79 ms gar6.ipsin.ip.att.net [12.122.132.241]
16 * 165 ms 209 ms 12.122.251.18
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.
C:Windowssystem32>pathping 63.240.161.189
Tracing route to 63.240.161.189 over a maximum of 30 hops
0 deathrament-PC [192.168.0.2]
1 192.168.0.1
2 blk-137-116-1.eastlink.ca [24.137.116.1]
3 blk-212-126-45.eastlink.ca [173.212.126.45]
4 ns-hlfx-dr002.ns.eastlink.ca [24.215.102.129]
5 ns-hlfx-br002.ns.eastlink.ca [24.215.102.221]
6 te-9-1.car2.Montreal2.Level3.net [4.59.178.77]
7 ae-11-11.car1.Montreal2.Level3.net [4.69.141.2]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 deathrament-PC [192.168.0.2]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 24ms 0/ 100 = 0% 0/ 100 = 0% blk-137-116-1.eastlink.ca [24.137.
116.1]
0/ 100 = 0% |
3 23ms 0/ 100 = 0% 0/ 100 = 0% blk-212-126-45.eastlink.ca [173.21
2.126.45]
0/ 100 = 0% |
4 35ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-dr002.ns.eastlink.ca [24.2
15.102.129]
0/ 100 = 0% |
5 36ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-br002.ns.eastlink.ca [24.2
15.102.221]
0/ 100 = 0% |
6 75ms 0/ 100 = 0% 0/ 100 = 0% te-9-1.car2.Montreal2.Level3.net [
4.59.178.77]
0/ 100 = 0% |
7 80ms 0/ 100 = 0% 0/ 100 = 0% ae-11-11.car1.Montreal2.Level3.net
[4.69.141.2]
Trace complete.
C:Windowssystem32>pathping 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
0 deathrament-PC [192.168.0.2]
1 192.168.0.1
2 blk-137-116-1.eastlink.ca [24.137.116.1]
3 blk-212-126-45.eastlink.ca [173.212.126.45]
4 ns-hlfx-dr002.ns.eastlink.ca [24.215.102.129]
5 ns-hlfx-br002.ns.eastlink.ca [24.215.102.221]
6 ns-hlfx-br001.ns.eastlink.ca [24.215.102.9]
7 gw-google.torontointernetxchange.net [206.108.34.6]
8 209.85.255.232
9 216.239.46.162
10 72.14.232.141
11 216.239.46.193
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 deathrament-PC [192.168.0.2]
0/ 100 = 0% |
1 5ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 22ms 0/ 100 = 0% 0/ 100 = 0% blk-137-116-1.eastlink.ca [24.137.
116.1]
0/ 100 = 0% |
3 21ms 0/ 100 = 0% 0/ 100 = 0% blk-212-126-45.eastlink.ca [173.21
2.126.45]
0/ 100 = 0% |
4 35ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-dr002.ns.eastlink.ca [24.2
15.102.129]
0/ 100 = 0% |
5 35ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-br002.ns.eastlink.ca [24.2
15.102.221]
0/ 100 = 0% |
6 35ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-br001.ns.eastlink.ca [24.2
15.102.9]
0/ 100 = 0% |
7 62ms 0/ 100 = 0% 0/ 100 = 0% gw-google.torontointernetxchange.n
et [206.108.34.6]
0/ 100 = 0% |
8 62ms 0/ 100 = 0% 0/ 100 = 0% 209.85.255.232
100/ 100 =100% |
9 --- 100/ 100 =100% 0/ 100 = 0% 216.239.46.162
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 72.14.232.141
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% 216.239.46.193
Trace complete.
C:Windowssystem32>pathping 8.4.4.4
Tracing route to 8.4.4.4 over a maximum of 30 hops
0 deathrament-PC [192.168.0.2]
1 192.168.0.1
2 blk-137-116-1.eastlink.ca [24.137.116.1]
3 blk-212-126-45.eastlink.ca [173.212.126.45]
4 ns-hlfx-dr002.ns.eastlink.ca [24.215.102.129]
5 ns-hlfx-br002.ns.eastlink.ca [24.215.102.221]
6 ns-hlfx-br001.ns.eastlink.ca [24.215.102.9]
7 xe-11-0-0.bar2.Boston1.Level3.net [4.79.2.89]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 deathrament-PC [192.168.0.2]
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 30ms 0/ 100 = 0% 0/ 100 = 0% blk-137-116-1.eastlink.ca [24.137.
116.1]
0/ 100 = 0% |
3 27ms 1/ 100 = 1% 1/ 100 = 1% blk-212-126-45.eastlink.ca [173.21
2.126.45]
0/ 100 = 0% |
4 57ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-dr002.ns.eastlink.ca [24.2
15.102.129]
0/ 100 = 0% |
5 53ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-br002.ns.eastlink.ca [24.2
15.102.221]
0/ 100 = 0% |
6 51ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-br001.ns.eastlink.ca [24.2
15.102.9]
0/ 100 = 0% |
7 58ms 0/ 100 = 0% 0/ 100 = 0% xe-11-0-0.bar2.Boston1.Level3.net
[4.79.2.89]
Trace complete.
C:Windowssystem32> pathping 63.240.161.189
Tracing route to 63.240.161.189 over a maximum of 30 hops
0 deathrament-PC [192.168.0.2]
1 192.168.0.1
2 blk-137-116-1.eastlink.ca [24.137.116.1]
3 blk-212-126-45.eastlink.ca [173.212.126.45]
4 ns-hlfx-dr002.ns.eastlink.ca [24.215.102.129]
5 ns-hlfx-br002.ns.eastlink.ca [24.215.102.221]
6 te-9-1.car2.Montreal2.Level3.net [4.59.178.77]
7 ae-11-11.car1.Montreal2.Level3.net [4.69.141.2]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 deathrament-PC [192.168.0.2]
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 24ms 0/ 100 = 0% 0/ 100 = 0% blk-137-116-1.eastlink.ca [24.137.
116.1]
0/ 100 = 0% |
3 24ms 0/ 100 = 0% 0/ 100 = 0% blk-212-126-45.eastlink.ca [173.21
2.126.45]
0/ 100 = 0% |
4 35ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-dr002.ns.eastlink.ca [24.2
15.102.129]
0/ 100 = 0% |
5 36ms 0/ 100 = 0% 0/ 100 = 0% ns-hlfx-br002.ns.eastlink.ca [24.2
15.102.221]
0/ 100 = 0% |
6 80ms 0/ 100 = 0% 0/ 100 = 0% te-9-1.car2.Montreal2.Level3.net [
4.59.178.77]
0/ 100 = 0% |
7 86ms 0/ 100 = 0% 0/ 100 = 0% ae-11-11.car1.Montreal2.Level3.net
[4.69.141.2]
As above poster said, problem not on your end. Its with Level 3. Level 3 is a regional ISP provider. If their IP routing is messed up then your packet will become lost. In your tests you are losing packets when you hit Level 3's network or Toronto's Internet Exchange.
I would say something is wrong with WinMTR if you are able to connect to the net with 98% packet loss. Probably it sent a shit load of packets at once and your router said no way. New Router would help with this.
If it's so easy to take control of any arbitrary router and make it do whatever you want, wouldn't that make it easy for hackers to arbitrarily change, oh, basically any web site in existence?
As for the US government limiting "legal" levels of encryption, that was for export only and hasn't been enforced at all in many years. Today, TLS (among other things, what is used for essentially any site you connect to that starts with https) usually implements much stronger encryption than was nominally "legal" then.
Your computer can't be "moved" into the DMZ by an outside attacker. That requires a configuration change on the router, as Quizzical pointed out. If it were as easy as you claim, people would be getting their home networks hacked all the time and financial information would be stolen far more often.
The majority of malware and "hacking" comes from careless and uneducated users. They fall for phishing attacks, download files from illegitimate sources, or open every email attachment they receive. "Hackers" don't have to attack. They only have to set up a trap and wait for people to fall in it.
OP: You are seeing 100% packet loss to certain nodes farther in your path. This is normal. Some hops on the internet don't respond to pings.