[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Ping Results



What looks bad about it? The last ping didn't return because you truncated
the request before the ICMP traffic could return on seq4.

Regards,

- John

  --------------------------------------------------------------
  John Shireley                 Desk: 317.251.5252, ext. 105
  Voyager Web Hosting           Mobile: 317.710.7678
  A CoreComm Company		Yahoo: jshirele
  john.shireley@xxxxxxxxxxx     ICQ: 71529750 Fax: 317.726.5239
  --------------------------------------------------------------


On Wed, 29 Nov 2000, George Ewing wrote:

> Guys,
> 
> I'm getting following when I ping to my server..... can someone explain how bad this is?
> 
> PING top-host.net (212.67.201.106) from 207.71.44.100 : 56(84) bytes of data.
> 64 bytes from ns.top-host.net (212.67.201.106): icmp_seq=0 ttl=238 time=180.3 ms
> 64 bytes from ns.top-host.net (212.67.201.106): icmp_seq=1 ttl=238 time=165.8 ms
> 64 bytes from ns.top-host.net (212.67.201.106): icmp_seq=2 ttl=238 time=153.8 ms
> 64 bytes from ns.top-host.net (212.67.201.106): icmp_seq=3 ttl=238 time=189.7 ms
> 
> --- top-host.net ping statistics ---
> 5 packets transmitted, 4 packets received, 20% packet loss
> round-trip min/avg/max = 153.8/172.4/189.7 ms
> 
> 
> 
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>