RE: Why is PPP so screwed up!?!?!
On Sat, 1 Mar 1997, Peter Iannarelli wrote:
> The ISP has nothing to do with it. There is a systematic
> approach to setting up anything. Before one can resolve
> an issue one must understand the problem.
> The approach is:
>
> 1: manually dial up and log into your ISA
> 2: edit the respective files so that the proper
> strings are looked for and responded with
> 3: adjust the protocol config files accordingly
>
> Just a not, there is one thing missing in the
> distributed etc/ppp/options files "defaultroute".
> That if the ISA is the primary DNS.
>
Hmmm... that's of course assuming everything goes smoothly in steps 1-3.
There are certain setups in which when you dial in using a terminal, it
activates a shell account, but when you dial in using the Win95 PPP setup,
it becomes PPP, so manually dialing in does nothing for you.
You have to assume that PPP is somehow passively established, but you
don't know what the delay period is, since there is no easy way to monitor
what Win95 does during a PPP negotiation. Also, such services as AT&T,
AOL dervitives, etc. have proprietary dialers which dialin scripts which
you can't easily access or figure out. A manual dial in does not
necessarily work in such circumstances because even the user password is
not accepted at the boot prompt... you get the picture...
Then of course you have to determine whether PPP is passively or actively
activated, whether it requires PAP/CHAP authentication, whether your need
to specify the defaultroure, etc. etc.
In other words, a lot of headaches.
Will
Reply to: