Whoops! Just realized you've got the same IP address configured on your serial 0 AND
serial 1 interfaces and that you've been trying to ping your serial 1 interface. I
see why Serial 0 is shut down.
As many have pointed out, access lists on the other end of the link can affect your
ability t
I looked at your config. You are using the
interface-dlci command on the physical interface. Most
people use the interfacce-dlci command on
subinterfaces and map statements on physical
interfaces. I don't have a lab to try this on but if
you use a subinterface and the interface command I
think
x27;[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Subject: FW: can't ping or reach serial port
>Date: Fri, 25 Aug 2000 01:12:46 -0500
>
>relying on you guys for help again
>
>Jason
>
>-Original Message-----
>From: Yee, Jason
>Sent: Friday, August 25,
ubject: FW: can't ping or reach serial port
relying on you guys for help again
Jason
-Original Message-
From: Yee, Jason
Sent: Friday, August 25, 2000 11:39 AM
To: '[EMAIL PROTECTED]'
Subject: FW: can't ping or reach serial port
hi with regard to my last problem I
relying on you guys for help again
Jason
-Original Message-
From: Yee, Jason
Sent: Friday, August 25, 2000 11:39 AM
To: '[EMAIL PROTECTED]'
Subject: FW: can't ping or reach serial port
hi with regard to my last problem I have removed the access-group commands
on seria
hi with regard to my last problem I have removed the access-group commands
on serial 1 and still I can't ping to serial's 1 ip address and ie
202.161.128.30, surprisingly I can telnet via this interface and I can ping
to the next hop 202.161.128.29 but I can't just ping to 202.161.128.30
I am rea
6 matches
Mail list logo