OK. Good report. Nice and clear.
Here's what is significant: the other end is not responding to your ppp
initiation *after* authentication. You see that here in the chat messages:
>Aug 5 21:24:33 debian pppd[442]: Connect: ppp0 <--> /dev/modem
>Aug 5 21:24:50 debian pppd[442]: peer refused to authenticate
>Aug 5 21:24:50 debian pppd[442]: Connection terminated.
Everything else that goes wrong is the result of this failure, so focus on
this part and fix it.
So ... what's wrong? I can only guess that the particular userid and
password you are entering do not start a PPP session. You need to
investigate this. Here's how.
Start minicom. Use it to dial the number and enter the userid and password.
After the password gets accepted, see what happens. Possibly you'll be at a
shell prompt, from which you'll need to run ppp manually. Possibly it's the
wrong account and you need to do a 3-step login -- MSN, then userid, then
password. Possibly the password won't be accepted (maybe your userid really
is MSN/davidturetsky, like the docs you quote say). Possibly it's weirder
than that.
But you need to test possibilities. You do not have a Linux problem here;
you have a problem of not knowing what your ISP wants you to do to start a
PPP session.
It might help if you tell us *exactly* how the Windows host is set up to
initiate PPP. Assuming you're using the standard TCP stack, what is in the
userid field of its "properties"?
At 10:11 PM 8/5/00 -0700, davidturetsky wrote:
>Progress to report!
>
>In looking around further, I noticed in /etc/ppp/connect-errors:
>
>sh: my-chat-script: command not found
...
--
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
