did you try putting on the clock rate on the dce end of the cable. to tell
what end you have, do a show controllers s on the interface you are using.
dont trust what the cable says physically on it.

-----Original Message-----
From: mark
To: [EMAIL PROTECTED]
Sent: 5/9/02 12:18 PM
Subject: Let the flamin' begin....dumbass beginner question [7:43759]

I originally configured and maintain several Cisco routers at work so
I'm
not a TOTAL dumbass when it comes to routers but I sure do feel like one
about now.
I have a couple of 2500's and a 2600 router with a couple of back to
back
cables. I'm not doing something correctly to allow the units to talk to
each
other using those cables. I can telnet into each router or connect via
console connection and all are working. The green lights come on the
serial
connections when the b to b cables are plugged in but I can't for the
life
of me get them to talk to each other. Can't ping from one serial port on
subnet A thru the b-to-b cable to the serial port on the other router on
the
same subnet on any of the routers. I have checked and rechecked ip info
on
all. I have tried frame-relay and PPP (which I would NOT trust my
configuraion of but I do know frame OK - or at least I thought I did). I
have RIP and EIGRP enabled on all and have them redistributing. I have
tried
the DCE and the DTE at each end. This is what maybe the particularly
dumbass
question - Do I need to set a clock rate or data rate for a frame
connection
using these cables? If so the commands required would be helpful. I can
look
at the options available. I just need to know where to start with them.
If
it's not a clock rate issue, have I given enough info for anyone to give
me
an educated guess as to what I'm doing wrong? If not, what other info
can I
provide?
Muchas gracias.

Mark "Gump"




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=43763&t=43763
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to