Question Getting bad speeds and ping with ethernet cable

[kanewolf]

I might be doing something wrong, but when i am trying to install new drivers it says ''device not found'' but i have made sure to choose the right file for the update but the problem is still occuring.

https://imgur.com/1hzhrJN

View: https://imgur.com/1hzhrJN

https://imgur.com/b2FYG2X

View: https://imgur.com/b2FYG2X

I would extract the drivers and use the device manager in Windows to do a manual update.

 

[AxelSSS]

I would extract the drivers and use the device manager in Windows to do a manual update.

I am sure that i have done it exactly as you have described it to me, but i am still not allowed to update it because windows have decided i have the best drivers already downloaded??

https://imgur.com/Gid8DrM

View: https://imgur.com/Gid8DrM

 

[Ralston18]

@AxelSSS

Your Test-NetConnection results are revealing:

Google = 29 ms
Cloudfare = 11 ms

Tomorrow's test results could be reversed.....

I am not sure about the meaning of "a real drop in ping would be around 12-10 ms".

Your expections perhaps being Google at 17 ms and Cloudfare at 1 ms or <1 ms.

To fully and (hopefully) properly gather more data you would need to run many more tests and work on understanding what the results may or may not be revealing. That is exactly what I am trying to do.

However, the thread's discussion has shifted into expectations, drivers, and updates.

Once there has been some resolution regarding the bad Ethernet cables and drivers etc. there may or may not be some need for additional testing.

You are in good hands with respect to those matters.

Test-NetConnection becoming just another diagnostic tool in the toolbox to keep in mind.

 

[AxelSSS]

@AxelSSS

Your Test-NetConnection results are revealing:

Google = 29 ms
Cloudfare = 11 ms

Tomorrow's test results could be reversed.....

I am not sure about the meaning of "a real drop in ping would be around 12-10 ms".

Your expections perhaps being Google at 17 ms and Cloudfare at 1 ms or <1 ms.

To fully and (hopefully) properly gather more data you would need to run many more tests and work on understanding what the results may or may not be revealing. That is exactly what I am trying to do.

However, the thread's discussion has shifted into expectations, drivers, and updates.

Once there has been some resolution regarding the bad Ethernet cables and drivers etc. there may or may not be some need for additional testing.

You are in good hands with respect to those matters.

Test-NetConnection becoming just another diagnostic tool in the toolbox to keep in mind.

I completely understand the need for me to cooperate with all of the tests that you all need me to run, and i will continue to run all of the test that are needed so you guys can help me to resolve my problem,