Re: Debugging Gandalf 5242
Melissa Lanning ((no email))
Tue, 24 Sep 1996 11:57:09 -0700 (PDT)
I've seen this problem a couple times now...it seems to be caused by one of the boxes in questions sending out a CHAP request, and the PM gets a packet back from the Gandalf saying, basically "i'm not doing CHAP." The way around this is
to set both the PM and the Gandalf to do PAP only. If you are only doing PAP, then this message can be ignored.
Be aware, though, that getting Gandalfs and PM's to authenticate ISDN is never
easy. The only way I have ever been successful trying this was by making sure that the client secret and peer secret matched (these are the terms the Gandalf customer used.)
Good luck..
Melissa
>
>
> One of our customers is having problems connecting too. Is there a bug
> in the Livingston or is it the Gandalf?
>
> On Sun, 22 Sep 1996, Kevin Kadow wrote:
>
> > When connecting from a Gandalf 5242, authentication fails. When trying CHAP
> > I get the following:
> > Received LCP_CONFIGURE_REQUEST on port S13 of 21 bytes containing:
> > 01 3a 00 19 01 04 05 ee 03 05 c2 23 05 05 06 64
> > 00 11 30 07 02 11 04 05 ee
> > Sending LCP_CONFIGURE_ACK to port S13 of 25 bytes containing:
> > 02 3a 00 19 01 04 05 ee 03 05 c2 23 05 05 06 64
> > 00 11 30 07 02 11 04 05 ee
> > Received LCP_CONFIGURE_NAK on port S13 of 4 bytes containing:
> > 03 0e 00 08 03 04 c2 23
> > Sending LCP_CONFIGURE_REQUEST to port S13 of 14 bytes containing:
> > 01 0f 00 0e 05 06 2e 98 4e 8f 11 04 06 1c
> > Received LCP_CONFIGURE_ACK on port S13 of 10 bytes containing:
> > 02 0f 00 0e 05 06 2e 98 4e 8f 11 04 06 1c
> > S13: LCP Open
> > Couldn't CHAP on port S13 - Not allowed
> > Received CHAP_CONF_CHALLENGE on port S13 of 13 bytes containing:
> > 01 01 00 0d 04 83 82 b7 18 72 64 65 77
> > Sending CHAP_CONF_RESPONSE to port S13 of 27 bytes containing:
> > 02 01 00 1b 10 51 af e7 7a 7c 17 91 59 98 c8 a5
> > 79 df ef c2 63 68 79 64 72 61 34
> > Sending LCP_TERMINATE_REQUEST to port S13 of 4 bytes containing:
> > 05 10 00 04
> > Connection Failed
> >
> > Why the 'Couldn't CHAP on port S13 - Not allowed' ?
> >
> > What's going wrong?
> >
>