Most likely the option "auth" was set by mistake. Then the other side is required to be authorized.
Like in the last question, an option has been set that requires the other side to be authorized. These options shouldn't be set. Possible candidates are: "+pap" as well as "+chap".
Your computer is refusing to identify itself with user name (e.g. XXX) and password (e.g. YYY). That only works with the authorization options "user XXX" and "remotename YYY" for ipppd or pppd together with a correct (!) /etc/ppp/pap-secrets. With a password of ZZZ it should ideally look like this:
XXX YYY ZZZ *
* * ZZZ *
http://www.lrz-muenchen.de/~ui161ab/www/isdn/Also have a look at the next question: pap_passwd.
Use the options
+pwlog for ipppd or pppd. Then you can
see your password in the log file.
Stefan A. Muehlenweg
Stefan.A.Muehlenweg@samhh.hanse.de wrote on
4 Oct 1996:
I had exactly the same problem/the same error message. The cause for it was that I had three entries in chap-secrets/pap-secrets (for client, server, secret), but not a fourth one (IP addresses). BUT: after the third entry were some BLANKs. After removing the trailing BLANKs and/or TABs (i)pppd is now very satisfied with my auth-files.A further source of problems can be the password itself. If it contains the "#" character, then everything after than is understood as a comment. Spaces or tabs can cause similar problems. Solution: put the password in quotes!