A config would help (minus all passwords, phone numbers, etc.).
The MAX doesn't allow a dialin user to authenticate it (i.e., it doesn't
support a CHAP challenge from the router dialing into it). At least this
was true in most past releases. This could cause your CHAP problem.
LQM is Line Quality Monitoring. If you have bad lines (lots of errors)
this might be useful. If not, then it isn't needed.
Chip
At 10:49 PM 5/12/97 +0400, Basil Dolmatov wrote:
>Hello!
>
> Some fresh news from battlefield... ;))
>
>One part of problem were successfully solved. It was really LCP problem,
>due to the fact that on Max LCM (LQM?) was enabled and it was not
understood
>by Cisco. When this option was disabled on Max LCP negotiation became
>successful.
>
>Question no.1:
> What the hell is this LCM (LQM?)?? People on Ascend side claimed that
it
>is standard PPP feature. How it can be enabled on Cisco and could that
be
>enabled at all?
>
>Now, we are moved forward and stopped again. :(
>Ascend clearly refuses to authenticate us. All names and passwords were
double-
>and triple-checked without any success. Usernames are OK, they are seen
in
>dump, so we caould check them...
>
>Question no.2:
>Could it be some feature in Ascend, which changes authentication
options?
>Maybe something like LCM (see above)? ;)
>Authentication through ordinary login is successful, so Ascend works and
>authenticates well... But... It receives plaintext password during
login,
>and in PAP/CHAP it receives encrypted password. So...
>
>Question no.3:
>As far as I could understand CHAP logic (I am not guru, so can say
saomething
>dumb now), it gives some ID, and encrypted version of something. Response
to
>that request demands encryption of something with password on responder's
side.
>But... All passwords, which I put in Cisco config, become encrypted with
some
>"7th degree" aglorithm, which, AFAIR, has _no_ reverse. That is, it is
usable
>for password checking, but it is unusable for encrypting of anything. Am
I
>wrong? I have found nothing which could help me to place unencrypted
password
>in Cisco config, so I suspect, that when encrypting this "something"
Cisco
>cannot use proper password. Seems that I am definitely wrong in this,
but
>it would be great, if someone, who knows better, explain that in detail.
>
>Question no.5:
>I have got replies from people, successfully using Cisco->Ascend line
(thanks
>them a lot), but have had no reply from people, who are on the Ascend
side
>of such lines... From Cisco side our configs look identical, so I
suspect,
>that some peculiarities are present on Ascend side and asks those, who
can
>say something about Ascend to find the time and reply me.
>
>Finally, Cisco dumps of unsuccessful authentications, maybe someone will
>point to me to something significant in them. I have seen nothing. :(
>
...snip...
-------------------------------------------------------
Hascall H. ("Chip") Sharp voice: +1 (919) 472-3121
Consulting Engineer-ISP email: chsharp@cisco.com
Cisco Systems
---------------------------------------------------------
To subscribe to cisco-nsp send "subscribe" to
cisco-nsp-request@cic.net
---------------------------------------------------------
=============================================================================
"inet-admins" Internet access mailing list. Maintained by East Connection ISP.
Mail "unsubscribe inet-admins" to Majordomo@east.ru if you want to quit.
