【問題】請大家幫我判斷一下SEEDNET到底是出什麼問題

**Vangil** · 2009-01-07, 05:58 AM

我換SEEDNET光纖後一直都很滿意
可是近幾天到晚上就特別誇張順暢感完全不見
三更半夜卻又回到較正常的數值
我提供下列數值請大家幫我判斷一下是那裡出問題

2009/01/06 星期二
下午 10:49

Microsoft Windows XP [版本 5.1.2600]
==========================================================================

Windows IP Configuration

Host Name . . . . . . . . . . . . : yoshikun-7e9834

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter 區域連線:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter

Physical Address. . . . . . . . . : 00-19-DB-23-57-CF

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.1.144

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 168.95.1.1

168.95.192.1

PPP adapter Seednet:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 123.204.172.54

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 123.204.172.54

DNS Servers . . . . . . . . . . . : 139.175.55.244

139.175.252.16

NetBIOS over Tcpip. . . . . . . . : Disabled

==========================================================================

Pinging 192.72.80.37 with 1 bytes of data:

Reply from 192.72.80.37: bytes=1 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1 time=46ms TTL=253

Reply from 192.72.80.37: bytes=1 time=46ms TTL=253

Reply from 192.72.80.37: bytes=1 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1 time=27ms TTL=253

Ping statistics for 192.72.80.37:

Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 15ms, Maximum = 46ms, Average = 32ms

==========================================================================

Pinging 192.72.80.37 with 500 bytes of data:

Reply from 192.72.80.37: bytes=500 time=38ms TTL=253

Reply from 192.72.80.37: bytes=500 time=31ms TTL=253

Reply from 192.72.80.37: bytes=500 time=31ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=31ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=31ms TTL=253

Reply from 192.72.80.37: bytes=500 time=31ms TTL=253

Reply from 192.72.80.37: bytes=500 time=46ms TTL=253

Reply from 192.72.80.37: bytes=500 time=46ms TTL=253

Ping statistics for 192.72.80.37:

Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 15ms, Maximum = 46ms, Average = 31ms

==========================================================================

Pinging 192.72.80.37 with 1400 bytes of data:

Reply from 192.72.80.37: bytes=1400 time=39ms TTL=253

Request timed out.

Reply from 192.72.80.37: bytes=1400 time=48ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=46ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=31ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=46ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=31ms TTL=253

Ping statistics for 192.72.80.37:

Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),

Approximate round trip times in milli-seconds:

Minimum = 31ms, Maximum = 48ms, Average = 37ms

==========================================================================

Active Connections

Proto Local Address Foreign Address State
TCP 123.204.172.54:2501 202.43.198.86:443 ESTABLISHED
TCP 123.204.172.54:2538 124.211.36.13:80 ESTABLISHED
TCP 123.204.172.54:2546 119.110.94.206:2525 ESTABLISHED
TCP 123.204.172.54:2562 202.248.110.204:80 ESTABLISHED
TCP 123.204.172.54:2563 202.248.110.204:80 ESTABLISHED
TCP 123.204.172.54:2565 125.63.42.39:80 SYN_SENT
TCP 127.0.0.1:5152 127.0.0.1:2208 CLOSE_WAIT
==========================================================================

Tracing route to service.seed.net.tw [192.72.80.37]

over a maximum of 30 hops:

1 28 ms 31 ms 31 ms tp240-9.dialup.seed.net.tw [139.175.240.9]

2 15 ms 15 ms 15 ms sj235-66.dialup.seed.net.tw [139.175.235.66]

3 31 ms 31 ms 31 ms service.seed.net.tw [192.72.80.37]

Trace complete.

==========================================================================
ftp> Connected to pftest3.seed.net.tw.

open pftest3.seed.net.tw
220 Welcome to seednet FTP service.
User (pftest3.seed.net.tw

none)):
331 Please specify the password.

230 Login successful.
ftp> get 3m.dat
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 3m.dat (3147825 bytes).
226 File send OK.
ftp: 3147825 bytes received in 5.03Seconds 625.69Kbytes/sec.

ftp> cd upload
250 Directory successfully changed.
ftp> put 3m.dat
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 3147825 bytes sent in 15.72Seconds 200.27Kbytes/sec.

ftp> put party-t0737207-224955-speed.txt
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 6158 bytes sent in 0.00Seconds 6158000.00Kbytes/sec.

ftp> quit
221 Goodbye.

--------------------------------------------------
另一個較為正常的數值測試時間也不同
--------------------------------------------------
2009/01/07 星期三
上午 05:09

Microsoft Windows XP [版本 5.1.2600]
==========================================================================

Windows IP Configuration

Host Name . . . . . . . . . . . . : yoshikun-7e9834

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter 區域連線:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter

Physical Address. . . . . . . . . : 00-19-DB-23-57-CF

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.1.144

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 168.95.1.1

168.95.192.1

PPP adapter Seednet:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 123.204.163.242

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 123.204.163.242

DNS Servers . . . . . . . . . . . : 139.175.55.244

139.175.252.16

NetBIOS over Tcpip. . . . . . . . : Disabled

==========================================================================

Pinging 192.72.80.37 with 1 bytes of data:

Reply from 192.72.80.37: bytes=1 time=16ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1 time=15ms TTL=253

Ping statistics for 192.72.80.37:

Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 15ms, Maximum = 16ms, Average = 15ms

==========================================================================

Pinging 192.72.80.37 with 500 bytes of data:

Reply from 192.72.80.37: bytes=500 time=12ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Reply from 192.72.80.37: bytes=500 time=15ms TTL=253

Ping statistics for 192.72.80.37:

Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 12ms, Maximum = 15ms, Average = 14ms

==========================================================================

Pinging 192.72.80.37 with 1400 bytes of data:

Reply from 192.72.80.37: bytes=1400 time=27ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=15ms TTL=253

Reply from 192.72.80.37: bytes=1400 time=15ms TTL=253

Ping statistics for 192.72.80.37:

Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 15ms, Maximum = 27ms, Average = 16ms

==========================================================================

Active Connections

Proto Local Address Foreign Address State
TCP 123.204.163.242:1084 203.84.201.71:80 ESTABLISHED
TCP 123.204.163.242:1085 203.84.201.71:80 ESTABLISHED
TCP 123.204.163.242:1086 203.84.201.71:80 ESTABLISHED
TCP 123.204.163.242:1087 203.84.201.71:80 ESTABLISHED
TCP 123.204.163.242:1088 203.84.201.71:80 ESTABLISHED
TCP 123.204.163.242:1089 203.84.201.71:80 ESTABLISHED
TCP 123.204.163.242:1090 203.84.201.71:80 ESTABLISHED
TCP 123.204.163.242:1091 203.84.201.71:80 ESTABLISHED
TCP 123.204.163.242:1092 203.84.201.71:80 ESTABLISHED
TCP 123.204.163.242:1093 203.84.201.71:80 ESTABLISHED
TCP 127.0.0.1:1045 127.0.0.1:5152 TIME_WAIT
TCP 127.0.0.1:1081 127.0.0.1:5152 FIN_WAIT_2
TCP 127.0.0.1:5152 127.0.0.1:1081 CLOSE_WAIT
==========================================================================

Tracing route to service.seed.net.tw [192.72.80.37]

over a maximum of 30 hops:

1 12 ms 15 ms 15 ms tp240-9.dialup.seed.net.tw [139.175.240.9]

2 15 ms 15 ms 15 ms sj235-131.dialup.seed.net.tw [139.175.235.131]

3 15 ms 15 ms 15 ms service.seed.net.tw [192.72.80.37]

Trace complete.

==========================================================================
ftp> Connected to pftest3.seed.net.tw.

open pftest3.seed.net.tw
220 Welcome to seednet FTP service.
User (pftest3.seed.net.tw

none)):
331 Please specify the password.

230 Login successful.
ftp> get 3m.dat
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 3m.dat (3147825 bytes).
226 File send OK.
ftp: 3147825 bytes received in 2.23Seconds 1409.05Kbytes/sec.

ftp> cd upload
250 Directory successfully changed.
ftp> put 3m.dat
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 3147825 bytes sent in 13.30Seconds 236.73Kbytes/sec.

ftp> put party-t0737207-50930-speed.txt
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 6605 bytes sent in 0.00Seconds 6605000.00Kbytes/sec.

ftp> quit
221 Goodbye.

----------------------------------------------------------------
日本的Nicovideo 不正常版
----------------------------------------------------------------
2009/01/06 星期二
下午 10:56

Microsoft Windows XP [版本 5.1.2600]

Windows IP Configuration

Host Name . . . . . . . . . . . . : yoshikun-7e9834

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter 區域連線:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter

Physical Address. . . . . . . . . : 00-19-DB-23-57-CF

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.1.144

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 168.95.1.1

168.95.192.1

PPP adapter Seednet:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 123.204.209.39

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 123.204.209.39

DNS Servers . . . . . . . . . . . : 139.175.55.244

139.175.252.16

NetBIOS over Tcpip. . . . . . . . : Disabled

==========================================================================
Server: dns.hinet.net
Address: 168.95.1.1

Name: www.nicovideo.jp
Address: 202.248.110.243

==========================================================================

Pinging www.nicovideo.jp [202.248.110.243] with 32 bytes of data:

Reply from 133.160.55.162: Destination net unreachable.

Request timed out.

Request timed out.

Request timed out.

Reply from 133.160.55.162: Destination net unreachable.

Request timed out.

Reply from 133.160.55.162: Destination net unreachable.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 202.248.110.243:

Packets: Sent = 10, Received = 3, Lost = 7 (70% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

==========================================================================

Tracing route to www.nicovideo.jp [202.248.110.243]

over a maximum of 30 hops:

1 53 ms 62 ms 62 ms tp240-9.dialup.seed.net.tw [139.175.240.9]

2 15 ms 15 ms 15 ms sj235-130.dialup.seed.net.tw [139.175.235.130]

3 62 ms 61 ms 62 ms R56-190.seed.net.tw [139.175.56.190]

4 93 ms 77 ms 77 ms R58-82.seed.net.tw [139.175.58.82]

5 109 ms 109 ms 93 ms AS2510-4.ix.jpix.ad.jp [210.171.224.183]

6 109 ms 109 ms 109 ms 133.160.183.33

7 109 ms 109 ms 109 ms 133.160.182.200

8 93 ms 93 ms 109 ms 133.160.139.18

9 133.160.55.162 reports: Destination net unreachable.

Trace complete.

==========================================================================
ftp> Connected to pftest3.seed.net.tw.

open pftest3.seed.net.tw
220 Welcome to seednet FTP service.
User (pftest3.seed.net.tw

none)):
331 Please specify the password.

230 Login successful.
ftp> cd upload
250 Directory successfully changed.
ftp> put party-t0737207-225624-web.txt
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 3670 bytes sent in 0.00Seconds 3670000.00Kbytes/sec.

ftp> quit
221 Goodbye.

----------------------------------------------------------------
NICOVIDEO Tracert部份較正常版
----------------------------------------------------------------
2009/01/07 星期三
上午 05:11

Microsoft Windows XP [版本 5.1.2600]

Windows IP Configuration

Host Name . . . . . . . . . . . . : yoshikun-7e9834

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter 區域連線:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter

Physical Address. . . . . . . . . : 00-19-DB-23-57-CF

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.1.144

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 168.95.1.1

168.95.192.1

PPP adapter Seednet:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 123.204.163.242

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 123.204.163.242

DNS Servers . . . . . . . . . . . : 139.175.55.244

139.175.252.16

NetBIOS over Tcpip. . . . . . . . : Disabled

==========================================================================
Server: dns.hinet.net
Address: 168.95.1.1

Name: www.nicovideo.jp
Address: 202.248.110.243

==========================================================================

Pinging www.nicovideo.jp [202.248.110.243] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 133.160.55.162: Destination net unreachable.

Request timed out.

Reply from 133.160.55.162: Destination net unreachable.

Request timed out.

Reply from 133.160.55.162: Destination net unreachable.

Ping statistics for 202.248.110.243:

Packets: Sent = 10, Received = 3, Lost = 7 (70% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

==========================================================================

Tracing route to www.nicovideo.jp [202.248.110.243]

over a maximum of 30 hops:

1 * * 15 ms tp240-9.dialup.seed.net.tw [139.175.240.9]

2 15 ms 15 ms 15 ms sj235-67.dialup.seed.net.tw [139.175.235.67]

3 15 ms 15 ms 15 ms R57-133.seed.net.tw [139.175.57.133]

4 46 ms 46 ms 46 ms R58-38.seed.net.tw [139.175.58.38]

5 46 ms 62 ms 46 ms AS2510-4.ix.jpix.ad.jp [210.171.224.183]

6 46 ms 46 ms 62 ms 133.160.183.1

7 46 ms 46 ms 46 ms 133.160.182.200

8 46 ms 46 ms 46 ms 133.160.139.18

9 * * * Request timed out.

10 * 133.160.55.162 reports: Destination net unreachable.

Trace complete.

==========================================================================
ftp> Connected to pftest3.seed.net.tw.

open pftest3.seed.net.tw
220 Welcome to seednet FTP service.
User (pftest3.seed.net.tw

none)):
331 Please specify the password.

230 Login successful.
ftp> cd upload
250 Directory successfully changed.
ftp> put party-t0737207-51127-web.txt
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 3730 bytes sent in 0.00Seconds 3730000.00Kbytes/sec.

ftp> quit
221 Goodbye.

請大家幫我判斷一下到底是怎麼一回事= =;
整體的穩定性都和之前差好多

我的SEEDNET蜜月期該不會只有二個月吧

**tvirus** · 2009-01-07, 10:31 AM

連www.nicovideo.jp的部份,看起來都是正常(對,那樣是正常)

不正常時
IP Address. . . . . . . . . . . . : 123.204.172.54
ftp: 3147825 bytes received in 5.03Seconds 625.69Kbytes/sec.
ftp: 3147825 bytes sent in 15.72Seconds 200.27Kbytes/sec.

正常時
IP Address. . . . . . . . . . . . : 123.204.163.242
ftp: 3147825 bytes received in 2.23Seconds 1409.05Kbytes/sec.
ftp: 3147825 bytes sent in 13.30Seconds 236.73Kbytes/sec.

這條線只有你一個人在用嗎??

**BenLi** · 2009-01-07, 12:24 PM

根據我用了一年 Seednet 數位光纖的經驗

這種一模一樣的情況我一年內碰到兩次，所以我可以 90% 判斷

出數據機第一個節點已經爆 ping
因為數位光纖電路仍是使用中華電信電路
所以是 [bold]Seednet 機房到中華電信機房的頻寬已經超過負荷[/bold]
你就直接用線上客服直接這麼障礙申告吧
不過可別附上你主題的那一大串，只要重點
你的作業系統、trace 到 dns.seed.net.tw 的數據(測試時請直接接數據機並分正常時及異常時)
到 Seednet 的大型檔案下載速率(同樣分正常時及異常時)

之前兩次這樣第一次拖了一個月才拓寬與中華電信機房頻寬所以當月連線費有補償
第二次是直接先幫我分流再慢慢拓寬頻寬，所以只有影響幾天

**Vangil** · 2009-01-07, 08:25 PM

作者：tvirus

連www.nicovideo.jp的部份,看起來都是正常(對,那樣是正常)

不正常時
IP Address. . . . . . . . . . . . : 123.204.172.54
ftp: 3147825 bytes received in 5.03Seconds 625.69Kbytes/sec.
ftp: 3147825 bytes sent in 15.72Seconds 200.27Kbytes/sec.

正常時
IP Address. . . . . . . . . . . . : 123.204.163.242
ftp: 3147825 bytes received in 2.23Seconds 1409.05Kbytes/sec.
ftp: 3147825 bytes sent in 13.30Seconds 236.73Kbytes/sec.

這條線只有你一個人在用嗎??

對只有我一個人在用....
而且電腦都沒有使用P2P或是養寵物...
測試時也把遊戲機的網路線拔掉了

**Vangil** · 2009-01-07, 08:36 PM

作者：BenLi

根據我用了一年 Seednet 數位光纖的經驗

這種一模一樣的情況我一年內碰到兩次，所以我可以 90% 判斷

出數據機第一個節點已經爆 ping
因為數位光纖電路仍是使用中華電信電路
所以是 [bold]Seednet 機房到中華電信機房的頻寬已經超過負荷[/bold]
你就直接用線上客服直接這麼障礙申告吧
不過可別附上你主題的那一大串，只要重點
你的作業系統、trace 到 dns.seed.net.tw 的數據(測試時請直接接數據機並分正常時及異常時)
到 Seednet 的大型檔案下載速率(同樣分正常時及異常時)

之前兩次這樣第一次拖了一個月才拓寬與中華電信機房頻寬所以當月連線費有補償
第二次是直接先幫我分流再慢慢拓寬頻寬，所以只有影響幾天

謝謝大大的心得分享...
了解
我會用線上客服申告看看的

不過還真擔心這問題會拖很久....;;;;

**cheerx** · 2009-01-08, 05:17 AM

其實你再pczone呆的夠久的話,大概就猜的出來這是區域壅塞的老問題.問題出在isp對中華電信租的連回骨幹的電路頻寬不夠,或是當地用戶增加讓當地的router不堪負荷.SEEDNET類似的情況已經不只一次了,其實小弟也一直很好奇為什麼這種事情SEEDNET沒辦法預防.

**BenLi** · 2009-01-08, 09:11 AM

其實不只Seednet，我轉換台灣大寬頻兩個月內就已經發生一次
而不爽的是Seednet會承認問題甚至賠償當月連線費
但台灣大寬頻回覆給我的居然是「因ping的指令只是一種簡單基本丟封包的測試，電腦端之防火牆及防毒軟體等均會影響您ping的結果，並不一定是線路的問題」
雖然用推託式的回答，但爆ping問題也還是在一個禮拜內恢復就是了
覺得這些租用中華電信電路的ISP都只顧著狂推銷商品卻沒注意跟中華電信的頻寬是否夠負荷
才10M而已就這樣，那100M/1G還得了，多1、2個用戶安裝就三天兩頭整區爆ping

**finalcut** · 2009-01-08, 09:35 AM

不會吧
我才剛換台灣大寬頻
雖然還沒什麼問題
不過有在用網路電話耶
這樣怎麼得了

不過我用bt
感覺有比hinet快耶

**cheerx** · 2009-01-08, 07:10 PM

爆ping有的時候未必是區域雍塞,而是機房壞PORT或是中華電信在機板上設定有誤(速率不對),SEEDNET是因為之前每隔一段時間就很多人在版上幹,很多區域都有雍塞過,所以問題很明顯.

**BenLi** · 2009-01-08, 07:25 PM

作者：cheerx

爆ping有的時候未必是區域雍塞,而是機房壞PORT或是中華電信在機板上設定有誤(速率不對),SEEDNET是因為之前每隔一段時間就很多人在版上幹,很多區域都有雍塞過,所以問題很明顯.

但若是爆ping都剛好發生在每天晚上9點過後呢？
總不會每天晚上port就壞掉或是每天晚上中華電信機板都設定錯誤吧？

我是有裝cfosspeed隨時都看得到ping的數值，所以ping一不穩馬上就可發現
而且cfosspeed ping的數值是ttl=2，等於是我出路由器後第一個節點

【問題】請大家幫我判斷一下SEEDNET到底是出什麼問題

主題: 【問題】請大家幫我判斷一下SEEDNET到底是出什麼問題

主題工具