| Author |
大家有冇同樣問題?? |
牛耕田evanslam
註冊於: 26/04/2003
發帖數目: 1246 |  發表於: 2008-04-17 on 20:34
我舉手做報料員,遇有上唔到黎時,即刻上報!
長江一燈留 
|
qbt
註冊於: 22/04/2007
發帖數目: 79 | 發表於: 2008-04-17 on 21:12
惠州的，一贯无事 
|
鍾國成chungkwokshing
註冊於: 17/10/2005
發帖數目: 400
| 發表於: 2008-04-17 on 21:33
求助者係小弟.小弟係東莞...無人有事即刻網站被'和諧'化!!慘嘞..
|
有規有舉，向着標竿直跑！gogohorse
註冊於: 25/11/2004
發帖數目: 425 | 發表於: 2008-04-17 on 22:14
我在深圳,用•notebook,无線上綱都吾覺有問題.
|
liup
註冊於: 13/09/2003
發帖數目: 2628 | 發表於: 2008-04-18 on 15:36
I didn't experience any access problem. The server is up but it takes a longer turnaround time from my home connection as compared with www.hkjc.com 
Pinging www.hkhorsedb.com [220.232.149.226] with 32 bytes of data:
Reply from 220.232.149.226: bytes=32 time=347ms TTL=44
Reply from 220.232.149.226: bytes=32 time=349ms TTL=44
Reply from 220.232.149.226: bytes=32 time=350ms TTL=44
Reply from 220.232.149.226: bytes=32 time=347ms TTL=44
Ping statistics for 220.232.149.226:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 347ms, Maximum = 350ms, Average = 348ms
Pinging www.hkjc.com [203.215.253.134] with 32 bytes of data:
Reply from 203.215.253.134: bytes=32 time=182ms TTL=52
Reply from 203.215.253.134: bytes=32 time=181ms TTL=52
Reply from 203.215.253.134: bytes=32 time=180ms TTL=52
Reply from 203.215.253.134: bytes=32 time=180ms TTL=52
Ping statistics for 203.215.253.134:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 182ms, Average = 180ms
Tracing route to www.hkhorsedb.com [220.232.149.226]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 10 ms 10 ms 10 ms 73.76.152.1
3 9 ms 9 ms * ge-4-1-ur06.sacramento.ca.sacra.comcast.net [68.
87.213.13]
4 9 ms * 9 ms te-7-2-ar01.sacramento.ca.sacra.comcast.net [68.
87.212.117]
5 12 ms 12 ms 11 ms pos-0-7-0-0-ar01.oakland.ca.sfba.comcast.net [68
.86.90.138]
6 15 ms 16 ms 14 ms pos-0-9-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.85.189]
7 30 ms 26 ms * 68.86.85.141
8 60 ms 60 ms 59 ms pos-0-14-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.153]
9 79 ms 81 ms 80 ms pos-0-9-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.85.154]
10 100 ms 95 ms 96 ms pos-0-9-0-0-cr01.mclean.va.ibone.comcast.net [68
.86.85.74]
11 94 ms 95 ms 95 ms xe-3-1-0.was11.ip.tiscali.net [213.200.84.117]
12 1791 ms 153 ms 204 ms so-0-0-0.lax22.ip.tiscali.net [213.200.80.93]
13 155 ms 164 ms 155 ms asia-netcom-gw.ip.tiscali.net [213.200.84.250]
14 290 ms 292 ms 291 ms gi2-0-0.cr1.nrt1.asianetcom.net [202.147.0.57]
15 344 ms 347 ms 345 ms po5-3.cr1.hkg3.asianetcom.net [202.147.0.174]
16 345 ms 345 ms 346 ms po15-0.gw2.hkg3.asianetcom.net [202.147.16.210]
17 352 ms 353 ms 356 ms PNT-0023.gw2.hkg3.asianetcom.net [203.192.178.74
]
18 346 ms 353 ms 344 ms v154.wtcc2.pacific.net.hk [202.64.3.129]
19 352 ms 353 ms 356 ms v102.tmhc2.pacific.net.hk [202.64.5.5]
20 346 ms 345 ms 345 ms v204.tmhs3504.pacific.net.hk [202.64.149.234]
21 347 ms 347 ms 354 ms sh1.fifthhosting.com [220.232.149.226]
Trace complete.
Tracing route to www.hkjc.com [203.215.253.134]
over a maximum of 30 hops:
1 4 ms 3 ms 1 ms 192.168.1.1
2 9 ms 18 ms 13 ms 73.76.152.1
3 11 ms * 13 ms ge-4-1-ur06.sacramento.ca.sacra.comcast.net [68.
87.213.13]
4 7 ms 12 ms 11 ms te-7-2-ar01.sacramento.ca.sacra.comcast.net [68.
87.212.117]
5 14 ms 16 ms 22 ms pos-0-7-0-0-ar01.oakland.ca.sfba.comcast.net [68
.86.90.138]
6 * 15 ms 23 ms pos-0-14-0-0-cr01.sacramento.ca.ibone.comcast.ne
t [68.86.85.181]
7 17 ms 16 ms 15 ms te-0-1-0-7-cr01.sanjose.ca.ibone.comcast.net [68
.86.84.125]
8 * 19 ms 20 ms te-1-1-pr01.11greatoaks.ca.ibone.comcast.net [68
.86.84.126]
9 19 ms 19 ms 20 ms Tenge13-3.br02.sjo01.pccwbtn.net [63.218.179.25]
10 179 ms 179 ms 179 ms powerbase.ge13-15.br01.hkg04.pccwbtn.net [63.218
.61.174]
11 191 ms 193 ms 201 ms 202.153.96.129
12 181 ms 179 ms 178 ms 133.254.215.203.in-addr.arpa [203.215.254.133]
13 186 ms 181 ms 183 ms 132.253.215.203.in-addr.arpa [203.215.253.132]
14 182 ms 182 ms * 134.253.215.203.in-addr.arpa [203.215.253.134]
15 189 ms 181 ms 181 ms 134.253.215.203.in-addr.arpa [203.215.253.134]
Trace complete.
|
船主~~home
註冊於: 13/03/2002
發帖數目: 9231 | 發表於: 2008-04-19 on 12:57
嘩，甘高深既。
liup係咪即係無問題?? ^_^
 
|
liup
註冊於: 13/09/2003
發帖數目: 2628 | 發表於: 2008-04-19 on 14:32
水蛇春咁長既分析報告, 通常都係無問題架啦。
睇落有d似"摸實屍"既晨操評語表
|
MML
註冊於: 05/04/2003
發帖數目: 5650
| 發表於: 2008-04-19 on 16:47
Quote:
|
On 2008-04-19 14:32, liup wrote:
水蛇春咁長既分析報告, 通常都係無問題架啦。
睇落有d似"摸實屍"既晨操評語表
|
|
Yeah, 水蛇春咁長既分析報告, 通常都係話件事無問題, 係有都係個分析報告本身嘅問題。
RE: 睇落有d似"摸實屍"既晨操評語表 ...
我唔知你個報告講乜 wor .... i.e. .... ^_^ (just kidding)
|
魔術師hkhorsetrack
註冊於: 21/09/2003
發帖數目: 3067
| 發表於: 2008-04-19 on 16:56
Quote:
|
On 2008-04-19 16:47, MML wrote:
Quote:
|
On 2008-04-19 14:32, liup wrote:
水蛇春咁長既分析報告, 通常都係無問題架啦。
睇落有d似"摸實屍"既晨操評語表
|
|
Yeah, 水蛇春咁長既分析報告, 通常都係話件事無問題, 係有都係個分析報告本身嘅問題。
RE: 睇落有d似"摸實屍"既晨操評語表 ...
我唔知你個報告講乜 wor .... i.e. .... ^_^ (just kidding)
|
|
有時我都唔知自己個表講乜
|
登入
會員登記
