Ping localhost results with inconsistent results (but never less than 1ms)

I have come across a few machines in recent times that are getting inconsistent ping reponses from localhost.  this includes machines with brand new installs.

On a windows 8 machine I note the localhost ping is consistently longer than pinging the onsite router.

Anyone have any thoughts on what could be the cause?
benfixitAsked:
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.

benfixitAuthor Commented:
turns out it was malwarebytes.. Standard behavour when monitoring!
0

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
AkinsdNetwork AdministratorCommented:
Are these doamain computers

By localhost, I'm assuming you're running the following command
C:\Users\Owner>ping localhost

Pinging Owner.test.local [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

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

Take note of the ip address the name resolves to. If ::1, it's using ipv6.  If 127.0.0.1, its using ipv4.
You can force the ping to either use ipv6 or ipv4 by appending the applicable switch


C:\Users\Owner>ping -4 localhost

Pinging Owner.test.local [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

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


C:\Users\Owner>ping -6 localhost

Pinging Owner.test.local [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

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

I'm adding the following just to shed more light.

Ping response time between two hosts connected to a switch =

1. Processing time for host A to package and send echo requests
2. Time it takes for the packets to get to the switch
3. Time it takes for the switch to process the packet and forward it
4. Time it takes for the packet to get to Host B
5. Time it takes host A to process and reply to the request.
6. Travel time back to Switch
7. Processing time on switch
8. Time it takes to get back to Host A
9. Processing time on Host A
 
Also
0
benfixitAuthor Commented:
100% correct
0
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.