Jump to content
Sign in to follow this  
Followers 0
Amer

Reply Ttl Expired From 58.27.xxx.xxx

By Amer, in Internet

Recommended Posts

Amer    0

Amer
Posted (edited)
sejak akhir-akhir ni aku perasan bila aku ping local sites, selalu dapat "Reply TTL expired from 58.27.104.153 .." patut lah banyak sites tu loading tak sekerat je, tak habis. aku nak tahu samada aku sorang je ke kena masalah ni atau korang pun kena jugak

cuba ping sites ni dan tengok ada tak dia kata "Reply TTL expired from 58.27.xxx.xxx" atau "Reply from 58.27.xxx.xxx: TTL expired in transit."

1. lowyat.net
2. bolehvpn.net
3. scukz.com
4. nst.com.my
5. ittutor.net

ni aku punya

CODE
Pinging lowyat.net [202.190.197.143] with 32 bytes of data from [192.168.1.10]:

Reply from 202.190.197.143: bytes=32 time 32.32 ms, TTL=53, Hop=11, Jitter=0.00 ms
Reply from 202.190.197.143: bytes=32 time 33.24 ms, TTL=53, Hop=11, Jitter=0.06 ms
Reply from 202.190.197.143: bytes=32 time 32.82 ms, TTL=53, Hop=11, Jitter=0.08 ms
Reply TTL expired from 58.27.104.157: bytes=28 time 26.21 ms, TTL=252, Hop=3, Jitter=0.49 ms
Reply from 202.190.197.143: bytes=32 time 32.41 ms, TTL=53, Hop=11, Jitter=0.85 ms
Reply TTL expired from 58.27.104.157: bytes=28 time 27.11 ms, TTL=252, Hop=3, Jitter=1.12 ms
Reply TTL expired from 58.27.104.157: bytes=28 time 26.63 ms, TTL=252, Hop=3, Jitter=1.08 ms
Reply TTL expired from 58.27.104.157: bytes=28 time 26.18 ms, TTL=252, Hop=3, Jitter=1.04 ms
Reply TTL expired from 58.27.104.157: bytes=28 time 25.47 ms, TTL=252, Hop=3, Jitter=1.02 ms
Reply from 202.190.197.143: bytes=32 time 32.64 ms, TTL=53, Hop=11, Jitter=1.41 ms
Reply from 202.190.197.143: bytes=32 time 33.00 ms, TTL=53, Hop=11, Jitter=1.34 ms
Reply from 202.190.197.143: bytes=32 time 33.28 ms, TTL=53, Hop=11, Jitter=1.28 ms
Reply from 202.190.197.143: bytes=32 time 32.87 ms, TTL=53, Hop=11, Jitter=1.22 ms
Reply from 202.190.197.143: bytes=32 time 33.00 ms, TTL=53, Hop=11, Jitter=1.15 ms
Reply from 202.190.197.143: bytes=32 time 33.07 ms, TTL=53, Hop=11, Jitter=1.09 ms
Reply TTL expired from 58.27.104.157: bytes=28 time 26.75 ms, TTL=252, Hop=3, Jitter=1.41 ms
Reply from 202.190.197.143: bytes=32 time 32.47 ms, TTL=53, Hop=11, Jitter=1.68 ms
Reply TTL expired from 58.27.104.157: bytes=28 time 26.52 ms, TTL=252, Hop=3, Jitter=1.95 ms
Reply from 202.190.197.143: bytes=32 time 32.08 ms, TTL=53, Hop=11, Jitter=2.17 ms
Reply from 202.190.197.143: bytes=32 time 32.68 ms, TTL=53, Hop=11, Jitter=2.08 ms

Ping statistics for 202.190.197.143
  Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 25.47ms, Maximum =  33.28ms, Average =  30.54ms, Jitter Statistical = 3.14ms



aku duduk kat kelantan, jadi mula-mula aku suspek masalah ni sebab banjir kot..tapi bila aku tanya member lain yg duduk dia area pantai timur, diorang kata takda masalah ni. ada sorang member aku cakap TTL ip 58.27.xxx tu tinggi sangat dia set (ttl 252) sebab tu jadi gini. sapa yg set tak tahu lah..dah seminggu lebih dah masalah ni.



wacko.gif Edited by aMer

Share this post

Link to post
Share on other sites

memito    0

memito
Posted
aku lebih kurang mcm ko jugak...baru aku perasan hari ni...dlm 2 minggu lps aku ping lowyat.net ..ok je..x de time out..skrg lain dah...gpun ada jugak website luar negara x leh masuk....connection interrupted la...mcm2 la....tp kdg2 leh pulak masuk...

Share this post

Link to post
Share on other sites

Yondaime    0

Yondaime
Posted
QUOTE
C:\Documents and Settings\xxx>ping lowyat.net

Pinging lowyat.net [202.190.197.143] with 32 bytes of data:

Reply from 58.27.104.153: TTL expired in transit.
Reply from 202.190.197.143: bytes=32 time=22ms TTL=55
Reply from 58.27.104.153: TTL expired in transit.
Reply from 202.190.197.143: bytes=32 time=21ms TTL=55

Ping statistics for 202.190.197.143:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 22ms, Average = 10ms

C:\Documents and Settings\xxx>ping jiwang.org

Pinging jiwang.org [202.75.48.9] with 32 bytes of data:

Reply from 202.75.48.9: bytes=32 time=26ms TTL=52
Reply from 202.75.48.9: bytes=32 time=25ms TTL=52
Reply from 58.27.104.153: TTL expired in transit.
Reply from 202.75.48.9: bytes=32 time=25ms TTL=52

Ping statistics for 202.75.48.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 26ms, Average = 19ms

C:\Documents and Settings\xxx>ping ittutor.net

Pinging ittutor.net [202.71.97.83] with 32 bytes of data:

Reply from 202.71.97.83: bytes=32 time=28ms TTL=54
Reply from 202.71.97.83: bytes=32 time=29ms TTL=54
Reply from 202.71.97.83: bytes=32 time=28ms TTL=54
Reply from 202.71.97.83: bytes=32 time=28ms TTL=54

Ping statistics for 202.71.97.83:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 29ms, Average = 28ms

C:\Documents and Settings\xxx>ping jiwang.org

Pinging jiwang.org [202.75.48.9] with 32 bytes of data:

Reply from 58.27.104.153: TTL expired in transit.
Reply from 202.75.48.9: bytes=32 time=24ms TTL=52
Reply from 58.27.104.153: TTL expired in transit.
Reply from 202.75.48.9: bytes=32 time=24ms TTL=52

Ping statistics for 202.75.48.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 24ms, Average = 12ms

C:\Documents and Settings\xxx>ping tm.net.my
^C
C:\Documents and Settings\xxx>ping www.tm.net.my

Pinging www.3dns.tm.net.my [202.71.97.48] with 32 bytes of data:

Reply from 202.71.97.48: bytes=32 time=64ms TTL=118
Reply from 202.71.97.48: bytes=32 time=50ms TTL=118
Reply from 202.71.97.48: bytes=32 time=28ms TTL=118
Reply from 202.71.97.48: bytes=32 time=25ms TTL=118

Ping statistics for 202.71.97.48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 64ms, Average = 41ms

C:\Documents and Settings\xxx>
C:\Documents and Settings\xxx>ping www.tm.net.my

Pinging www.3dns.tm.net.my [202.71.97.48] with 32 bytes of data:

Reply from 202.71.97.48: bytes=32 time=28ms TTL=118
Reply from 202.71.97.48: bytes=32 time=25ms TTL=118
Reply from 202.71.97.48: bytes=32 time=28ms TTL=118
Reply from 202.71.97.48: bytes=32 time=29ms TTL=118

Ping statistics for 202.71.97.48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 29ms, Average = 27ms

C:\Documents and Settings\xxx>ping www.tm.net.my

Pinging www.3dns.tm.net.my [202.71.97.48] with 32 bytes of data:

Reply from 202.71.97.48: bytes=32 time=26ms TTL=118
Reply from 202.71.97.48: bytes=32 time=29ms TTL=118
Reply from 202.71.97.48: bytes=32 time=25ms TTL=118
Reply from 202.71.97.48: bytes=32 time=29ms TTL=118

Ping statistics for 202.71.97.48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 29ms, Average = 27ms

C:\Documents and Settings\xxx>ping www.tm.net.my

Pinging www.3dns.tm.net.my [202.71.97.48] with 32 bytes of data:

Reply from 202.71.97.48: bytes=32 time=28ms TTL=118
Reply from 202.71.97.48: bytes=32 time=25ms TTL=118
Reply from 202.71.97.48: bytes=32 time=29ms TTL=118
Reply from 202.71.97.48: bytes=32 time=36ms TTL=118

Ping statistics for 202.71.97.48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 36ms, Average = 29ms
Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=179ms TTL=246
Reply from 202.188.0.133: bytes=32 time=181ms TTL=246
Reply from 202.188.0.133: bytes=32 time=186ms TTL=246
Request timed out.

Ping statistics for 202.188.0.133:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 179ms, Maximum = 186ms, Average = 182ms

C:\Documents and Settings\Deuterium>ping 202.188.0.133

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=173ms TTL=246
Reply from 202.188.0.133: bytes=32 time=176ms TTL=246
Reply from 202.188.0.133: bytes=32 time=177ms TTL=246
Reply from 202.188.0.133: bytes=32 time=173ms TTL=246

Ping statistics for 202.188.0.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 177ms, Average = 174ms


aku pom kene

Dah report tapi hampeh huh.gif

Share this post

Link to post
Share on other sites

FryShadow    90

FryShadow
Posted
em.. aku rasa TTL ni time utk packet (cnth packet ping) yang akan traverse through the network, kalau abis masa dia akan drop the packet sbb tu kuar "Reply TTL expired from 58.27.104.157: bytes=28 time 27.11 ms, TTL=252, Hop=3, Jitter=1.12 ms"

so TTL akan ditentukan oleh connection medium tu sndiri n takde sape yang set kan biggrin.gif

as long "time=173ms" dan "time=9.34 ms" yg lain2 ni masih dikira ok lagi dan rasa takde masalah sgt.. kalau lebih 300 mungkin ada prob pada connection

kalau local pn ada jitter mmg masalah streamyx tu sndiri smile.gif biggrin.gif

"sayang streamyx" tongue.gif

Share this post

Link to post
Share on other sites

prontoxp    2

prontoxp
Posted
Kalau hal mcm tu mmg connection problem... kalau dah report dok diam2 ... tau la diaorg buat..

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
Sign in to follow this  
Followers 0
Go To Topic Listing
×
×
  • Create New...