Larry Fletcher wrote:
>
> >Larry Fletcher wrote:
> >> The first time I tried pppconfig it worked perfectly, but I just tried
> >> to change the phone number and now it won't connect. (The only change
> >> is the phone number, everything else is the same.)
> >>
> >> I tried deleting /etc/ppp/peers/provider in an effort to erase the
> >> defaults and start over, but when I ran pppconfig the defaults were
> >> still there. What files should I delete to get pppconfig back to where
> >> it was when I first installed hamm?
>
> John Leget <[EMAIL PROTECTED]> wrote:
> >Also check out the files in /etc/chatscripts/... these are used as well, i
> >just manually changed the phone no here recently.
>
> I wish I would have done it manually, but it's to late now. I think the
> problem was caused by accidentally selecting PAP instead of CHAT, but I did
> this the first time used pppconfig and it didn't cause a problem then. The
> only difference is I changed back to CHAT before I used pon the first time.
>
> I finally found all of the pppconfig files in pppconfig manual and deleted
> them. Then I ran pppconfig again, but I still have the same problem. I
> also looked though the PPPD and CHAT manuals and tried a couple of changes,
> but nothing helped.
>
> Below are the before and after sections of the ppp.log. The only change
> is the phone number, but the first one worked and second one doesn't.
Warning: I'm not an expert on this issue. Also, I'm running
slink, and there have been changes to the whole ppp situation
(file locations and names, etc.) since hamm (I think, it seems to
have been a long time since hamm).
From the log it looks as if the second number wants a pap
connection, while the old number doesn't ask for it.
> Feb 20 20:36:01 debian pppd[216]: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0>
> <magic 0x30fe74d6> <pcomp> <accomp> <auth pap>]
^^^^^^^^^^
> Feb 20 20:36:01 debian pppd[216]: sent [LCP ConfAck id=0x1 <asyncmap 0x0>
> <magic 0x30fe74d6> <pcomp> <accomp> <auth pap>]
^^^^^^^^^^
In the second log, it seems to fail because of a lack of a proper
login name and password for the PAP connection.
> Feb 20 20:36:04 debian pppd[216]: sent [LCP EchoReq id=0x0 magic=0xffff0041]
> Feb 20 20:36:04 debian pppd[216]: sent [PAP AuthReq id=0x1 user="ay903"
> password=""]
> Feb 20 20:36:04 debian pppd[216]: rcvd [LCP EchoRep id=0x0 magic=0x30fe74d6]
> Feb 20 20:36:05 debian pppd[216]: rcvd [PAP AuthNak id=0x1 "Invalid Login"]
> Feb 20 20:36:05 debian pppd[216]: Remote message: Invalid Login
> Feb 20 20:36:05 debian pppd[216]: PAP authentication failed
Have you setup the pap-secrets file with a line like this at the
bottom of the file in the 'OUTBOUND CONNECTIONS' section? It
looks like this:
login_user_name * my_password
First, start with a fresh set of config files (force a reinstall
of ppp and then pppconfig), and then use minicom to verify exactly
what your ISP wants to see. This may have remained the same, but
verify it anyway. When the ISP starts sending what looks like
garbage in the minicom terminal, thats the PAP request you are
seeing. Verify your name and password are the same for the
pap-secrets file as well as the chatscript file. Also make sure
'noauth' is in your provider file (a parameter send to pppd).
'auth' would cause your machine to interrogate your ISP's machine
for a PAP connection, which won't work, of course, as the
situation is the other way around.
Hope it helps.
--
Ed C.
