home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #19 / NN_1992_19.iso / spool / comp / dcom / sys / cisco / 1237 < prev    next >
Encoding:
Internet Message Format  |  1992-09-03  |  1.3 KB
  1. Xref: sparky comp.dcom.sys.cisco:1237 comp.sys.novell:7000
  2. Newsgroups: comp.dcom.sys.cisco,comp.sys.novell
  3. Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!sgiblab!newsun!donp
  4. From: donp@novell.com (don provan)
  5. Subject: Re: Cant get 3.11 IP router to PING
  6. Message-ID: <1992Sep4.063753.22322@novell.com>
  7. Sender: usenet@novell.com (The Netnews Manager)
  8. Nntp-Posting-Host: na.novell.com
  9. Organization: Novell, Inc., San Jose, California
  10. References: <1992Sep3.205909.1@cc.uvcc.edu>
  11. Date: Fri, 4 Sep 1992 06:37:53 GMT
  12. Lines: 23
  13.  
  14. In article <1992Sep3.205909.1@cc.uvcc.edu> coleve@cc.uvcc.edu writes:
  15. >Q1:  Is a healthy 3.11 IP router supposed to PING?
  16.  
  17. Yes.
  18.  
  19. >Q2:  If so, what can stop it?
  20.  
  21. Nothing.  Consequently, it either isn't healthy or it isn't receiving
  22. the ping requests.
  23.  
  24. Since i don't see any obvious problems with your picture, my guess is
  25. that the picture you've drawn does not entirely agree with the actual
  26. configurations of the systems involved.  I imagine the TCPCON routing
  27. table should tell you a lot.  You might also point TCPCON at the Cisco
  28. and check out its routing table as well.
  29.  
  30. >Q3:  (more advanced)  Do I need to worry about re-distributing the RIP
  31. >derived routing info out to westnet?
  32.  
  33. I don't see any cause to worry, but perhaps i'm missing what concerns
  34. you.
  35.                         don provan
  36.                         donp@novell.com
  37.