Erratic ping response time

This happen in the LAN of a small company
I am responsible for IT with a colleague
Since a couple of months (nothing special changed since then), two PC gives erratic response to ping
I mean, figures like 1ms then 300, 100 200, 1 , 35 etc...
Both PC are cables to the same switch
When I unplug on cable an plug it into my laptop (same OS all, Windows 7), then I get 1ms forever, excellent.
What shell I check to find the "guilty" ?
LVL 1
LeTayAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LeTayAuthor Commented:
More info
Same problem on a third PC, located in the same area
I moved one of these guilty PC in another area where equivalent PC (same box, same OS) are connected to the LAN and where the ping is OK.
For the guilty PC, the problem is still there
LeTayAuthor Commented:
More info
Here the result of not working well ping (french, sorry)

Envoi d'une requˆte 'Ping'  192.168.1.5 avec 32 octets de donn‚esÿ:
R‚ponse de 192.168.1.5ÿ: octets=32 temps=63 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps<1ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps<1ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps<1ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps<1ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps<1ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps<1ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=545 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=140 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=343 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=243 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=156 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=358 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=3 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=65 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=390 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=592 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=187 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=100 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=608 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=165 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=167 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=31 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=30 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=420 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=62 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=265 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=467 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=62 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=265 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=467 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=62 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=265 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=468 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=62 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=265 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=467 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=62 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=265 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=468 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=62 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps<1ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=467 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=62 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=265 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=467 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=62 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=228 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=483 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=77 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=9 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=87 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=109 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=296 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=514 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=109 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=311 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=118 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=47 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=18 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=278 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=156 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=199 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=25 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=90 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=130 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=15 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=218 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=421 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=15 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=218 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=109 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=15 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=218 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=421 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=15 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=218 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=421 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=15 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=218 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=421 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=15 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=171 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps<1ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=15 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=218 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=421 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=15 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=218 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=275 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=31 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=233 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=405 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=31 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=234 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=436 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=14 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=249 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=452 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=46 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=249 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=452 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=46 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=249 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=452 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=46 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=249 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=452 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=46 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=249 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=319 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=62 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=36 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=147 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=93 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=296 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=489 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=109 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=311 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=514 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=109 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=312 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=89 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=124 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=327 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=530 ms TTL=128
R‚ponse de 192.168.1.5ÿ: octets=32 temps=124 ms TTL=128

Statistiques Ping pour 192.168.1.5:
    Paquetsÿ: envoy‚s = 127, re‡us = 127, perdus = 0 (perte 0%),
Dur‚e approximative des boucles en millisecondes :
    Minimum = 0ms, Maximum = 608ms, Moyenne = 206m
LeTayAuthor Commented:
Additional info : as can be seen in the trace above, the first pings (5 to 15) are (always) excellent then the degradation occurs.
If I restart a new ping sequence just after another one, then it is degraded directly
OWASP Proactive Controls

Learn the most important control and control categories that every architect and developer should include in their projects.

Cris HannaSr IT Support EngineerCommented:
Sounds like bad switch
You said if you move to a different area ...is that a different switch?
Bill BachPresident and Btrieve GuruCommented:
Try updating the NIC driver, or perhaps even replace the NIC altogether.  We've seen the bulk of the issues on the RealTek NIC cards, for whatever that is worth....

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LeTayAuthor Commented:
Same switch used everywhere
Can the problem be related to speed ?
Switch is gigabits, cards not
What is strange is that the problem was not there before
Users do not remember when the problem appeared, but it may be when we replaced the switch, in decembr 2015
Cris HannaSr IT Support EngineerCommented:
First I would look at is updating the NICK drivers for the problem PC's
Davis McCarnOwnerCommented:
I take it that 192.168.1.5 is a "server" of some sort?
What happens if you ping an outside ip, like Google?
LeTayAuthor Commented:
Yes, internal server
Will try pinging outside ...
LeTayAuthor Commented:
Pinging outside gives excellent results ...
So ?
Davis McCarnOwnerCommented:
Either the server is busy as h*ck, something on your network is chewing up traffic, that user has an infection, or the switch(es) are having issues.  Because switches are semi intelligent, I'd suggest cycling their power so they rebuild their internal ip tables.  After that, current ports ( http://www.nirsoft.net/utils/cports.html ) can be very useful to reveal processes that should not be running which should be run on both the server and the affected workstation(s).  Pingplotter free is also a visual traceroute which I would point at the server to reveal packet loss (PL%); though, I'd only go for replacement after repowering the switches. https://www.pingplotter.com/freeware.html
LeTayAuthor Commented:
Not a problem of infection I think as several PCs are concerned.
Will try what you suggest
LeTayAuthor Commented:
NIC card upgrade is the solution !
Thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.