| 會員  | 台基寬頻最近常瞬斷... 我是申辦中投寬頻的用戶 使用台灣大的出口 這兩天一直常瞬斷 每次都斷個十幾秒在連線 個人有玩OLG的習慣 每次都會突然斷線 真的會很讓人不高興 打去客服專線 剛通沒多久 馬上又恢復正常= = 說我訊號很正常..... 這邊是我PING到斷線的結果 Reply from 210.209.15.27: bytes=32 time=29ms TTL=49 Reply from 210.209.15.27: bytes=32 time=30ms TTL=49 Request timed out. Reply from 210.209.15.27: bytes=32 time=25ms TTL=49 Reply from 210.209.15.27: bytes=32 time=66ms TTL=49 Reply from 210.209.15.27: bytes=32 time=24ms TTL=49 Reply from 210.209.15.27: bytes=32 time=46ms TTL=49 Request timed out. Request timed out. Request timed out. Ping statistics for 210.209.15.27: Packets: Sent = 17672, Received = 17654, Lost = 18 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 1127ms, Average = 34ms Control-C 不知道各位先進是否有什麼方法可以解決? 常常這樣真的很困擾~"~ |
| 回覆 |
| 會員 | 回覆: 台基寬頻最近常瞬斷... 玩遊戲斷線當下開網頁可以嗎? 假設可以看來線路並沒斷， 那可問一下遊戲廠商那邊。 如果線路整個都斷掉了， 還是持續跟你網路業者反應吧~ 假設一值都沒改善， 就改換中華吧， 至少穩定多了~ |
| 回覆 |
| 會員 | 回覆: 台基寬頻最近常瞬斷... 我打過客服電話 工程也到府查看線路設備 也將很多接頭重壓 不過還是會瞬斷 18號那天最誇張斷了12次 每次打過去都說訊號很好 唉…這品質真是  |
| 回覆 |
| 會員 | 回覆: 台基寬頻最近常瞬斷... 引用:
網頁皆無法開啟.. 我都預繳一年了 才用兩年就問題一堆  | |
| 回覆 |
| 會員  | 回覆: 台基寬頻最近常瞬斷... CABLE品質是看該地區的系統台有沒有良心的 但路由也要注意 你先用速博看看 |
| 回覆 |
| 會員 | 回覆: 台基寬頻最近常瞬斷... 網路出口這問題有點扯 我完全沒有去申請變更 就把我從台固變成和網 今天是先把他換回台固看看 畢竟先前使用台固也沒有什麼問題 最近斷線時cm都會出現T3 time out的log 不知各位先進能否幫小弟看看是什麼情況？ 語法: 1970-01-01 13:50:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 12:26:32 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 12:25:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 11:59:28 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 11:55:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 11:33:40 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 11:30:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 10:40:45 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 10:40:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 10:40:14 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 10:35:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 10:10:03 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 10:05:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 09:38:20 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 09:35:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 07:35:59 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 07:35:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 06:35:10 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 06:30:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 06:03:56 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 06:00:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 05:01:18 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 05:00:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 04:38:51 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 04:35:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 03:37:23 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 03:35:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 02:45:19 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 02:45:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 02:45:17 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 02:45:15 4-Error D004.3 ToD request sent- No Response received 1970-01-01 02:45:15 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 02:40:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 02:17:16 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 02:15:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 01:21:19 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 01:20:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:51:40 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:50:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:25:07 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:20:17 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:03:18 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:03:10 6-Notice M571.4 Ethernet link dormant - not currently active 1970-01-01 00:00:23 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:00:21 5-Warning D004.1 ToD request sent - No Response received 1970-01-01 00:00:13 3-Critical D003.0 DHCP FAILED - Requested Info not supported. 1970-01-01 00:00:06 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:06:14 5-Warning D004.1 ToD request sent - No Response received 1970-01-01 00:06:06 3-Critical D003.0 DHCP FAILED - Requested Info not supported. 1970-01-01 00:05:56 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:07 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:13:01 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 1970-01-01 00:13:01 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 1970-01-01 00:13:01 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:11:30 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:09:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:06:36 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:06:34 5-Warning D004.1 ToD request sent - No Response received 1970-01-01 00:06:26 3-Critical D003.0 DHCP FAILED - Requested Info not supported. 1970-01-01 00:06:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:06 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:57:28 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 1970-01-01 00:57:28 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 1970-01-01 00:57:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:55:21 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:52:02 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:50:21 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:21:59 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:20:21 4-Error D004.3 ToD request sent- No Response received 不過換完後還是一樣會斷 跟著工程從家裡查到光化箱 據他所述是沒有什麼問題 可是就還是會斷線... 我在上頭有貼上cm的log 想請教各位先進 這情形大概是問題出在哪個環節呢？ 感恩！ |
| 回覆 |
| 會員  | 回覆: 台基寬頻最近常瞬斷... 改用tracert指令試試，看看是那個節點出了問題 光用ping指令，能獲得的資料有限 |
| 回覆 |
| 會員 | 回覆: 台基寬頻最近常瞬斷... 在斷線的時候 是只能連到modem而已 出外完全連不上 過兩分鐘後就又恢復正常 維修人員也說我這邊T3 TIME OUT的次數很多 家中一直到室外的實體線路都查過了 接頭有氧化的都換新 但一樣還是會斷… 而且斷又不是固定時間 有時候今天斷個十次 明天斷一、兩次 後天斷個五次之類的… 且維修也不積極… 一定要有打電話去報修才會繼續動作 不然你還是斷你的＝ ＝.. |
| 回覆 |
| Yanzi  | 回覆: 台基寬頻最近常瞬斷... 換CM機器&有從外獨立拉一條線進來用 還是會有順斷的問題發生的話 建議可以改申裝中華的偽光纖了 |
| 回覆 |
| 會員 | 回覆: 台基寬頻最近常瞬斷... 引用:
所有分接的線路都拔掉 原本可能預留過長的cable線也請工程幫忙截短 從cm端到戶外接頭工程人員也都重壓過+防水… 還是會一直斷… 可能是我這附近只有兩戶人使用cm上網… 比較不被重視 打算年底退租了… 一天至少斷三次 | |
| 回覆 |
| XML | RSS 2.0 | RSS |
本論壇所有文章僅代表留言者個人意見，並不代表本站之立場，討論區以「即時留言」方式運作，故無法完全監察所有即時留言，若您發現文章可能有異議，請 email :[email protected] 處理。
