|
贊助商連結 頁 :
[1]
2
stuart 2008-09-08, 07:43 AM 因公司需求，故請了一條雙向2M專業型FTTB... 利用PING hinet主機測試，發現約二至三分鐘內會發生ping值瞬拉的情況... 有打過中華工程部門！回應是正常情況... 但仍有疑慮故上來請教...這樣是正常的嗎？:jump2: 贊助商連結 n34963496 2008-09-08, 09:49 AM 想請問一下 你們公司申請FTTB雙向專業型，HINET是直接拉一條專線到你們公司嗎? 現在申請2M/2M月租是多少了 rogershu 2008-09-08, 03:04 PM 我客戶的那條雙向2M經過測試不會有樓主說的這種情形，不過也請樓主要貼個ping 值的數據出來看一下吧。 stuart 2008-09-10, 07:15 PM Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\abyul>ping www.hinet.net -t Pinging www.hinet.net [61.219.38.89] with 32 bytes of data: Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=19ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=29ms TTL=249 Reply from 61.219.38.89: bytes=32 time=18ms TTL=249 Reply from 61.219.38.89: bytes=32 time=36ms TTL=249 Reply from 61.219.38.89: bytes=32 time=25ms TTL=249 Reply from 61.219.38.89: bytes=32 time=35ms TTL=249 Reply from 61.219.38.89: bytes=32 time=24ms TTL=249 Reply from 61.219.38.89: bytes=32 time=20ms TTL=249 Reply from 61.219.38.89: bytes=32 time=7ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=20ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=33ms TTL=249 Reply from 61.219.38.89: bytes=32 time=20ms TTL=249 Reply from 61.219.38.89: bytes=32 time=36ms TTL=249 Reply from 61.219.38.89: bytes=32 time=26ms TTL=249 Reply from 61.219.38.89: bytes=32 time=37ms TTL=249 Reply from 61.219.38.89: bytes=32 time=26ms TTL=249 Reply from 61.219.38.89: bytes=32 time=22ms TTL=249 Reply from 61.219.38.89: bytes=32 time=10ms TTL=249 Reply from 61.219.38.89: bytes=32 time=105ms TTL=249 Reply from 61.219.38.89: bytes=32 time=5ms TTL=249 Reply from 61.219.38.89: bytes=32 time=110ms TTL=249 Reply from 61.219.38.89: bytes=32 time=264ms TTL=249 Reply from 61.219.38.89: bytes=32 time=257ms TTL=249 Reply from 61.219.38.89: bytes=32 time=617ms TTL=249 Reply from 61.219.38.89: bytes=32 time=486ms TTL=249 Reply from 61.219.38.89: bytes=32 time=885ms TTL=249 Reply from 61.219.38.89: bytes=32 time=1010ms TTL=249 Reply from 61.219.38.89: bytes=32 time=925ms TTL=249 Reply from 61.219.38.89: bytes=32 time=988ms TTL=249 Reply from 61.219.38.89: bytes=32 time=768ms TTL=249 Reply from 61.219.38.89: bytes=32 time=536ms TTL=249 Reply from 61.219.38.89: bytes=32 time=5ms TTL=249 Reply from 61.219.38.89: bytes=32 time=210ms TTL=249 Reply from 61.219.38.89: bytes=32 time=233ms TTL=249 Reply from 61.219.38.89: bytes=32 time=8ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=15ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=28ms TTL=249 Reply from 61.219.38.89: bytes=32 time=11ms TTL=249 Reply from 61.219.38.89: bytes=32 time=33ms TTL=249 Reply from 61.219.38.89: bytes=32 time=21ms TTL=249 Reply from 61.219.38.89: bytes=32 time=36ms TTL=249 Reply from 61.219.38.89: bytes=32 time=25ms TTL=249 Reply from 61.219.38.89: bytes=32 time=35ms TTL=249 Reply from 61.219.38.89: bytes=32 time=18ms TTL=249 Reply from 61.219.38.89: bytes=32 time=13ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=12ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=12ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=19ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=18ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=30ms TTL=249 Reply from 61.219.38.89: bytes=32 time=17ms TTL=249 Reply from 61.219.38.89: bytes=32 time=34ms TTL=249 Reply from 61.219.38.89: bytes=32 time=25ms TTL=249 Reply from 61.219.38.89: bytes=32 time=36ms TTL=249 Reply from 61.219.38.89: bytes=32 time=27ms TTL=249 Reply from 61.219.38.89: bytes=32 time=28ms TTL=249 Reply from 61.219.38.89: bytes=32 time=13ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 Reply from 61.219.38.89: bytes=32 time=3ms TTL=249 以上是ping 值，全公司現在上網主機二台。 皆無網路動作...(除了這台上網頁外...) 麻煩各位幫我解答....^^ tvirus 2008-09-11, 01:27 AM 不知道是哪種FTTB... 是直接拉光纖進公司? 還是光纖大樓拉光纖進公司? 還是電話線銅線或RJ45進公司? 除了ping之外,用tracert看一下,問題"可能"出在哪 ping time有時真的只能做為參考用...... rogershu 2008-09-11, 02:26 AM 不太正常喔!! 你trace一下，看暴ping會出現在那個節點上。 我客戶那條是VDSL供裝，PING值沒有樓主的漂亮，約在18~19ms，但完全不會暴ping，快跟死人心電圖一樣了。:king: 可以找hinet的機房協助測試，但樓主必需要能夠找到的所在地所屬的中華電信數據分公司的機房電話。 ps.是Hinet 的機房人員不是中華電信的線路機房人員。 mis_waiszli 2008-09-11, 09:39 AM CHT FTTB 2M/2M 16IP 7000元/月 C:\Documents and Settings\Administrator>ping www.hinet.net -t Pinging www.hinet.net [203.66.88.89] with 32 bytes of data: Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=5ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=5ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=23ms TTL=249 Reply from 203.66.88.89: bytes=32 time=8ms TTL=249 Reply from 203.66.88.89: bytes=32 time=31ms TTL=249 Reply from 203.66.88.89: bytes=32 time=13ms TTL=249 Reply from 203.66.88.89: bytes=32 time=33ms TTL=249 Reply from 203.66.88.89: bytes=32 time=24ms TTL=249 Reply from 203.66.88.89: bytes=32 time=36ms TTL=249 Reply from 203.66.88.89: bytes=32 time=26ms TTL=249 Reply from 203.66.88.89: bytes=32 time=31ms TTL=249 Reply from 203.66.88.89: bytes=32 time=27ms TTL=249 Reply from 203.66.88.89: bytes=32 time=29ms TTL=249 Reply from 203.66.88.89: bytes=32 time=14ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=5ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Reply from 203.66.88.89: bytes=32 time=4ms TTL=249 Ping statistics for 203.66.88.89: Packets: Sent = 54, Received = 54, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 36ms, Average = 8ms C:\Documents and Settings\Administrator>ping 61.219.38.89 -t Pinging 61.219.38.89 with 32 bytes of data: Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=5ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=5ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=5ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=5ms TTL=249 Reply from 61.219.38.89: bytes=32 time=5ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=22ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=30ms TTL=249 Reply from 61.219.38.89: bytes=32 time=8ms TTL=249 Reply from 61.219.38.89: bytes=32 time=33ms TTL=249 Reply from 61.219.38.89: bytes=32 time=23ms TTL=249 Reply from 61.219.38.89: bytes=32 time=37ms TTL=249 Reply from 61.219.38.89: bytes=32 time=27ms TTL=249 Reply from 61.219.38.89: bytes=32 time=34ms TTL=249 Reply from 61.219.38.89: bytes=32 time=19ms TTL=249 Reply from 61.219.38.89: bytes=32 time=12ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=5ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Reply from 61.219.38.89: bytes=32 time=4ms TTL=249 Ping statistics for 61.219.38.89: Packets: Sent = 47, Received = 47, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 37ms, Average = 8ms hamspc 2008-09-11, 09:58 AM 去下載visualrouter來跑看看會不會掉封包(packet loss)， 我雖然不是用hinet的， 但是情況比樓主還慘 ping 的話直接request timeout http://i488.photobucket.com/albums/rr248/hamspc/VisualRouterSnap.jpg 目前報修處理中... rocky229 2008-09-11, 02:06 PM 如果這種回應就是專業型hinet FTTB的品質 那也未免太濫了吧.. 很明顯是hinet線路異常 Pinging www.hinet.net [203.66.88.89] with 32 bytes of data: Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 Reply from 203.66.88.89: bytes=32 time=2ms TTL=241 . . . . . . . Ping statistics for 203.66.88.89: Packets: Sent = 97, Received = 97, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 2ms, Average = 2ms n34963496 2008-09-11, 09:43 PM 因公司需求，故請了一條雙向2M專業型FTTB... 利用PING hinet主機測試，發現約二至三分鐘內會發生ping值瞬拉的情況... 有打過中華工程部門！回應是正常情況... 但仍有疑慮故上來請教...這樣是正常的嗎？:jump2: 一個月付這麼多錢，你應該多多打電話過去罵罵:mad: 看你這樣我都不太敢用了 |
|
|