> I have a customer using Win 3.x with Trumpet who we're having a heck of a
> time connecting. The debug session on the pm2E shows LCP going smoothly
> & then we get an error "Cannot CHAP S1 Not allowed."
This happens when the remote computer has negotiated to authenticate
via PAP and then attempts to authenticate via CHAP. You can watch and
decode the LCP negotiations if you like:
Command> set console
Command> set debug 0x51
Now have the user dial in. You can stop the debugging infomation this way:
Command> set debug
> Now I know from the docs that I need to add lines to my RADIUS user config
> to implement CHAP, but I don't necessarily want to unless I have to.
Hmmm. I don't recall RADIUS enteries for CHAP. Shouldn't be necessary
in any case.
> My question is why this error is showing up from just this one user.
> Is there a setting that he has set that is requesting CHAP that is not
> readily apparent in the Trumpet or Win 3.x modem setup settings? Or
> do I need to accept CHAP?
Yes, the user needs to examine his configuration for CHAP. There really
isn't much you can do as it is the LCP negotionation agreement of PAP
followed by his atempt at CHAP that is causing the problem.
JGT
-- John G. Thompson Livingston Enterprises Inc. Phone: (800) 458-9966 JOAT(MON) 6920-220 Koll Centre Pkwy. Fax: (510) 426-8951 support@livingston.com Pleasanton, CA 94566 http://www.livingston.com