9 replies
by fendi86
by fendi86
by gpwruck
by fendi86
by dlw6
There are several ways to do this, but the best approach is to do the easy tests first to narrow down the problem.
In preparation, get an accurate LAN diagram that shows how everything is connected and the IP addresses (or equivalent for whateverprotocol you're running).
Start with a connectivity test, such as PING. Use the LEDs on the network cards, hubs, switches, and routers to watch for traffic while your PING is running.
If the PING fails, you can use TRACERT (Winxx) or TRACE (Cisco) to determine where the path has failed. Recommend you use the " -d" switch to speed it up.
From there, you can start testing the node that failed the trace and/or the cables on both sides of the failed node.
Testing a PC, hub, router, etc. will vary based on what it is. You can start by determining which machines can talk to each other, to narrow down the problem.
Testing cables requires testing equipment such as the COMPAS or some lesser tester.
That's all I can tell you without more info.
Good fortune,
Don
by fendi86
by fendi86
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending