Re: PROBLEM IN MY LAN
- From: "Pegasus \(MVP\)" <I.can@xxxxxxx>
- Date: Sun, 30 Apr 2006 12:50:31 +1000
"bemudia77" <bemudia77@xxxxxxxxx> wrote in message
news:1146334899.956104.21100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a cafe that about 20 computers linked together by my local area
network
The internet link entering my server is quite fast but as all the
computers are put on the speed becomes very very slow
after trobleshotting i realised that it is usually one or two system
that is making other computer browse slowly.
when this troubled computers are removed from the network, other
computer speed increases and after formatting the computer and changing
the LAN card the proble stops.
when i ping my IP below is the result i get
Ping statistics for xxx.xx.xxx.x:
Packets: Sent = 291, Received = 63, Lost = 228 (78% loss),
Approximate round trip times in milli-seconds:
Minimum = 541ms, Maximum = 912ms, Average = 141ms
Control-Break
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for xx,xx,xxx,xxx:
Packets: Sent = 332, Received = 63, Lost = 269 (81% loss),
Approximate round trip times in milli-seconds:
Minimum = 541ms, Maximum = 912ms, Average = 124ms
Control-Break
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.88.128.1: bytes=32 time=600ms TTL=253
Reply from 80.88.128.1: bytes=32 time=591ms TTL=253
Reply from 80.88.128.1: bytes=32 time=651ms TTL=253
Reply from 80.88.128.1: bytes=32 time=551ms TTL=253
Reply from 80.88.128.1: bytes=32 time=661ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.88.128.1: bytes=32 time=671ms TTL=253
Reply from 80.88.128.1: bytes=32 time=581ms TTL=253
Reply from 80.88.128.1: bytes=32 time=580ms TTL=253
Reply from 80.88.128.1: bytes=32 time=631ms TTL=253
Reply from 80.88.128.1: bytes=32 time=650ms TTL=253
Reply from 80.88.128.1: bytes=32 time=681ms TTL=253
Reply from 80.88.128.1: bytes=32 time=701ms TTL=253
Reply from 80.88.128.1: bytes=32 time=761ms TTL=253
Reply from 80.88.128.1: bytes=32 time=621ms TTL=253
Request timed out.
Reply from 80.88.128.1: bytes=32 time=560ms TTL=253
Reply from 80.88.128.1: bytes=32 time=551ms TTL=253
Reply from 80.88.128.1: bytes=32 time=661ms TTL=253
Reply from 80.88.128.1: bytes=32 time=561ms TTL=253
Reply from 80.88.128.1: bytes=32 time=691ms TTL=253
Reply from 80.88.128.1: bytes=32 time=541ms TTL=253
Reply from 80.88.128.1: bytes=32 time=621ms TTL=253
Reply from 80.88.128.1: bytes=32 time=581ms TTL=253
Reply from 80.88.128.1: bytes=32 time=691ms TTL=253
Reply from 80.88.128.1: bytes=32 time=601ms TTL=253
Reply from 80.88.128.1: bytes=32 time=691ms TTL=253
Reply from 80.88.128.1: bytes=32 time=600ms TTL=253
Reply from 80.88.128.1: bytes=32 time=681ms TTL=253
Reply from 80.88.128.1: bytes=32 time=661ms TTL=253
Reply from 80.88.128.1: bytes=32 time=631ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.88.128.1: bytes=32 time=982ms TTL=253
Request timed out.
Reply from 80.88.128.1: bytes=32 time=962ms TTL=253
Reply from 80.88.128.1: bytes=32 time=851ms TTL=253
Request timed out.
Request timed out.
Reply from 80.88.128.1: bytes=32 time=711ms TTL=253
Request timed out.
Reply from 80.88.128.1: bytes=32 time=621ms TTL=253
Request timed out.
Reply from 80.88.128.1: bytes=32 time=721ms TTL=253
Request timed out.
Reply from 80.88.128.1: bytes=32 time=761ms TTL=253
WHAT I WANT TO KNOW IS IF THERE IS A WAY THE PROBLEM OF ONE COMPUTER
WILL NOT AFFECT OTHERS
THAT IS IF ONE COMPUTER HAS ANY PROBLEM IT WILL NOT AFFECT THE SPEED OF
OTHER COMPUTER IN THE NETWORK.
I look forward to getting a reply from you
Thank you
Bemudia Smith
bemudia77@xxxxxxxxx
When pinging PCs connected to your internal network then
all packets must arrive. Time-outs indicate a serious networking
problem. It could be due to one of the following:
- Bad cables
- Bad connectors
- Incorrectly fitted connectors
- Bad network adapters
- Faulty switch
- Strong interference, e.g. from mains cables in the same cable duct.
You can identify the culprit by a process of elimination.
And by the way, please do not write whole paragraphs
in your post in upper case. In newsgroup etiquette it is
referred to as "shouting", and nobody likes to be shouted
at.
.
- Prev by Date: Re: Lost "My Documents" when cleaning up user accounts
- Next by Date: Re: File Sharing (CIFS) Proxy
- Previous by thread: after a ftp put command it just says "200 PORT command successful." and hangs forever. What could be wrong? when i test the ftp server using IE in "passive" mode it works fine. but ftp at command line hangs on "200 PORT command successful." after i enter p
- Index(es):
Relevant Pages
|