home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.sys.cisco
- Path: sparky!uunet!fornax!skl
- From: skl@wimsey.bc.ca (Samuel Lam)
- Subject: Re: Router Problem Caused by Errant Host
- Message-ID: <1992Aug30.221545.12137@cs.sfu.ca>
- Sender: skl@cs.sfu.ca (Samuel Lam)
- Reply-To: skl@wimsey.bc.ca (Samuel Lam)
- References: <9vdnx8#.badboy@netcom.com>
- Date: Sun, 30 Aug 1992 22:15:45 GMT
- Lines: 18
-
- In article <9vdnx8#.badboy@netcom.com>, badboy@netcom.com (Jay Keller) wrote:
- >what troubleshooting techniques would have led our team to
- >discover the exact nature of the problem more quickly?
-
- When things stop working, try the following on a host that's
- inside the isolated part of the network:
-
- 1) use "ping" to see where you can't reach, then
- 2) use "tracroute" to see where that path stops, then
- 3) use "arp" to see if the IP address of the next router
- maps to the correct Ethernet address.
-
- If the test in 3) fails, the router's IP address had been stolen
- by another host on the same Ethernet.
-
- ...Sam
- --
- <skl@wimsey.bc.ca>
-