線路問題集中討論
- Rena
- 究級玩家
- 文章: 5545
- 註冊時間: 週日 6月 16, 2002 4:33 pm
Re: 現在server的線路算好了么?
Shanghai: 3月10日10:25pm
Pinging login.odyes.com [122.116.138.145] with 32 bytes of data:
Reply from 122.116.138.145: bytes=32 time=197ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=213ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=209ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=193ms TTL=115
Reply from 122.116.138.145: bytes=32 time=197ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=212ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=203ms TTL=115
Reply from 122.116.138.145: bytes=32 time=196ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=216ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=212ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=212ms TTL=115
Ping statistics for 122.116.138.145:
Packets: Sent = 25, Received = 22, Lost = 3 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 193ms, Maximum = 216ms, Average = 208ms
Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms RTA230.home [192.168.1.1]
2 17 ms 10 ms 9 ms 218.1.60.249
3 8 ms 8 ms 8 ms 222.72.254.133
4 8 ms 9 ms 8 ms 124.74.210.129
5 9 ms 8 ms 9 ms 61.152.86.6
6 119 ms 117 ms 120 ms 202.97.35.162
7 9 ms 9 ms 9 ms 202.97.35.22
8 107 ms 107 ms 106 ms 202.97.35.33
9 109 ms 107 ms 107 ms 202.97.4.114
10 186 ms 183 ms 186 ms r36-s2.tp.hinet.net [211.72.233.234]
11 184 ms 185 ms 184 ms r35-s2.tp.hinet.net [210.65.254.249]
12 183 ms 184 ms 184 ms pr01-s2.tp.hinet.net [210.65.254.172]
13 186 ms 186 ms 186 ms tp-crs12.router.hinet.net [220.128.4.70]
14 184 ms 223 ms 185 ms tp-pc1-t64-1.router.hinet.net [220.128.11.57]
15 189 ms 184 ms 185 ms h105.s75.ts.hinet.net [168.95.75.105]
16 210 ms 218 ms 202 ms login.odyes.com [122.116.138.145]
Trace complete.
現在一般晚上速度200,白天是50左右
Pinging login.odyes.com [122.116.138.145] with 32 bytes of data:
Reply from 122.116.138.145: bytes=32 time=197ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=213ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=209ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=193ms TTL=115
Reply from 122.116.138.145: bytes=32 time=197ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=212ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=203ms TTL=115
Reply from 122.116.138.145: bytes=32 time=196ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=216ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=212ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=212ms TTL=115
Ping statistics for 122.116.138.145:
Packets: Sent = 25, Received = 22, Lost = 3 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 193ms, Maximum = 216ms, Average = 208ms
Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms RTA230.home [192.168.1.1]
2 17 ms 10 ms 9 ms 218.1.60.249
3 8 ms 8 ms 8 ms 222.72.254.133
4 8 ms 9 ms 8 ms 124.74.210.129
5 9 ms 8 ms 9 ms 61.152.86.6
6 119 ms 117 ms 120 ms 202.97.35.162
7 9 ms 9 ms 9 ms 202.97.35.22
8 107 ms 107 ms 106 ms 202.97.35.33
9 109 ms 107 ms 107 ms 202.97.4.114
10 186 ms 183 ms 186 ms r36-s2.tp.hinet.net [211.72.233.234]
11 184 ms 185 ms 184 ms r35-s2.tp.hinet.net [210.65.254.249]
12 183 ms 184 ms 184 ms pr01-s2.tp.hinet.net [210.65.254.172]
13 186 ms 186 ms 186 ms tp-crs12.router.hinet.net [220.128.4.70]
14 184 ms 223 ms 185 ms tp-pc1-t64-1.router.hinet.net [220.128.11.57]
15 189 ms 184 ms 185 ms h105.s75.ts.hinet.net [168.95.75.105]
16 210 ms 218 ms 202 ms login.odyes.com [122.116.138.145]
Trace complete.
現在一般晚上速度200,白天是50左右
歡迎加入WOW公會
-
- 系統管理者(Administrator)
- 文章: 1412
- 註冊時間: 週六 6月 30, 2001 8:00 am
Re: 現在server的線路算好了么?
請用tracert看一下是哪個節點比較慢
- Rena
- 究級玩家
- 文章: 5545
- 註冊時間: 週日 6月 16, 2002 4:33 pm
現在server的線路算好了么?
Shanghai: 3月9日10:45pm
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=215ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=207ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=202ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=205ms TTL=115
Reply from 122.116.138.145: bytes=32 time=207ms TTL=115
Reply from 122.116.138.145: bytes=32 time=229ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=224ms TTL=115
Reply from 122.116.138.145: bytes=32 time=220ms TTL=115
Reply from 122.116.138.145: bytes=32 time=200ms TTL=115
Reply from 122.116.138.145: bytes=32 time=231ms TTL=115
Reply from 122.116.138.145: bytes=32 time=219ms TTL=115
Reply from 122.116.138.145: bytes=32 time=203ms TTL=115
Reply from 122.116.138.145: bytes=32 time=208ms TTL=115
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Request timed out.
Request timed out.
Reply from 122.116.138.145: bytes=32 time=191ms TTL=115
Reply from 122.116.138.145: bytes=32 time=206ms TTL=115
Reply from 122.116.138.145: bytes=32 time=198ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=209ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Ping statistics for 122.116.138.145:
Packets: Sent = 434, Received = 405, Lost = 29 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 278ms, Average = 205ms
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=215ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=207ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=202ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=205ms TTL=115
Reply from 122.116.138.145: bytes=32 time=207ms TTL=115
Reply from 122.116.138.145: bytes=32 time=229ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=224ms TTL=115
Reply from 122.116.138.145: bytes=32 time=220ms TTL=115
Reply from 122.116.138.145: bytes=32 time=200ms TTL=115
Reply from 122.116.138.145: bytes=32 time=231ms TTL=115
Reply from 122.116.138.145: bytes=32 time=219ms TTL=115
Reply from 122.116.138.145: bytes=32 time=203ms TTL=115
Reply from 122.116.138.145: bytes=32 time=208ms TTL=115
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Request timed out.
Request timed out.
Reply from 122.116.138.145: bytes=32 time=191ms TTL=115
Reply from 122.116.138.145: bytes=32 time=206ms TTL=115
Reply from 122.116.138.145: bytes=32 time=198ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=199ms TTL=115
Reply from 122.116.138.145: bytes=32 time=210ms TTL=115
Reply from 122.116.138.145: bytes=32 time=209ms TTL=115
Reply from 122.116.138.145: bytes=32 time=211ms TTL=115
Ping statistics for 122.116.138.145:
Packets: Sent = 434, Received = 405, Lost = 29 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 278ms, Average = 205ms
歡迎加入WOW公會
- hiphopsicfuret
- 中級玩家
- 文章: 203
- 註冊時間: 週三 9月 09, 2009 5:52 am
Re: 伺服器連不上了
GM大大~ 辛苦了 / \
-
- 系統管理者(Administrator)
- 文章: 545
- 註冊時間: 週三 9月 02, 2009 8:54 pm
伺服器網路已恢復
伺服器已經恢復正常,各位可以登入遊戲了!!
-
- 遊戲管理者(GM)
- 文章: 311
- 註冊時間: 週一 9月 21, 2009 8:58 pm
Re: 伺服器連不上了
Dears,
目前正聯繫管理伺服器的GM中,請大家稍等。
Thanks!
目前正聯繫管理伺服器的GM中,請大家稍等。
Thanks!
Mail : odyjudas@gmail.com
有任何與遊戲相關問題歡迎發Mail or PM聯繫。
有任何與遊戲相關問題歡迎發Mail or PM聯繫。
- hiphopsicfuret
- 中級玩家
- 文章: 203
- 註冊時間: 週三 9月 09, 2009 5:52 am
Re: 伺服器連不上了
現在連不上???? 只有我這樣嗎O O?
-
- 高級玩家
- 文章: 369
- 註冊時間: 週一 5月 27, 2002 5:14 am
Re: 修正lag問題後似乎更加lag了
基本上不算 lag, 根據經驗會出現 time out 的地方有兩點:
1. 第 15 個 route 海外連到 Hinet 的那一段
2. 最後一個連到主機的 route (應該是指 Server 本身).
Ping statistics for 122.116.138.145:
Packets: Sent = 324, Received = 323, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 283ms, Average = 199ms
後期關站前用雙向 512 從海外走"一步"要三秒, 現在可以玩已經偷笑了.
Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:
1 * 2 ms 1 ms x.x.x.x
2 12 ms 8 ms 9 ms 10.88.16.1
3 10 ms 16 ms 10 ms xxx01xxxca-gbe-1-34.charter.com [96.34.97.xxx]
4 9 ms 19 ms 7 ms 96-34-96-22.static.unas.ca.charter.com [96.34.96.22]
5 13 ms 12 ms 11 ms bbr01mtpkca-tge-0-0-0-6.mtpk.ca.charter.com [96.34.2.24]
6 9 ms 11 ms 10 ms los-edge-01.inet.qwest.net [208.46.190.193]
7 23 ms 9 ms 11 ms los-core-02.inet.qwest.net [205.171.32.37]
8 11 ms 10 ms 12 ms lap-brdr-01.inet.qwest.net [205.171.32.14]
9 22 ms 15 ms 12 ms 0.so-5-0-0.BR1.LAX7.ALTER.NET [204.255.168.33]
10 14 ms 13 ms 12 ms 0.so-6-0-0.XT2.LAX7.ALTER.NET [152.63.112.154]
11 28 ms 21 ms 21 ms 0.so-4-0-0.XL2.PAO1.ALTER.NET [152.63.54.82]
12 23 ms 27 ms 22 ms POS5-0.IG2.PAO1.ALTER.NET [152.63.49.137]
13 37 ms 22 ms 29 ms chunghwa-gw.customer.alter.net [63.65.131.122]
14 28 ms 35 ms 23 ms r02-pa.us.hinet.net [202.39.83.1]
15 159 ms 157 ms 153 ms r02-s2.tp.hinet.net [211.72.108.206]
16 157 ms 163 ms 154 ms 220-128-7-130.HINET-IP.hinet.net [220.128.7.130]
17 170 ms 191 ms 167 ms 220-128-7-174.HINET-IP.hinet.net [220.128.7.174]
18 173 ms 170 ms 175 ms tp-pc1-t64-1.router.hinet.net [220.128.2.53]
19 174 ms 171 ms 170 ms h105.s75.ts.hinet.net [168.95.75.105]
20 220 ms 203 ms 202 ms 122-116-138-145.HINET-IP.hinet.net [122.116.138.145]
Trace complete.
1. 第 15 個 route 海外連到 Hinet 的那一段
2. 最後一個連到主機的 route (應該是指 Server 本身).
Ping statistics for 122.116.138.145:
Packets: Sent = 324, Received = 323, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 283ms, Average = 199ms
後期關站前用雙向 512 從海外走"一步"要三秒, 現在可以玩已經偷笑了.
Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:
1 * 2 ms 1 ms x.x.x.x
2 12 ms 8 ms 9 ms 10.88.16.1
3 10 ms 16 ms 10 ms xxx01xxxca-gbe-1-34.charter.com [96.34.97.xxx]
4 9 ms 19 ms 7 ms 96-34-96-22.static.unas.ca.charter.com [96.34.96.22]
5 13 ms 12 ms 11 ms bbr01mtpkca-tge-0-0-0-6.mtpk.ca.charter.com [96.34.2.24]
6 9 ms 11 ms 10 ms los-edge-01.inet.qwest.net [208.46.190.193]
7 23 ms 9 ms 11 ms los-core-02.inet.qwest.net [205.171.32.37]
8 11 ms 10 ms 12 ms lap-brdr-01.inet.qwest.net [205.171.32.14]
9 22 ms 15 ms 12 ms 0.so-5-0-0.BR1.LAX7.ALTER.NET [204.255.168.33]
10 14 ms 13 ms 12 ms 0.so-6-0-0.XT2.LAX7.ALTER.NET [152.63.112.154]
11 28 ms 21 ms 21 ms 0.so-4-0-0.XL2.PAO1.ALTER.NET [152.63.54.82]
12 23 ms 27 ms 22 ms POS5-0.IG2.PAO1.ALTER.NET [152.63.49.137]
13 37 ms 22 ms 29 ms chunghwa-gw.customer.alter.net [63.65.131.122]
14 28 ms 35 ms 23 ms r02-pa.us.hinet.net [202.39.83.1]
15 159 ms 157 ms 153 ms r02-s2.tp.hinet.net [211.72.108.206]
16 157 ms 163 ms 154 ms 220-128-7-130.HINET-IP.hinet.net [220.128.7.130]
17 170 ms 191 ms 167 ms 220-128-7-174.HINET-IP.hinet.net [220.128.7.174]
18 173 ms 170 ms 175 ms tp-pc1-t64-1.router.hinet.net [220.128.2.53]
19 174 ms 171 ms 170 ms h105.s75.ts.hinet.net [168.95.75.105]
20 220 ms 203 ms 202 ms 122-116-138-145.HINET-IP.hinet.net [122.116.138.145]
Trace complete.
-
- 高級玩家
- 文章: 621
- 註冊時間: 週二 10月 01, 2002 6:58 am
-
- 頂級玩家
- 文章: 1142
- 註冊時間: 週二 12月 11, 2001 8:00 am
Re: 修正lag問題後似乎更加lag了
報告: 台灣地區目前很順暢!!GM Aron 寫:請台灣的玩家報告一下lag的情況
另外,建議用tracert去看哪個節點出問題
在windows命令列下打 tracert login.odyes.com
誰在線上
正在瀏覽這個版面的使用者:沒有註冊會員 和 2 位訪客