I am configuring an NTP server running Ubuntu 14 remotely, but it is not reaching to any timeservers, so I tried to troubleshoot it and discovered that the server is not getting ping responses from any host on the Internet. Example google.com but it is pinging to localhost. All inbound and outbound rules in security group and ACl is allowed. UFW is inactive and no rule in iptables.

And yes, I am able to ssh to this server, so it was on the network.

Output of ping

ping google.com
PING google.com ( 56(84) bytes of data.
--- google.com ping statistics ---
59 packets transmitted, 0 received, 100% packet loss, time 58007ms

closed as unclear what you're asking by Stephen Rauch, countermode, Archemar, Stephen Kitt, Jeff Schaller Jun 23 '17 at 16:07

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • show actual output of ping. Even the failure messages, it has several of them (and a mode where no error message is seen), it's so useful :). tell us if you are accessing the server using SSH successfully already, or if instead you are using some access method which does not require network. My first guess was DNS; if ping shows failure to resolve host then show cat /etc/resolv.conf. getent ahosts google.com can also be useful to confirm failure. – sourcejedi Jun 23 '17 at 10:07
  • If it is not dns, then sudo traceroute -T google.com can be useful. – sourcejedi Jun 23 '17 at 10:12
  • always share the specific error messages, if you can see them. Or if there is no message. Or if the program sits there doing nothing despite you waiting 60 seconds, say that. – sourcejedi Jun 23 '17 at 10:13
  • Probably you dont have the default gateway configured on the server. Try something like "route" without any arguments and this will show your default gateway. – Luciano Andress Martini Jun 23 '17 at 20:14
  • If you're really got no rules in iptables (it would be nice to know - iptables -nvL please) then Amazon has set you up with a firewall that allows inbound ssh and nothing else. – roaima Jun 23 '17 at 21:17