Typical ping reports:
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=0. time=172. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=1. time=146. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=2. time=143. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=3. time=132. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=4. time=131. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=5. time=129. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=6. time=127. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=7. time=130. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=8. time=126. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=9. time=122. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=10. time=123. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=11. time=123. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=12. time=124. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=13. time=123. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=14. time=121. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=15. time=125. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=16. time=3116. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=17. time=2130. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=18. time=1141. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=19. time=289. ms
64 bytes from dialup-68.nic.com (204.141.60.68): icmp_seq=20. time=117. ms
He claims the 1,000 through 3,000 ms ping times never
occur with our competitor USR based ISP.
Random sample shows ISDN connections have consistant low latency
and most modem connects have consistant low latency. I'm
lost as to where to begin with this problem
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.