Question Network Speed via ethernet on Desktop PC is terrible ?

[koberulz]

How bad it is varies. Sometimes I can't even load the speed test site. Other times it reports 40 down/20 up, which is what I'm paying for, but when I'm uploading a 12GB video to YouTube, which in the past has taken only a couple of hours, it now takes 6-7. Sometimes I just plain can't watch YouTube at all, I just get a black rectangle with a spinning circle. Other times I can watch, but only in 240p with lots of buffering. Other times...it seems fine.

Tried rebooting the PC, router, etc etc, to no avail.

It's not an internet issue, because once when it was really bad I was trying to do something on my NAS (also wired) and it took a couple of minutes just for a command prompt to load. Trying to navigate in Windows Explorer was painfully slow, and forget about trying to play any video files.

Provide us with the make and model of your router: TP-Link AC1750
- Make and model of motherboard: Gigabyte GA-H170 Gaming 3
Make and model of power supply: No idea TBH
Operating system and driver version: Win7 Pro (driver version?)

You will also need to post your ISP and connection type: I don't believe this is relevant, as the issue seems exclusive to the LAN
You will also need to post the exact number of devices connected to your router (this includes tablets, smart phones, laptops, and desktop PCs) as some routers can only handle a specific number of devices at a time: No idea? Wired, I have my desktop and a Synology DS1819+. And a powerline adapter going to an NVIDIA Shield. Wirelessly...at least two phones, a laptop, two smart TVs, several gaming consoles...but most of these (other than the phones) are off 99% of the time.
Post any and all error messages you are getting from your ISP or Windows itself: N/A


Make and model of switches and how many ports are on each switch: N/A
How many PCs and laptops are connected to the network: Wired? One PC, one NAS, one powerline adapter to an NVIDIA Shield
Whether or not a NAS (Network Attached Storage) or regular server is connected to the network
Whether or not a Wifi router is connected to the network and/or switch: I don't understand the question.
If you are using the internal LAN connection on your motherboard, a USB dongle, or external PCI card: Motherboard.

 

[rgd1101]

malware scan?
what the dns server?
what the storage?
check cpu temp?

 

[koberulz]

malware scan?

Malwarebytes is scanning daily and has been reporting clean.

what the dns server?
what the storage?

What?

check cpu temp?

50-60 C.

 

[bill001g]

So I assume other device have no issues?

So what is most strange a is are you saying it takes a long time for it launch the browser software and/or that it takes a long time for the cmd prompt screen to even let you type things it. This is very different than if the program starts but when you try to use it then it responds slowly. What happens if you unplug the network cable and then try to launch the programs is it still slow.

Maybe the resource manage will show something is overloaded. It could be cpu running at 100% or some problem with disk files. It does not sound like actual network issue.

 

[koberulz]

So what is most strange a is are you saying it takes a long time for it launch the browser software and/or that it takes a long time for the cmd prompt screen to even let you type things it. This is very different than if the program starts but when you try to use it then it responds slowly. What happens if you unplug the network cable and then try to launch the programs is it still slow.

I never mentioned launching a browser being slow?

The command prompt thing, I'd tried to launch it from a folder on my NAS via right-click in Windows Explorer. While it sat there trying to load, I managed to open a new Windows Explorer window, get to a folder on a local drive, launch the command prompt from there, do what I needed to do, and exit the command prompt. The prompt I'd launched from my NAS was still trying to load.

 

[bill001g]

Then try the standard tests. First open a cmd window and run tracert 8.8.8.8
This may nor may not show anything interesting. It is used mostly to get the IP addresses of the routers in the path.

Next run constant pings to hop 1 (your router), hop 2 (most likely the first ISP router) and the final ip 8.8.8.8

What you are mostly looking for is packet loss.

What you can also try is to disable IPv6 support in your nic setting. IPv6 for whatever reason does not perform as well as IPv4 for some people and microsoft will prefer using IPv6 over IPv4 when both are allowed.

 

[koberulz]

Then try the standard tests. First open a cmd window and run tracert 8.8.8.8
This may nor may not show anything interesting. It is used mostly to get the IP addresses of the routers in the path.

Next run constant pings to hop 1 (your router), hop 2 (most likely the first ISP router) and the final ip 8.8.8.8

What you are mostly looking for is packet loss.

I'm not sure what's good or bad in terms of a tracert result, or how to go about pinging those hops?

 

[bill001g]

Simple ping commands example

Ping 8.8.8.8 -t

 

[koberulz]

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=46ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=46ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=67ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=46ms TTL=53
Reply from 8.8.8.8: bytes=32 time=46ms TTL=53
Reply from 8.8.8.8: bytes=32 time=49ms TTL=53
Reply from 8.8.8.8: bytes=32 time=46ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=46ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=45ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2110ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2462ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2276ms TTL=53
Reply from 8.8.8.8: bytes=32 time=1516ms TTL=53
Reply from 8.8.8.8: bytes=32 time=49ms TTL=53
Reply from 8.8.8.8: bytes=32 time=1817ms TTL=53
Reply from 8.8.8.8: bytes=32 time=235ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2654ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2624ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2347ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2205ms TTL=53
Reply from 8.8.8.8: bytes=32 time=441ms TTL=53
Reply from 8.8.8.8: bytes=32 time=658ms TTL=53
Reply from 8.8.8.8: bytes=32 time=1238ms TTL=53
Reply from 8.8.8.8: bytes=32 time=1898ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2095ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2035ms TTL=53
Reply from 8.8.8.8: bytes=32 time=2089ms TTL=53
Reply from 8.8.8.8: bytes=32 time=1085ms TTL=53
Reply from 8.8.8.8: bytes=32 time=171ms TTL=53
Reply from 8.8.8.8: bytes=32 time=433ms TTL=53
Reply from 8.8.8.8: bytes=32 time=625ms TTL=53
Reply from 8.8.8.8: bytes=32 time=836ms TTL=53
Reply from 8.8.8.8: bytes=32 time=746ms TTL=53
Reply from 8.8.8.8: bytes=32 time=773ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=167ms TTL=53
Reply from 8.8.8.8: bytes=32 time=430ms TTL=53
Reply from 8.8.8.8: bytes=32 time=513ms TTL=53
Reply from 8.8.8.8: bytes=32 time=537ms TTL=53
Reply from 8.8.8.8: bytes=32 time=637ms TTL=53
Reply from 8.8.8.8: bytes=32 time=558ms TTL=53
Reply from 8.8.8.8: bytes=32 time=487ms TTL=53
Reply from 8.8.8.8: bytes=32 time=813ms TTL=53
Reply from 8.8.8.8: bytes=32 time=777ms TTL=53
Reply from 8.8.8.8: bytes=32 time=503ms TTL=53
Reply from 8.8.8.8: bytes=32 time=341ms TTL=53

Ping statistics for 8.8.8.8:
Packets: Sent = 56, Received = 55, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 2654ms, Average = 764ms

 

[bill001g]

That just show you do have a problem.

Now you must do the same for the other IP for hop 1 and hop 2.

 

[koberulz]

What IPs are those, though? That was my initial question.

 

[bill001g]

Only you can find out. What did the tracert show.

 

[koberulz]

Only you can find out. What did the tracert show.

I don't know how to find out. I'm not sure how much of the tracert is safe to post here?

 

[bill001g]

Mostly it is fine at worst someone will be able to see the ISP router nearest your house.

It should be very obvious....It has the hop numbers on the left and the IP on the right

 

[koberulz]

I was working on an image in Photoshop earlier. The image is stored on my NAS. Photoshop completely stopped responding when I tried to save it, eventually saying the location wasn't available.

Pinging hop 1:
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
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=3ms 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=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms 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=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=26ms 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=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms 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
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=4ms 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=3ms 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

Ping statistics for 192.168.0.1:
Packets: Sent = 105, Received = 105, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 26ms, Average = 0ms


Pinging hop 2:
Pinging [Hop 2] with 32 bytes of data:
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=10ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=10ms TTL=254
Reply from [Hop 2]: bytes=32 time=41ms TTL=254
Reply from [Hop 2]: bytes=32 time=12ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=12ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=10ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=10ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=15ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=19ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=10ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=11ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=22ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=13ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=10ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=9ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254
Reply from [Hop 2]: bytes=32 time=8ms TTL=254

Ping statistics for [Hop 2]:
Packets: Sent = 65, Received = 65, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 41ms, Average = 9ms

 

[bill001g]

The problem seems extremely random.

If it affects the connection to the NAS then it is not the internet so we have been down the wrong testing with the ping/tracert. The strange numbers to 8.8.8.8 made it look like the internet has issues.

I guess you could try to leave a ping run to the nas constantly in a background window.....assume the NAS will respond. When your application has issues it would be interesting to see if you also get ping loss. If you do not get ping loss to the nas when the application has issues it is more likely this is something other than a true network issue.

Going directly to the NAS means the router is acting as a simple switch so it is unlikely any issue with the router.

This leaves the pc. Looking at the motherboard you have it has a killer 2200 ethernet controller. These have a very long history of causing strange errors. Mostly it is the some software called killer suite that causes all the problems.
This one unlike other bloatware like this just uninstalling the app is not enough. You need to replace the driver with the ones that do not have the support for that software.

I had really hoped we saw the last of killer stuff after they were sold. The normal advice was to go to killer site and load what is called driver only for that chipset. It loads a driver without the extra hooks in it.
Problem is I have no idea where to tell you to look other than it might be on intels site they purchased killer. The other problem is most vendors have completely stopped any support for win7.

Now this might not be the problem at all but when I see killer stuff I tend to blame it first since it has a bad history.

So many times I would recommend you try a USB linux image boot. If this works then it tends to be some software on windows causing it. If it also has issues then it is more likely it is a actual hardware issue. Two problems I see here.
The first is this might be too advanced when it appears you have limited knowledge of some of the simple tools like tracert or ping.
The second is the linux image runs completely from the USB stick so it does not damage your windows install. It has very limited software installed so it will fit on the USB stick. It does have a web browser so you could likely do something like watch youtube which you say has issues.
It can also access your NAS but I am unsure what you could test other than some small file copies that would fit into the USB.

Maybe blindly try a new ethernet card. Your motherboard has lots of PCIE slots and a card is only about $15.

 

[koberulz]

Pinging my NAS:
Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=4ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=58ms TTL=64
Reply from 192.168.0.2: bytes=32 time=447ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=827ms TTL=64
Reply from 192.168.0.2: bytes=32 time=1290ms TTL=64
Reply from 192.168.0.2: bytes=32 time=1750ms TTL=64
Reply from 192.168.0.2: bytes=32 time=2291ms TTL=64
Reply from 192.168.0.2: bytes=32 time=3046ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.2: bytes=32 time=483ms TTL=64
Reply from 192.168.0.2: bytes=32 time=303ms TTL=64
Reply from 192.168.0.2: bytes=32 time=25ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.2:
Packets: Sent = 31, Received = 27, Lost = 4 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3046ms, Average = 389ms

 

[koberulz]

What does slow down, in terms of Windows operation, is networking control panel stuff. I've plugged my phone in and tethered it, while still connected to the WiFi, essentially allowing a WiFi connection to my PC. Went to open the Network and Sharing Center to kill off the wired connection (which will kill the NAS stuff, obviously, but I need internet right now) and it's taking forever to open. I'm also not getting the Network Setup popup or whatever it is (to choose home/public network) for the USB tether.

 

[bill001g]

That is extremely strange for ping times. Not so much the packet loss that could be the interface going down. What is more strange is ping times over 1 full second...ie over 1000ms. Where is that data being held during this time. It can't be the ethernet cable it just a piece of copper metal. It must be some buffer in the pc or maybe the NAS. Since the pc has issues to other location I would suspect the PC but I don't know anything that would delay a ping command.

Maybe the event monitor will give you a clue, did that exit in windows 7? The resource monitor might also give you a clue if there is say some process eating the cpu, that is about the only thing I can see that would affect ping since it doesn't use disk or memory.

 

[koberulz]

Event Viewer? Where would I be looking, and what for?

The issue is it's so sporadic, so it's difficult to know when to check things. Internet is pretty much constantly way slower than it should be, but every now and then it becomes basically useless...I was even getting a complete loss of connection for periods last night.

It's going down for planned maintenance later tonight, which will limit testing ability but I doubt it'll fix the problem as it seems to be somewhere between my PC and my router.

 

[bill001g]

I forget how win7 works. On the newer windows you just push the windows key and start typing in event viewer and it will find it for you.

I don't think it is your internet because you have trouble with the NAS which is in your house. Maybe testing to the NAS when the internet is down is a good thing to try. Would eliminate some internet download or something is running and you don't know about it. I suppose you could also just unplug the internet cable to do the same thing. When you test to your NAS you almost don't need a router the lan ports are acting as a simple switch. The router is only used to assign IP addresses but after they have the IPs they don't really talk to the cpu chip in your router.

The lan ports used to be connected to actual switch chip similar to the ones used in 5 ports switches. 4 you see and the 5th going to the router chip. Now days it is all on one big chip but still functions the same way.

This is such a simple function the lan ports on the router are unlikely to be the cause of your problem to the NAS.

Still the thing that is so strange about your test data are the very long ping times. Things like data loss are very common with defective hardware (mostly cables) but delays like that are some kind of software thing.

 

[koberulz]

Right, can open the Event Viewer, I just don't know what to look for within it.

 

[bill001g]

Look for something that happens around the time you see the problem. There are time stamps on the messages.

Can't even begin to tell you what to look for. There are so many things that can cause slowness.

 

[koberulz]

Windows logs? Application logs? There's a lot there.

It's also slower than it ought to be pretty much permanently, there are just also spikes where it's really bad.

 

[koberulz]

Here's an outage from the Networking tab of the Task Manager:

The RAM usage is almost entirely Waterfox.