Question I just moved houses and kept the same plan but now getting packet loss ?

[hypexo]

Hi ive been getting heavy ping spikes and packet loss at random times. Sometimes it will cool down and not do it for 5ish mins but other times it will happen 30 seconds apart. I havnt tried much to fix it but im not sure what to do.

i have a cox modem with 500ish download and 10 up if you have any fixes please let me know

 

[Ralston18]

More information needed.

Make and model modem, router, or modem/router if combined.

Cox being your ISP and they provided the devices being used - correct?

Run "ipconfig /all" (without quotes) via the Command Prompt from your main computer.

Also run "ping", "pathping", and "tracert" via the Command Prompt from your main computer targeting Googles's website at 8.8.8.8.

The commands may require a few minutes to run.

When finished with each command you should be able to copy and past the results herein without needing to retype everything.

 

[hypexo]

More information needed.

Make and model modem, router, or modem/router if combined.

Cox being your ISP and they provided the devices being used - correct?

Run "ipconfig /all" (without quotes) via the Command Prompt from your main computer.

Also run "ping", "pathping", and "tracert" via the Command Prompt from your main computer targeting Googles's website at 8.8.8.8.

The commands may require a few minutes to run.

When finished with each command you should be able to copy and past the results herein without needing to retype everything.

what do i need to get from these commands

 

[USAFRet]

Hi ive been getting heavy ping spikes and packetloss at random times. Sometimes it will cool down and not do it for 5ish mins but other times it will happen 30 seconds apart. I havnt tried much to fix it but im not sure what to do.

i have a cox modem with 500ish download and 10 up if you have any fixes please let me know

Wired to the router or WiFi?

 

[Ralston18]

All of the displayed results.

However, you can redact any name or words that you believe to be personally revealing.

For example my pathping would show my computer name and network name.

As would "ipconfig /all".

If you are concerned about IP addresses then, FYI:

https://www.lifewire.com/what-is-a-...thin a specific,is used for the communication.

End objective being to help determine where the spikes and heavy losses are occurring: 1) in your network, 2) in your ISP's network, or3 ) beyond your ISP.

You are responsible for 1).
Your ISP for 2). Maybe....
Neither of you can do anything regarding 3).

 

[hypexo]

Wired to the router or WiFi?

wired

All of the displayed results.

However, you can redact any name or words that you believe to be personally revealing.

For example my pathping would show my computer name and network name.

As would "ipconfig /all".

If you are concerned about IP addresses then, FYI:

https://www.lifewire.com/what-is-a-private-ip-address-2625970#:~:text=The hardware within a specific,is used for the communication.

End objective being to help determine where the spikes and heavy losses are occurring: 1) in your network, 2) in your ISP's network, or3 ) beyond your ISP.

You are responsible for 1).
Your ISP for 2). Maybe....
Neither of you can do anything regarding 3).

i will get those answers as soon as i can but i feel like it might be beyond my isp just for the reason that im like a couple mins out of town so im sorta in the middle of no where

 

[hypexo]

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
0 DESKTOP-OT9AIG5 [192.168.0.181]
1 192.168.0.1
2 10.40.144.1
3 100.127.77.150
4 100.120.100.148
5 langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 72.215.224.173
7 142.251.238.107
8 209.85.249.177
9 dns.google [8.8.8.8]
---------------------------------------------------------------------------------------------------------------------
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-OT9AIG5 [192.168.0.181]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% 10.40.144.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% 100.127.77.150
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% 100.120.100.148
0/ 100 = 0% |
5 27ms 1/ 100 = 1% 1/ 100 = 1% langbprj01-ae1.rd.la.cox.net [68.1.1.13]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 72.215.224.173
0/ 100 = 0% |
7 24ms 0/ 100 = 0% 0/ 100 = 0% 142.251.238.107
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 209.85.249.177
0/ 100 = 0% |
9 25ms 0/ 100 = 0% 0/ 100 = 0% dns.google [8.8.8.8]


Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=22ms TTL=118
Reply from 8.8.8.8: bytes=32 time=23ms TTL=118
Reply from 8.8.8.8: bytes=32 time=23ms TTL=118
Reply from 8.8.8.8: bytes=32 time=24ms TTL=118

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 24ms, Average = 23ms
---------------------------------------------------------------------------------------------------------------------
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 3 ms 2 ms 1 ms 192.168.0.1
2 19 ms 9 ms 17 ms 10.40.144.1
3 13 ms 9 ms 14 ms 100.127.77.150
4 10 ms 20 ms 17 ms 100.120.100.148
5 * * * Request timed out.
6 29 ms 22 ms 24 ms 72.215.224.173
7 26 ms 22 ms 21 ms 142.251.238.107
8 21 ms 21 ms 22 ms 209.85.249.177
9 26 ms 26 ms 23 ms dns.google [8.8.8.8]

this is the commands besides ipconfig

 

[hypexo]

Host Name . . . . . . . . . . . . : DESKTOP-OT9AIG5
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (7) I219-V
Physical Address. . . . . . . . . : 00-D8-61-1A-0C-CA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2600:8800:8305:ba00::3dda(Preferred)
Lease Obtained. . . . . . . . . . : Tuesday, October 17, 2023 1:04:06 PM
Lease Expires . . . . . . . . . . : Wednesday, October 18, 2023 1:04:05 PM
IPv6 Address. . . . . . . . . . . : 2600:8800:8305:ba00:10d8:fe90:1eac:d7c2(Preferred)
Temporary IPv6 Address. . . . . . : 2600:8800:8305:ba00:c1ad:cb66:535d:3095(Preferred)
Link-local IPv6 Address . . . . . : fe80::dcfa:a3c6:c4be:88b6%7(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.181(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, October 17, 2023 11:01:52 AM
Lease Expires . . . . . . . . . . : Thursday, October 19, 2023 1:03:59 PM
Default Gateway . . . . . . . . . : fe80::8a9e:68ff:fe32:805c%7
192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 100718689
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2C-6C-39-29-00-D8-61-1A-0C-CA
DNS Servers . . . . . . . . . . . : 2001:578:3f::30
2001:578:3f:1::30
68.105.28.11
68.105.29.11
68.105.28.12
2001:578:3f::30
2001:578:3f:1::30
NetBIOS over Tcpip. . . . . . . . : Enabled

 

[bill001g]

Everything you have posted looks fine. All that means though is the problem did not happen when you were running those commands.

I would first try to disable IPv6 in the nic setting on your ethernet card. May or may not make any difference but IPv6 can many times follow different path in the internet than IPv4. It is unlikely turning off IPv6 will have any negative impact and it tends to cause strange problems for people.

Since the problem is intermittent try to leave a constant ping command run to 10.40.144.1. This should be your ISP first router and issue on this connection tend to be on the wires coming to your house. Hopefully the ISP has not disabled the ability to run ping commands to it.

You can also leave a ping run to 8.8.8.8 just to be sure you are seeing the loss and ping spikes at the same time.....I assume you are seeing this in a game or something ?

 

[hypexo]

Everything you have posted looks fine. All that means though is the problem did not happen when you were running those commands.

I would first try to disable IPv6 in the nic setting on your ethernet card. May or may not make any difference but IPv6 can many times follow different path in the internet than IPv4. It is unlikely turning off IPv6 will have any negative impact and it tends to cause strange problems for people.

Since the problem is intermittent try to leave a constant ping command run to 10.40.144.1. This should be your ISP first router and issue on this connection tend to be on the wires coming to your house. Hopefully the ISP has not disabled the ability to run ping commands to it.

You can also leave a ping run to 8.8.8.8 just to be sure you are seeing the loss and ping spikes at the same time.....I assume you are seeing this in a game or something ?

yes i am seeing it in a game i dont think its my ethernet card because the other computer in my house has the same problem so does my phone i can try to ping 10.40.144.1 and see what happens i also dont have a router atm just the modem that came with the isp

 

[bill001g]

It is not a actual ethernet issue it is IPv6. Your other devices if they also run IPv6 could be affected.

It is just such a common issue that I recommend people disable it just to be sure that is not the cause of the problem.

But as stated ralston18 post the main goal of the ping commands is to try to find where the problem is. You actually really hope you see problems on the connection between your house and the ISP it tends to be the only one that the ISP can easily fix. Other stuff might be in another ISP network for example.

Luckily the problems tend to be in the connection coming to your house most the time.

 

[hypexo]

It is not a actual ethernet issue it is IPv6. Your other devices if they also run IPv6 could be affected.

It is just such a common issue that I recommend people disable it just to be sure that is not the cause of the problem.

But as stated ralston18 post the main goal of the ping commands is to try to find where the problem is. You actually really hope you see problems on the connection between your house and the ISP it tends to be the only one that the ISP can easily fix. Other stuff might be in another ISP network for example.

Luckily the problems tend to be in the connection coming to your house most the time.

so you think disabling ipv6 could fix the problem or lead me to fix the problem and what commands should i be doing that ralston18 said just pining the server?

 

[bill001g]

Disabling ipv6 is a trivial thing to try.....I always disable on every machine I use "just because".

Things like pathping etc are tools that make it easier for someone new but they only run for a short time.

You are going to basically do what pathping is doing but do it manually. You technically could ping every ip in the path like pathping does but since you can't fix most of them it tends to be a waste of time.

The command is very simple. Just open a cmd window and type. Let it run in the background until you see issues in your game and then quickly switch over and see if you see problems at the same time.

ping 10.40.144.1 -t

Depending what you see you can try other IP. You could for example try 192.168.0.1 which is your router. You seldom see issues here but you can open a second cmd window and let that one run in the background at the same time.

You really hope you see problems on the connection to your ISP...if the problem is say in connection between the ISP the game company uses and some other ISP you are not going to get that fixed.

 

[hypexo]

Disabling ipv6 is a trivial thing to try.....I always disable on every machine I use "just because".

Things like pathping etc are tools that make it easier for someone new but they only run for a short time.

You are going to basically do what pathping is doing but do it manually. You technically could ping every ip in the path like pathping does but since you can't fix most of them it tends to be a waste of time.

The command is very simple. Just open a cmd window and type. Let it run in the background until you see issues in your game and then quickly switch over and see if you see problems at the same time.

ping 10.40.144.1 -t

Depending what you see you can try other IP. You could for example try 192.168.0.1 which is your router. You seldom see issues here but you can open a second cmd window and let that one run in the background at the same time.

You really hope you see problems on the connection to your ISP...if the problem is say in connection between the ISP the game company uses and some other ISP you are not going to get that fixed.

ok i did ping 10.40.144.1 -t and when my game spiked the ping in the cmd didnt go up at all so is it something outside of my isp?

 

[bill001g]

Maybe gets very complex to find the true cause sometimes.

Try leaving a ping run to 8.8.8.8. Problem is this just tells you if you have a good path between your house and google does not really tell you about the game company.

You could in theory ping the game servers but most times these are complex server farms and not single devices. Many game companies also block ping commands to their servers. Lots of poor losers in online games that would use ping commands as denial of service attacks to affect the game company and other players.

You in many ways hope this is not your issue. You have almost no options to fix any of this stuff. The only thing you can even think to try to fix issue outside your ISP is to use one of the gamer VPN services. These services buy special network connection outside the internet that might be faster/better. All trial and error since you still need to use the internet to get to these services.

What may happen though is you see no issues at all no matter where you ping. This means the game is telling lies. Most games do not use actual ping commands. What you can see for example is a game get stuck in some video rendering process. When it gets done it checks for its "ping" response. What happens is many games do not actually keep track of when the response packet was placed in the buffer they only calculate the time based on when they look at the buffer. So the data could have been sitting there all the time it was doing something else but it will blame all the delay on the network. This is why you see people say they fixed their ping times by changing video settings. Makes no sense because the video screen image never goes over the network.

This is why I said you really hope you see problems on your connection to your ISP everything else gets very messy to fix.

 

[Flayed]

just a thought have you tried a different cable? When I had packet loss a while ago it turned out I had inadvertently damaged my ethernet cable.

 

[hypexo]

Maybe gets very complex to find the true cause sometimes.

Try leaving a ping run to 8.8.8.8. Problem is this just tells you if you have a good path between your house and google does not really tell you about the game company.

You could in theory ping the game servers but most times these are complex server farms and not single devices. Many game companies also block ping commands to their servers. Lots of poor losers in online games that would use ping commands as denial of service attacks to affect the game company and other players.

You in many ways hope this is not your issue. You have almost no options to fix any of this stuff. The only thing you can even think to try to fix issue outside your ISP is to use one of the gamer VPN services. These services buy special network connection outside the internet that might be faster/better. All trial and error since you still need to use the internet to get to these services.

What may happen though is you see no issues at all no matter where you ping. This means the game is telling lies. Most games do not use actual ping commands. What you can see for example is a game get stuck in some video rendering process. When it gets done it checks for its "ping" response. What happens is many games do not actually keep track of when the response packet was placed in the buffer they only calculate the time based on when they look at the buffer. So the data could have been sitting there all the time it was doing something else but it will blame all the delay on the network. This is why you see people say they fixed their ping times by changing video settings. Makes no sense because the video screen image never goes over the network.

This is why I said you really hope you see problems on your connection to your ISP everything else gets very messy to fix.

do you know if having no router could be the problem of these small spikes. I also kinda live like 5-10 ish mins out of town so i maybe feel like thats the problem

just a thought have you tried a different cable? When I had packet loss a while ago it turned out I had inadvertently damaged my ethernet cable.

yes the cable wasnt the problem i alr tried most of the small fixes so far from what i know of

 

[bill001g]

Unless you changed something since your trace you posted you have a router. Now maybe it is a router and modem in same box.

It would be extremely rare to not have a router, you would only be able to use a single device in your house. In some ways if you did not have a router it would be 1 less thing to be concerned about.

How far you are out of town make almost no difference. Almost any kind of wire coming to your house can not go very far, maybe a couple miles maximum. Everything gets converted to fiber normally fairly close to your house and then distance becomes some percentage of the speed of light.

BUT none of that matters.

The testing you have done show that you get no ping loss on your internet connection even though your game claims other wise.

All traffic to both the device you ping and the game server are using the same cables to your house and the same router in your house. If either of those was the cause both would see issues at the same time.

The key now is to find out what is different between those types of traffic. Be aware it is not uncommon for these type of issue to actually be bugs in the games or your video drivers.

 

[hypexo]

Unless you changed something since your trace you posted you have a router. Now maybe it is a router and modem in same box.

It would be extremely rare to not have a router, you would only be able to use a single device in your house. In some ways if you did not have a router it would be 1 less thing to be concerned about.

How far you are out of town make almost no difference. Almost any kind of wire coming to your house can not go very far, maybe a couple miles maximum. Everything gets converted to fiber normally fairly close to your house and then distance becomes some percentage of the speed of light.

BUT none of that matters.

The testing you have done show that you get no ping loss on your internet connection even though your game claims other wise.

All traffic to both the device you ping and the game server are using the same cables to your house and the same router in your house. If either of those was the cause both would see issues at the same time.

The key now is to find out what is different between those types of traffic. Be aware it is not uncommon for these type of issue to actually be bugs in the games or your video drivers.

im pretty sure its the wires theres no way to fix that right

 

[Ralston18]

To start with you must be able to demonstrate that it is "the wires".

You do that by swapping in long, known working (at speed, no spikes or packet loss) cables.

Usually that sort of testing involves running long Ethernet cables about the house from Point A to Point B etc...

You need to be methodical and allow enough time for each test run to get a good "sampling". Especially with intermittent problems.

If the problems stop then it is indeed likely that the issue is along the actual wire path from Point A to Point B that you bypassed.

Then, within that path you can take a closer look at cable run (hopefully), cable terminations, and wall jacks.

Stringing test cables about is not always a viable option if there are kids, pets, senior citizens, and just about anyone around who could get tripped and/or cause damage to the test cable.

As for a specific fix that would be a TBD. A poorly terminated wall jack is one thing. A damaged Ethernet cable behind the drywall is another. Or maybe even substandard cable was run in the walls.

Make note of what is printed along the length of any network cables you can find and see.

Does the house have a patch panel and wall jacks? Some photographs may prove helpful.

Post photographs here via imgur (www.imgur.com).

 

[hypexo]

To start with you must be able to demonstrate that it is "the wires".

You do that by swapping in long, known working (at speed, no spikes or packet loss) cables.

Usually that sort of testing involves running long Ethernet cables about the house from Point A to Point B etc...

You need to be methodical and allow enough time for each test run to get a good "sampling". Especially with intermittent problems.

If the problems stop then it is indeed likely that the issue is along the actual wire path from Point A to Point B that you bypassed.

Then, within that path you can take a closer look at cable run (hopefully), cable terminations, and wall jacks.

Stringing test cables about is not always a viable option if there are kids, pets, senior citizens, and just about anyone around who could get tripped and/or cause damage to the test cable.

As for a specific fix that would be a TBD. A poorly terminated wall jack is one thing. A damaged Ethernet cable behind the drywall is another. Or maybe even substandard cable was run in the walls.

Make note of what is printed along the length of any network cables you can find and see.

Does the house have a patch panel and wall jacks? Some photographs may prove helpful.

Post photographs here via imgur (www.imgur.com).

i meant the wires coming to my house not my ethernet wire sorry if that wasnt clear

 

[Ralston18]

Has IPv6 been diasbled as has been suggested?

Make and model modem?

Only two devices in your house?

Most home networks are much like the following line diagram:

ISP === (coax, DSL, fiber) ===> Modem ---->[WAN Port] Router [LAN Port] ----> [LAN Port] Office Wifi Access Point ~~~~> Wireless network devices

With other Router LAN ports -----> Wired network devices.

Edit and correct the above line diagram to represent your home network.

Include make and model information for the devices shown. Include other devices not shown in the line diagram.

 

[hypexo]

Has IPv6 been diasbled as has been suggested?

Make and model modem?

Only two devices in your house?

Most home networks are much like the following line diagram:

ISP === (coax, DSL, fiber) ===> Modem ---->[WAN Port] Router [LAN Port] ----> [LAN Port] Office Wifi Access Point ~~~~> Wireless network devices

With other Router LAN ports -----> Wired network devices.

Edit and correct the above line diagram to represent your home network.

Include make and model information for the devices shown. Include other devices not shown in the line diagram.

Brand: TECHNICOLOR
Model: CGM4331COM
^cox modem

ISP= COX

No router

also yes ipv6 was disabled

 

[Ralston18]

This modem/router?

https://fccid.io/G954331X/User-Manual/User-Manual-4382073.pdf

Check the Ethernet Status LEDs per pages 13,14, and 15.

Watch for changes when packet losses are occuring.

And you are able to use a browser to log directly into the modem/router via 192.168.0.1 - correct?

IPv6 has been disabled = "check".

Also try changing the DNS Servers to Google at 8.8.8.8 and 8.8.4.4

 

[hypexo]

This modem/router?

https://fccid.io/G954331X/User-Manual/User-Manual-4382073.pdf

Check the Ethernet Status LEDs per pages 13,14, and 15.

Watch for changes when packet losses are occuring.

And you are able to use a browser to log directly into the modem/router via 192.168.0.1 - correct?

IPv6 has been disabled = "check".

Also try changing the DNS Servers to Google at 8.8.8.8 and 8.8.4.4

i did both of those through my internet settings on my pc not through the

192.168.0.1