The following message is a courtesy copy of an article
that has been posted to comp.protocols.ppp as well.
James Carlson <[EMAIL PROTECTED]> writes:
> Graham Coles <[EMAIL PROTECTED]> writes:
>> I have been setting up a PPP dialup connection on a Sun Solaris (SPARC)
>> box running Sunos 5.5
>
>Using aspppd? I think pppd works better.
>
> > I was told by the Ras server people that they were expecting a
> > config-nak instead of config-rej and it was due to receiving the reject
> > message that their server terminated the connection negotiation. I was
> > assuming that with auth=chap rejected the RAS box would retry with
> > something like auth=PAP before giving up.
>
> Yep. This is a rather common implementation bug. LCP Configure-
> Reject is entirely wrong here. It means "I don't know how to
> negotiate authentication protocols at all, so do not send me this
> option again." The correct answer, as you were given by the RAS
> folks, is that it should be sending LCP Configure-Nak and hinting a
> different authentication protocol.
>
> > I'm guessing that the RAS box is expecting "config-nak auth=pap
> > auth=none" or something similar.
>
> Yep.
>
Ah.. I've got the same problem on a Linux installation of ppp-2.3.7
because, when I set noccp in the options file, pppd sends ProtRej and
without it the ConfRej is sent. Any solution you know of for pppd?
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
