mcnuttlaw
asked on
Ping High Millisecond
I'm troubleshooting a slow connection to my home office.
Pinging the domain controller returns 92 ms.
Is this too high? What is the normal return in ms?
I am connected to the home office via MPLS circuit.
Pinging the domain controller returns 92 ms.
Is this too high? What is the normal return in ms?
I am connected to the home office via MPLS circuit.
Try contious ping - to for 10 minutes to get the clear latency
In the LAN it should be max less than MSs, in the WAN 90 ms is good latency
In the LAN it should be max less than MSs, in the WAN 90 ms is good latency
is it always 92 ms? Through MPLS circuit 92 ms is quite high value, but it defense on line usage. check circuit graphs. What is the through put of your MPLS.
Check your network for malware virus. and you can check your home office network using a tool like wire shark
Better you contact your ISP and ask them to trouble shoot.
Check your network for malware virus. and you can check your home office network using a tool like wire shark
Better you contact your ISP and ask them to trouble shoot.
There are a lot of factors that can impact response times.
If your connecting from another country that would probably be about normal.
if you are connecting from another office 1 or 2 hops away that is fairly poor response times.
There are bandwidth testing tools and diagnostic tools that can be used to better troubleshoot latency than ping.
You can use Trace route or even download a tool such as iperf to get better idea of speeds.
As the previous poster said you can contact the MPLS provider and ask them to troubleshoot the line for you if you feel the connection is not meeting the contracted performance.
If your connecting from another country that would probably be about normal.
if you are connecting from another office 1 or 2 hops away that is fairly poor response times.
There are bandwidth testing tools and diagnostic tools that can be used to better troubleshoot latency than ping.
You can use Trace route or even download a tool such as iperf to get better idea of speeds.
As the previous poster said you can contact the MPLS provider and ask them to troubleshoot the line for you if you feel the connection is not meeting the contracted performance.
ASKER
I did a pathping and it did 7 hops and failed at the 6th hop.
Lost/Sent = 100/100
Total time is 95ms
Could the 6th hop be the culprit?
Lost/Sent = 100/100
Total time is 95ms
Could the 6th hop be the culprit?
Did the sixth hop end up as "Request timed out"?
Some routers are not configured to respond to ICMP requests (pings).
Similar to pathping:
https://www.inmotionhosting.com/support/website/how-to/read-traceroute
Some routers are not configured to respond to ICMP requests (pings).
Similar to pathping:
https://www.inmotionhosting.com/support/website/how-to/read-traceroute
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was a carrier issue.
pingpath info:
https://technet.microsoft.com/en-us/library/hh831799(v=ws.11).aspx