Ping response time

I have few servers that respond to ping and have response time over 200ms. Can it be an issue and is it something that we need to be concerned with? If yes, what would we need to do in order to improve the response time?

IPV4Address      ResponseTime      3681      269      193      95      60      59      53      39      30      28      27      12      2

THank you very much.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

JohnBusiness Consultant (Owner)Commented:
Are the servers local or over a VPN?

Local ping time for me is 1 ms.  Your times are long for local.

Please describe the setup a bit.
creative555Author Commented:
Thank you John!
The servers are local too but we host DNS somewhere else. So we don't manage DNS in house. So, what we do is just put the DNS servers in TCP/IP settings. Should we be concerned that the ping response time is so large?

Is this issue with hosted DNS?

Let me know.
Assuming these are all located (physically) in a local area (eg: same building) and the links between them are commercial grade (ie: not running over twisted pair with line drivers or similar)  then you should expect a response time under 10ms (all other things being equal) so I think the first three, at least, are definitely worth investigating. The 3681 is high and could lead to timeout of network connections - depending on what its role is - so start there and you may find if you resolve that the others improve.

However the reasons for network lag are many and notoriously difficult to troubleshoot without some expensive gear to help you monitor what's going on and obviously if the server is in production environment then you can't go fiddling without agreement from the users.

Here's some basic things to consider; you need to think about how you might be able to test these in your environment:

- Server load, if the server is busy generally (CPU usage) and its function requires a lot of network use then it may simply be overloaded and unable to respond.
- Chatter from a faulty card or port, this is a situation where a hardware/software fault (possibly in another network element) is constantly sending spurious information across the network
- Denial of Service attack, unlikely in a private network but essentially a malicious form of chatter deliberately injected to prevent a server responding to actual requests
- misconfigured nets/subnets/routing tables

without a hardware sniffer (the expensive kit I mentioned) your best option is to look at each network element and investigate what might be wrong so starting at
- what do the server logs say about network traffic?
- does replacing drop cable and/or switching to a different router port fix the issue?
- if you connect to a different router does it improve?
- is the server overloaded (eg: handling 10,000 requests when its only configured for 5000) or runnning a CPU or memory intensive task that prevents it from responding?

I'm sure other experts will have a similar list of things to try!
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

JohnBusiness Consultant (Owner)Commented:
Hosted DNS is probably what is slowing you down. I expect that could slow down server browsing as well. DNS on your server is easy to do, so you may wish to re-consider.

Also let us know about the above question about network traffic.

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
Fred MarshallPrincipalCommented:
It would likely be informative to see a traceroute for the addresses with long times.  That should tell you where the delays are.  That could help in your analysis.
JoeSystems AdministratorCommented:
I don't think that it would be DNS since you are pinging the IP address and not the servername so there is no name resolution. I do recommend local DNS though. Are you experiencing any other performance issues with these servers?
JohnBusiness Consultant (Owner)Commented:
I just pinged my own home computer across the internet over a secure permanent tunnel from where I am and got 70 ms average. Just a reference point.
Fred MarshallPrincipalCommented:
If you're interested in what's "typical", you might traceroute a few well-known sites to see the results *per hop*.
creative555Author Commented:
Thank you all for great answers! Hosted DNS is the problem. But you also helped with the details on how to troubleshoot and find out what what is the issue.
madunix (Fadi SODAH)Chief Information Security Officer Commented:
I do netpipe for latency and ping for packet loss, notice: Latency , Loss and Jitter, these parameters mainly depend on the Quality and utilization of the links
Will SzymkowskiSenior Solution ArchitectCommented:
This has nothing to do with DNS. You are pinging the IP address. If your ping ms is high this is typically an issue with the routing path that it is taking to get to the destination.

Another thing it could be is the router at the site where you are pinging the machine. Might need to be rebooted etc.

DNS is also recommended to be local (if possible) however having DNS over a site-to-site VPN it possible with very little overhead.

Put this in perspective, I have a site in Candada and another site in Vietnam and my ping ms to Vietnam data center is about 300ms. So that is over about 15 hops. When you are getting 300+ ms and it is not geographically far away it is usually due to a routing issue or a router malfunction.

Will SzymkowskiSenior Solution ArchitectCommented:
Closed it too quickly.

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

From novice to tech pro — start learning today.