home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!uwm.edu!biosci!agate!boulder!recnews
- From: ddunwood@dsc.blm.gov (Dave Dunwoodie 6042)
- Newsgroups: comp.dcom.sys.cisco
- Subject: IGS 9.0(1) HELLLLP!!!
- Message-ID: <722540755.23328@news.Colorado.EDU>
- Date: 20 Nov 92 16:27:16 GMT
- Sender: news
- Lines: 13
- Approved: news
- X-Mailer: SCO System V Mail (version 3.2)
- X-Note1: mail msgid was <9211200927.aa06863@dsc.blm.gov>
- X-Note2: message-id generated by recnews
-
- I have 2 routers connected by ethernet. One (a 3-COM) connects me
- to the internet. The other (the Cisco) is managing our routing to
- an X.25 network. If I login in to the Cisco and try to ping
- the 3-COM, it chokes. What's the deal here?
- I've tried a default route on the Cisco that points as:
- 0.0.0.0 158.68.31.254. No go. I tried taking it out.
- No go.
- The bottom line is that our X.25 clients can't get any further
- than our Campus LAN as the Cisco isn't connecting to the other
- router to get the caller to his internet target.
- The two routers are on the same physical and logical network.
- The cisco: 158.68.31.253, the 3-COM: 158.68.31.254. There's
- gotta be a way to get packets from one to the other!
-