Thanks for all the help.  It turns out that I just don't know enough about
ISDN.  I could actually make the call and showed this with the "show isdn
status", and "debug dialer". I'm not sure that I actually needed to put in
the ppp authentication chap command; seemed like it worked anyway before I
did that.   I also did a "debug ppp negotiation" and that showed "install
route to 192.168.x.x"  So, the call was good through layer 3, but the
customer had to get rid of his access list before I could ping.  Sometimes
you have to do so much just to prove/confirm everything is good on your side
before the customer will admit something is configured wrong on his side...

  Note: forwarded message attached. 



---------------------------------
Do You Yahoo!?
Yahoo! Auctions $2 Million Sweepstakes  -  Got something to sell?
X-Apparently-To: [EMAIL PROTECTED] via web5104; 21 May 2001
  22:08:03 -0700 (PDT)
X-Track: 1: 40
Received: from mail.ureach.com  (EHLO ureach.com) (63.150.151.36) by
  mta205.mail.yahoo.com with SMTP; 21 May 2001 22:08:02 -0700 (PDT)
Received: from www20.ureach.com (IDENT:[EMAIL PROTECTED]
  [172.16.2.48]) by ureach.com (8.9.1/8.8.5) with ESMTP id BAA09666;
  Tue, 22 May 2001 01:07:31 -0400
Received: (from nobody@localhost) by www20.ureach.com (8.9.3/8.9.1) id
  BAA32299; Tue, 22 May 2001 01:07:31 -0400
Date: Tue, 22 May 2001 01:07:31 -0400
Message-Id: 
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
  "[EMAIL PROTECTED]" 
From: Paul Werner 
Reply-to: 
Subject: Re: Subject: ISDN [7:5295]
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-vsuite-type: e
Content-Length: 2252

A couple of thoughts on this issue(some generic, some specific 
to your problem):

1.  What results do you get with "show isdn status"?

2.  While running "debug dialer" during this ping, is a cause 
code reflected for dial?  Specifically, is it attempting to 
dial out at all?  Do you have the following statement present 
on this router:

dialer-list 1 protocol ip permit

or something closely similar?

3.  I noted the absence of the following line under the 
interface config:

ppp authentication chap

That might likely cause the PROTREJ message you saw(although it 
could be for other protocols requested).  You probably need to 
copy a sample of the debug to get a better answer. 

4.  What does the other router config look like?

5.  Was this previously working, or is the first time this 
circuit came up?

-Need more input...and configs/debugs

HTH,

Paul Werner


> Please help, I can't ping the remote side of this ISDN 
connection.
> 
> Here is the config AND the log with debug ppp negotiation 
showing a
> PROTREJ(toward the end of output).  Does that mean PPP is not 
working or
> setup right?
> 
> When I ping the remote, the call is made to the customer but 
I don't get
> a
> reply.  Also, if I show ip route after I ping(while the line 
is still
> up) I
> see a route like this 192.168.2.58/32 what does the /32 mean-
I know it's
> subnet bits but how is it 32?  Before the dialer makes the 
call if I
> show ip
> route I see it as 192.168.2.56/29(I'm 192.168.2.57 and 
customer is
> 192.168.2.58) The rest of the output show what happens when I 
ping the
> other
> side with debug ppp negotiation on.  Thanks for any help.
> 
> isdn switch-type basic-ni1
> !
> interface BRI0/0
>  ip address 192.168.2.57 255.255.255.248
>  encapsulation ppp
>  isdn spid1 9258255950xxxx
>  isdn spid2 9258255957xxxx
>  dialer idle-timeout 57
>  dialer map ip 192.168.2.58 name customer 1904296xxxx
>  dialer-group 1
>  ppp chap hostname service
>  ppp chap password xxxxxxx
> 
> ping 192.168.2.58
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 192.168.2.58, timeout is 2 
seconds:

________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=5484&t=5295
--------------------------------------------------
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