• 4

[已解決]北美無法連線mobile01..

我的是中華電信 adsl
之前連"路天拍賣" 都無法連線 連 "PCHOME" 就正常
打給客服 她們也說 "露天"正常 可進入
叫我暫時用Proxy 連路天 一設定就可以了 你也可測試看看
bZIP
注意一下 Windows/System32/Drivers/Etc/Hosts 有沒有被改過.

有些木馬或病毒會在這邊把網址對應到惡意網站的 IP .

pzip wrote:用Proxy 連路天 一設定就可以了(恕刪)

謝謝,我知道只要用proxy就可以了。可是,我還是很想知道是哪個環節出了錯。
slime wrote:注意一下 Windows/System32/Drivers/Etc/Hosts 有沒有被改過.
(恕刪)

謝謝回覆~~但是應該不可能連不上的人都中吧~~
我的媽呀...

不過, 你這個"正確"的 routing 走的還真遠. 很可能還沒走到封包就已經死掉了 TTL exceeded.

你試試 ping -i 255 www.mobile01.com 看看.

不過, 看來高雄到台南的hinet線路是有點問題.
兼職MIS... 但是當全職操
bakacary wrote:我的媽呀... ...(恕刪)

C:\Documents and Settings\xx>ping -i 255 www.mobile01.com
Pinging www.mobile01.com [211.75.83.3] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 211.75.83.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
doggy.piggy wrote:

C:\Documents and Settings\xx>ping -i 255 www.mobile01.com
Pinging www.mobile01.com [211.75.83.3] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 211.75.83.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)


這很詭異.

我剛剛也從這裡traceroute到m01. 發現我的 routing 到台灣以後跟你的是一樣.

這是你的neotrace:
26 15 4 220.128.25.30 Gaoxiong kh-c12r12.router.hinet.net
27 15 4 220.128.25.145 Gaoxiong kh-c76r2.router.hinet.net
28 14 - 211.22.225.105 Gaoxiong
29 16 - 202.39.137.1 Shanzhong

這是我的 trace:
12 66 ms 69 ms 69 ms kh-c12r12.router.hinet.net [220.128.2.13]
13 67 ms 70 ms 69 ms kh-c76r2.router.hinet.net [220.128.25.145]
14 68 ms 70 ms 69 ms 211.22.225.105
15 66 ms 64 ms 66 ms 202.39.137.1
16 71 ms 69 ms 70 ms www.mobile01.com [211.75.83.3]

你就差那麼一個hop...

不過, time-warner 的 routing 是可以再最佳化. 我在上海traceroute 到 www.rr.com 都只有 24 個 hop. TW 到了 28 個 hop 還連不到是有點誇張.


兼職MIS... 但是當全職操
bakacary wrote:(恕刪)這兩天多做traceroute. 注意一下你的 routing 有沒有變動

OK. 謝謝你了。也很希望mobile01的站務可以快點發現這幾篇北美連不到mobile01的求救文。
* * * * * * * * * * * * * * * * * * * * * * * * * * * *
tracert -h 40 www.mobile01.com
Tracing route to www.mobile01.com [211.75.83.3]
over a maximum of 40 hops:
1 8 ms 2 ms 2 ms 192.168.1.1
2 10 ms 9 ms 15 ms 192.168.1.1
3 14 ms 11 ms 11 ms gig8-0-0.....rr.com [24.xx.xx.xx]
4 16 ms 15 ms 18 ms ge-6-0-0.....rr.com [24.xx.xx.xx]
5 19 ms 22 ms 21 ms te-3-1.car1.Boston1.Level3.net [4.79.0.73]
6 29 ms 21 ms 63 ms ae-11-11.car2.Boston1.Level3.net [4.69.132.246]
7 28 ms 37 ms 38 ms ae-5-5.ebr1.NewYork1.Level3.net [4.69.132.250]
8 30 ms 31 ms 35 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
9 53 ms 27 ms 27 ms ae-33-89.car3.NewYork1.Level3.net [4.68.16.133]
10 23 ms 37 ms 27 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]
11 108 ms 104 ms 107 ms tbr1.n54ny.ip.att.net [12.123.3.106]
12 108 ms 107 ms 104 ms cr2.n54ny.ip.att.net [12.122.16.157]
13 106 ms 106 ms 105 ms cr2.wswdc.ip.att.net [12.122.3.38]
14 118 ms 118 ms 108 ms tbr1.wswdc.ip.att.net [12.122.16.30]
15 112 ms 117 ms 106 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
16 105 ms 111 ms 118 ms cr1.sl9mo.ip.att.net [12.122.18.17]
17 108 ms 113 ms 106 ms cr1.la2ca.ip.att.net [12.122.28.185]
18 107 ms 108 ms 107 ms tbr1.la2ca.ip.att.net [12.122.19.138]
19 125 ms 115 ms 123 ms 12.122.82.141
20 108 ms 106 ms 103 ms 12.118.42.14
21 103 ms 103 ms 106 ms la-c12r11.USA-LA.router.hinet.net [202.39.93.13]
22 236 ms 237 ms 226 ms ty-fo-c12r32.router.hinet.net [211.21.116.154]
23 228 ms 276 ms 288 ms ty-fo-c12r12.router.hinet.net [211.21.116.142]
24 237 ms 236 ms 245 ms tn-st-c12r12.router.hinet.net [220.128.9.5]
25 238 ms 238 ms 240 ms kh-c12r12.router.hinet.net [220.128.25.30]
26 248 ms 236 ms 234 ms kh-c76r2.router.hinet.net [220.128.25.145]
27 237 ms 245 ms 236 ms 211.22.225.105
28 238 ms 240 ms 235 ms 202.39.137.1
29 * * * Request timed out.
30 * * * Request timed out.
31 * * * Request timed out.
32 * * * Request timed out.
33 * * * Request timed out.
34 * * * Request timed out.
35 * * * Request timed out.
36 * * * Request timed out.
37 * * * Request timed out.
38 * * * Request timed out.
39 * * * Request timed out.
40 * * * Request timed out.
Trace complete.
...
20 108 ms 106 ms 103 ms 12.118.42.14
21 103 ms 103 ms 106 ms la-c12r11.USA-LA.router.hinet.net [202.39.93.13]
22 236 ms 237 ms 226 ms ty-fo-c12r32.router.hinet.net [211.21.116.154]
23 228 ms 276 ms 288 ms ty-fo-c12r12.router.hinet.net [211.21.116.142]
24 237 ms 236 ms 245 ms tn-st-c12r12.router.hinet.net [220.128.9.5]
25 238 ms 238 ms 240 ms kh-c12r12.router.hinet.net [220.128.25.30]
26 248 ms 236 ms 234 ms kh-c76r2.router.hinet.net [220.128.25.145]
27 237 ms 245 ms 236 ms 211.22.225.105
28 238 ms 240 ms 235 ms 202.39.137.1
29 * * * Request timed out.
30 * * * Request timed out.
31 * * * Request timed out.
32 * * * Request timed out.
33 * * * Request timed out.
34 * * * Request timed out.
35 * * * Request timed out.
36 * * * Request timed out.
37 * * * Request timed out.
38 * * * Request timed out.
39 * * * Request timed out.
40 * * * Request timed out.
Trace complete.


樓主呀, 原則上你已經到m01門口了呀.

把你的traceroute跟我的比較一下就知道了.

到站務版去發個消息吧. 搞不好m01的防火牆把 24 & 74 的 IP 組給檔掉了. (我的router log 裡面曾經有來自 24 的 DoS 攻擊紀錄, 所以router反應是加入黑名單... 不排除m01也有碰過這個問題. 尤其他又是固定ip)
兼職MIS... 但是當全職操
我也是用 Time Warner (South CA), 接 Mobile01 沒問題.
  • 4
內文搜尋
X
評分
評分
複製連結
Mobile01提醒您
您目前瀏覽的是行動版網頁
是否切換到電腦版網頁呢?