-=> Quoting David Calafrancesco to David Richardson <=-
 DC> David Richardson wrote in a message to All:
 DR> If anyone is connecting Warp 3.0 with an ISP using PAP can
 DR> you point me in the right direction? If your not using
 DR> PPPDIAL could you tell me what software your using for a PAP
 DR> connect?
 DC> I believe InJoy v1.1 will do PAP. It is available at the authors web
 DC> site (http://www.fx.de) as well as BMT Micro and all the Hobbes
 DC> archives.
 DC> Dave Calafrancesco, Team OS/2
 DC> dave@drakkar.mhv.net
Thanks to all, for their replies about PAP!
For some reason I could not connect to http://www.fx.de (it could be
my ISP fault. I did find In-Joy v1.0 by searching shareware.com.
It does PAP real good. But I couldn't get the Dial On Demand
enabled, even after connecting and disconnection to my ISP like the
docs said... I dunno, didn't spend a whole lot of time with it and
it may have been because I had a old version plus I had to use
PKZIPFIX to unpack it... Hmmmm.
But I finally did (after many hours of work) get the command line
ppp.exe to connect to NetINS using PAP (with or without PPPDIAL29)
I have a very sparse how-to-do from the E-mail message that I sent
to the author of PPPDIAL. It's included below if your interested...
and if your not just hit Next Message :-)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> To:            don_russell@ibm.net
> Subject:       PAP (how to do)
> Reply-to:      drichardson@vax2.rainis.net
> Date:          Fri, 13 Jun 1997 11:57:33 -0600
> Don;
>
> I DONE IT -- Yahoo!  :-)
>
> I did it. I found a doc on the Internet:
> http://www.ict.pwr.wroc.pl/doc/Linux-HOWTO/PPP-HOWTO-13.html
> referring to setting up Linux with PAP & CHAP, I followed it not
> knowing whether it would be even remotely valid with OS/2 (when
your
> desperate you'll try anything)
>
> My BIGGEST problem was using +pap on the command line!
>
> This what the Linux doc said:
>
> # If you are running a PPP *server* and need to force PAP or CHAP
> # uncomment the appropriate one of the following lines. Do NOT use
> # these is you are a client connecting to a PPP server (even if it
> # uses PAP or CHAP) as this tells the SERVER to authenticate
itself to
> # your machine (which almost certainly can't do - and the link
will
> # fail).
> #+chap
> #+pap
>
> Yep my link was failing alright...
>
> Also by taking out +pap, you DO NOT need a d:\tcpip\etc\pap.sct
file!
> (This is wonderful since I don't know what's supposed to be in it
> anyway! - that same Linux doc gives me a pretty good idea however)
>
> PPPDIAL works perfect with PAP!
>
> This is my setup that works with NetINS:
>
> 'ppp.exe com3 57600 rtscts +ua netins.pap mru 1500 modem
defaultroute
> priority 1 exit  connect "pppdial.cmd d:\tcpip\bin\netins.rsp"'
>
The above three lines MUST be all on one line in your Rexx .cmd file
> This is my netins.rsp file.. minus all the junk that I have REMed
> out.
>
> WAIT
> [PPPDIAL_QUIET]
> [PPPDIAL_MAX_REDIAL] 50
> [PPPDIAL_INIT1]ath0
> [PPPDIAL_INIT2]AT&f1
> [PPPDIAL_PHONE]1-800-469-9990
>
> This is the netins.pap file:
>
> userid
> passwd
>
> (my actual userid and password)
>
> If you don't make netins.pap read only your will get this
warning:
> but it seems to work ok with write access to the secret file
>
> warn   : check_access: Warning -
>          secret file netins.pap has write access
>
> One other file that's needed on my setup is d:\tcpip\etc\resolv
> (domain name IP addresses)
> I don't think that was mentioned anywhere in the PPPDIAL doc's
>
> The re-dial capability that PPPDIAL adds is really really nice! My
> set-up  wouldn't be nearly as reliable without it, that's for
sure.
>
> Thanks for the response. Thought I would let you know that I got
it
> working, maybe you could mention how-to-do with PAP in your next
> release if and when there is one...
>
> TTYL
> David
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Blue Wave v2.12
---------------