[SOLVED] network does not work reliably

[tango444]

C:\Windows\system32>ping 8.8.8.8 -n 20

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116

Another round
C:\Windows\system32>ping 8.8.8.8 -n 20

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=26ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116

To the router it is perfect..




:\Windows\system32>ping 192.168.0.1 -n 20

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

The internet provides says the line is good.
What could be wrong?
I am on Window 10
The PC is connected with cable.
Thanks.

 

[tango444]

Hi,
I have windows 10 and Missing packets.. browser does not lood randomly.. Pc is connected to the internet with cable.

Ping returns this
C:\Windows\system32>ping 8.8.8.8 -n 20

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=26ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116

To the router it seems to be ok..

C:\Windows\system32>ping 192.168.0.1 -n 20

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

What could be wrong?

 

[bill001g]

Means the loss is outside your house.

Run tracert and find the ip for hop 2 and try to ping that one. That represents the connection between your house and the ISP. This is the most common location for problems and the easiest to get fixed. If you see loss here show your ISP that you have no loss to the router but loss to their router. Hopefully the ISP has not set their router to not respond to ping because it make it harder to test.

If this one ok you can try other hops but the farther from your house you get the more unlikely it is that you can get it fixed. If the problem is damaged connection between 2 ISP that are not yours there is really nobody you can contact.

 

[Ralston18]

Run "tracert" and "pathping" for more information and detail.

Post the results.

FYI:

https://www.geeksforgeeks.org/traceroute-in-network-layer/

https://netbeez.net/blog/path-analysis-pathping-windows/

 

[tango444]

C:\Windows\system32>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 6 ms 7 ms 10.229.0.1
3 6 ms 5 ms 8 ms tge1-1.osr0-tvnetwork.net.telekom.hu [81.183.205.26]
4 7 ms 6 ms 7 ms 81.183.0.37
5 7 ms 7 ms 11 ms 81.183.0.37
6 14 ms 8 ms 9 ms 81.183.3.62
7 7 ms 7 ms 8 ms 81.183.3.117
8 * 10 ms 18 ms 74.125.242.241
9 7 ms 7 ms 5 ms 142.251.65.219
10 6 ms 7 ms 7 ms dns.google [8.8.8.8]

Trace complete.

C:\Windows\system32>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * 13 ms 6 ms 10.229.0.1
3 * * * Request timed out.
4 * * 12 ms 81.183.0.37
5 9 ms 7 ms 6 ms 81.183.0.37
6 8 ms 7 ms 6 ms 81.183.3.62
7 * * * Request timed out.
8 6 ms 8 ms 9 ms 74.125.242.241
9 6 ms 8 ms 9 ms 142.251.65.219
10 8 ms 8 ms 7 ms dns.google [8.8.8.8]

Trace complete.

C:\Windows\system32>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 12 ms 6 ms 10.229.0.1
3 10 ms 5 ms 7 ms tge1-1.osr0-tvnetwork.net.telekom.hu [81.183.205.26]
4 9 ms 8 ms 7 ms 81.183.0.37
5 8 ms 8 ms 7 ms 81.183.0.37
6 11 ms 7 ms 7 ms 81.183.3.62
7 * * 6 ms 81.183.3.117
8 8 ms 5 ms 5 ms 74.125.242.241
9 7 ms 6 ms 5 ms 142.251.65.219
10 6 ms 5 ms 5 ms dns.google [8.8.8.8]

Trace complete.

C:\Windows\system32>pathping 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
0 host.docker.internal [192.168.0.14]
1 192.168.0.1
2 10.229.0.1
3 tge1-1.osr0-tvnetwork.net.telekom.hu [81.183.205.26]
4 81.183.0.37
5 81.183.0.37
6 81.183.3.62
7 81.183.3.117
8 74.125.242.241
9 142.251.65.219
10 dns.google [8.8.8.8]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 host.docker.internal [192.168.0.14]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
33/ 100 = 33% |
2 7ms 40/ 100 = 40% 7/ 100 = 7% 10.229.0.1
0/ 100 = 0% |
3 8ms 40/ 100 = 40% 7/ 100 = 7% tge1-1.osr0-tvnetwork.net.telekom.hu [81.183.205.26]
0/ 100 = 0% |
4 7ms 35/ 100 = 35% 2/ 100 = 2% 81.183.0.37
0/ 100 = 0% |
5 8ms 33/ 100 = 33% 0/ 100 = 0% 81.183.0.37
4/ 100 = 4% |
6 8ms 37/ 100 = 37% 0/ 100 = 0% 81.183.3.62
5/ 100 = 5% |
7 9ms 42/ 100 = 42% 0/ 100 = 0% 81.183.3.117
1/ 100 = 1% |
8 8ms 43/ 100 = 43% 0/ 100 = 0% 74.125.242.241
4/ 100 = 4% |
9 --- 100/ 100 =100% 53/ 100 = 53% 142.251.65.219
0/ 100 = 0% |
10 8ms 47/ 100 = 47% 0/ 100 = 0% dns.google [8.8.8.8]

Trace complete.

C:\Windows\system32>pathping 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
0 host.docker.internal [192.168.0.14]
1 192.168.0.1
2 * 10.229.0.1
3 tge1-1.osr0-tvnetwork.net.telekom.hu [81.183.205.26]
4 81.183.0.37
5 81.183.0.37
6 81.183.3.62
7 81.183.3.117
8 74.125.242.241
9 142.251.65.219
10 dns.google [8.8.8.8]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 host.docker.internal [192.168.0.14]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
16/ 100 = 16% |
2 6ms 16/ 100 = 16% 0/ 100 = 0% 10.229.0.1
4/ 100 = 4% |
3 7ms 20/ 100 = 20% 0/ 100 = 0% tge1-1.osr0-tvnetwork.net.telekom.hu [81.183.205.26]
0/ 100 = 0% |
4 8ms 20/ 100 = 20% 0/ 100 = 0% 81.183.0.37
0/ 100 = 0% |
5 7ms 22/ 100 = 22% 2/ 100 = 2% 81.183.0.37
0/ 100 = 0% |
6 9ms 23/ 100 = 23% 3/ 100 = 3% 81.183.3.62
0/ 100 = 0% |
7 9ms 20/ 100 = 20% 0/ 100 = 0% 81.183.3.117
2/ 100 = 2% |
8 7ms 23/ 100 = 23% 1/ 100 = 1% 74.125.242.241
0/ 100 = 0% |
9 --- 100/ 100 =100% 78/ 100 = 78% 142.251.65.219
0/ 100 = 0% |
10 8ms 22/ 100 = 22% 0/ 100 = 0% dns.google [8.8.8.8]

Trace complete.

 

[bill001g]

Seems the loss is very random. It does not even stay consistent during the times these commands take to run. Pathping is not seeing loss to 8.8.8.8 and tracert is showing either no loss or loss to random nodes.

I would try a constant ping to 10.229.0.1 and see if you get similar results to your ping to 8.8.8.8

This is the ISP router that runs the connection to your house so if you see it here there is a problem with the wiring or other equipment between your house and the ISP

 

[tango444]

ping 10.229.0.1 -n 20

Pinging 10.229.0.1 with 32 bytes of data:
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=4ms TTL=254
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=8ms TTL=254
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=8ms TTL=254
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Request timed out.
Request timed out.

Then no connection problems of 4 times ... running the ping.. I do not post them ..
THen.

ping 10.229.0.1 -n 20

Pinging 10.229.0.1 with 32 bytes of data:
Reply from 10.229.0.1: bytes=32 time=8ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=10ms TTL=254
Reply from 10.229.0.1: bytes=32 time=8ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254

Ping statistics for 10.229.0.1:
Packets: Sent = 20, Received = 17, Lost = 3 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 10ms, Average = 6ms

ping 10.229.0.1 -n 20

Pinging 10.229.0.1 with 32 bytes of data:
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=8ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Request timed out.
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=8ms TTL=254
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=7ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=6ms TTL=254
Reply from 10.229.0.1: bytes=32 time=8ms TTL=254
Reply from 10.229.0.1: bytes=32 time=5ms TTL=254

Ping statistics for 10.229.0.1:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 8ms, Average = 6ms

 

[bill001g]

yup you now have proof that you internet connection has some issue.

So take these results along with the ones that show your router get no loss and call the ISP. Hopefully you get a halfway smart person. I ran into a couple that do not even know what the ping command is. Most do have methods to test the line which will show problems sometime better than ping commands will.

 

[tango444]

yup you now have proof that you internet connection has some issue.

So take these results along with the ones that show your router get no loss and call the ISP. Hopefully you get a halfway smart person. I ran into a couple that do not even know what the ping command is. Most do have methods to test the line which will show problems sometime better than ping commands will.

Something I do not understand.. They/internet provider said there is no problem.

1. if I put wifi dongle into USB port of the PC and I connectusing that to wifi of the modem... I have much less problems... the loss is much less frequent... pages come up immediately
2. If I connect a laptop using the same cable I use to connect it to the PC.... I seem to have no browsing problems///

So if I use witi connect between PC and modem.

Ping statistics for 10.229.0.1:
Packets: Sent = 200, Received = 197, Lost = 3 (1% loss),

Ping statistics for 8.8.8.8:
Packets: Sent = 200, Received = 198, Lost = 2 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 20ms, Average = 7ms

It looks contradictory.

 

[bill001g]

You have tested the pc to the router with ping. If there is any issue with the pc or with cabling you would see issues ping the router.

Data going to a different IP first goes to the router and then to the ISP. It follows the exact path as your ping to the router. It would be highly unlikely that a packet would be dropped going between the pc and the router just because it had a final destination address other than the router.

You are going to have to do more testing if you really think it works for some machine and not others. You almost have to see packet loss on hop 1 if there is a problem with the pc or the cable.

 

[tango444]

You have tested the pc to the router with ping. If there is any issue with the pc or with cabling you would see issues ping the router.

Data going to a different IP first goes to the router and then to the ISP. It follows the exact path as your ping to the router. It would be highly unlikely that a packet would be dropped going between the pc and the router just because it had a final destination address other than the router.

You are going to have to do more testing if you really think it works for some machine and not others. You almost have to see packet loss on hop 1 if there is a problem with the pc or the cable.

so if I had a problem with network chips.. in the pc. would I experience a loss of packets on hop 1?

 

[bill001g]

Yes the same network chip talks to the router so if it was bad all packet would be affected. The network hardware actually has no concept of ip addresses. It at best knows about mac addresses. I does not look inside the data packet to it all the ip header and the actual user data is just payload. There used to be protocols that didn't use IP addresses and the same chips would pass those it doesn't care what it being passed.

All the IP address stuff is used by the all the routers to find the path to the destination.