|
 | 作者: mongwuheng [mongwuheng]
 论坛用户 |
登录 |
| 我公司的网络，经常会变得奇慢，网络拓扑是主干一台16口交换机，下面级联三台HUB（六口），还有四五台电脑直接连接到主干交换机。速度变慢时， 只要把其中一台连接了六台电脑的HUB重启后等一会就会快，但过了十来天又会变慢，ping深圳DNS(202.96.134.133)的time值达到了1000ms，局域网电脑根本上不网！很烦人的，真不知什么原因？请位哪位高手指点，请说明原因？ [此贴被 梦无痕(mongwuheng) 在 02月11日10时17分 编辑过] |
| 地主 发表时间: 04-02-10 16:31 |
 | 回复: tuzi [tuzi]  版主 |
登录 |
|
速度变慢时， 只要把一台连接六台HUB的重启后等一会就会快，？？ 不是说 3个HUB 怎么又6台HUB了 什么东西连6台HUB呀 HUB连的是什么呀 拓扑具体一点 症状描述详细一点 再加上自己的调试过程 [此贴被 带脚镣跳舞(tuzi) 在 02月10日16时41分 编辑过] |
| B1层 发表时间: 04-02-10 16:40 |
 | 回复: koolboy [koolboy]  论坛用户 |
登录 |
|
我曾经也遇到过这样的事情。 当时那个公司是通过电信光纤接入的，同样也出现了你所说的问题。 你试试问问是不是电信那头的光纤的问题 |
| B2层 发表时间: 04-02-10 20:46 |
| 回复: mongwuheng [mongwuheng] 论坛用户 |
登录 |
|
不好意思，打错啦！应该是“只要把一台连接了六台电脑的HUB重启后等一会就会快” 最近几天更严重，重启这台HUB后，过几个小时，速度就变慢，Ping 202.96.134.133的timew值时常有1000多ms，时好时坏！真的好烦！！！！ |
| B3层 发表时间: 04-02-11 10:21 |
 | 回复: group [group] 论坛用户 |
登录 |
|
是不是冲击波？ |
| B4层 发表时间: 04-02-11 11:02 |
 | 回复: permino [permino]  论坛用户 |
登录 |
|
我觉得应该是有病毒，或者是有网卡有问题导致冲突域产生大量的冲突。如果没有这方面的问题，就考虑换个交换机试试。 [此贴被 俊华(permino) 在 02月11日11时40分 编辑过] |
| B5层 发表时间: 04-02-11 11:36 |
| 回复: zyh2099 [zyh2099] 论坛用户 |
登录 |
|
换个交换机吧,六个HUB这样也太影响了吧 |
| B6层 发表时间: 04-02-11 21:12 |
 | 回复: wfjxx [wfjxx] |
登录 |
|
简单把hub换成交换机就可以了呀 |
| B7层 发表时间: 04-02-12 08:58 |
| 回复: mongwuheng [mongwuheng] 论坛用户 |
登录 |
|
各位大哥呀！我敢肯定不是病毒的事，所有的电脑我都打了最新的补丁，都安装了正版最新杀毒软件，现在问题是没有规律，时好时坏，有时打开网页很慢时，我连续ping（202.96.134.133）几次就会好一会，久了时候可以好上半天，有时就是几分钟就会出现这种情况，如果是电脑多的话，有时就是两台电脑开着也会出现，但如果只一台电脑直接连接ADSL MODEM（我们伊泰克2018的，带路由功能）就不会，而且很快。以前只是偶尔出现这种现象，但最近才很频繁，我真的想不出是什么原因啦！我好歹也是一个搞网络几年的，而且通过了CCNA，真的弄不明白是怎么回事，看哪位大哥能指点迷津！！！！！ |
| B8层 发表时间: 04-02-12 09:38 |
| 回复: mongwuheng [mongwuheng] 论坛用户 |
登录 |
|
C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Reply from 202.96.134.133: bytes=32 time=451ms TTL=250 Reply from 202.96.134.133: bytes=32 time=390ms TTL=250 Reply from 202.96.134.133: bytes=32 time=571ms TTL=250 Reply from 202.96.134.133: bytes=32 time=401ms TTL=250 Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 390ms, Maximum = 571ms, Average = 453ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Reply from 202.96.134.133: bytes=32 time=351ms TTL=250 Reply from 202.96.134.133: bytes=32 time=260ms TTL=250 Reply from 202.96.134.133: bytes=32 time=260ms TTL=250 Reply from 202.96.134.133: bytes=32 time=510ms TTL=250 Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 260ms, Maximum = 510ms, Average = 345ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Reply from 202.96.134.133: bytes=32 time=691ms TTL=250 Reply from 202.96.134.133: bytes=32 time=360ms TTL=250 Reply from 202.96.134.133: bytes=32 time=501ms TTL=250 Reply from 202.96.134.133: bytes=32 time=260ms TTL=250 Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 260ms, Maximum = 691ms, Average = 453ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 202.96.134.133 Pinging 202.96.134.133 with 32 bytes of data: Reply from 202.96.134.133: bytes=32 time=90ms TTL=250 Reply from 202.96.134.133: bytes=32 time=170ms TTL=250 Reply from 202.96.134.133: bytes=32 time=160ms TTL=250 Reply from 202.96.134.133: bytes=32 time=100ms TTL=250 Ping statistics for 202.96.134.133: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 90ms, Maximum = 170ms, Average = 130ms C:\> |
| B9层 发表时间: 04-02-12 09:41 |
|
20CN网络安全小组版权所有
Copyright © 2000-2010 20CN Security Group. All Rights Reserved.
论坛程序编写：NetDemon
粤ICP备05087286号
论坛: 系统集成
标题: 网速为什么经常变慢？