asked on

HP Envy Laptop slowing down the company's WAN but not LAN

HP Envy laptop (Intel i7, 12GB RAM, Windows 10 Pro). Dynamic IP acquired from Server 2012R2 machine

Company moved into a new building (recently built). Server and about 7 computers connected to a DSL modem, 7mbps down, 0.5 mbps up. (Waiting for fibre on this street)

When this HP laptop is connected to the wired LAN, ping times to Google's server at 8.8.8.8 rise from a norm of about 30 mS to 1600 to 2000 mS!

This issue did not seem to exist at their old location (though they were 75mbps fibre there, so maybe it did but wasn't severe). I have removed and reinstalled the network adapter driver. No difference. pings to local PCs appear to be fine, typically <1mS.

The only change in the topography is that the 2012 R2 server is new, and it is now the DHCP server (and DNS). While this laptop is disconnected, no issues are experienced. Probably important: The same issue is experienced when the WIFI is used on the laptop instead.

Any idea of how to troubleshoot this?

ASKER CERTIFIED SOLUTION

Kimputer

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

DaveWWW

ASKER

Thanks Kimputer. And yes, since my message I have checked and seen that the ping times are bad. It seems like with this horrible DSL, there is a tipping point, because yesterday when I was observing the ping times of around 2000 on a desktop, unplugging the laptop made it go to 28 mS within a second or so. Plugging the laptop back in made them go high. But today, the tests results were not so cut-and-dried.

The DSL provider is saying that the connection is working normally, so I'm now thinking that a computer on site must be either infected, or downloading updates, etc.

Thanks again.

Kimputer

If you don't have the correct monitoring hardware, or a really old network hub, or a managed switch with port mirroring capability, I'm afraid you're back to the unplugging method of testing.

DaveWWW

ASKER

It turns out that the network was able to be brought to a crawl by several PCs streaming data to an offline backup. I resolved it by configuring the backups to run at night. Thanks.