> We've got a mix of vendor comm-servers and I want to make the PM do
> PPP only with PAP authentication only. This is so that users don't try
> to do scripted logins on our different equipment's prompts.
Hrm, what kind of hardware are we talking about? This is a portmaster
list.
I dunno if this helps but with portmasters,
I dunno if you can turn off chap. Or maybe Im confusing that with WIN 95.
I am not sure with Win 95 that you can specifiy which authentication
protocol to use, like you can with Trumpet Winsock for Win 95 which I use
instead of DUN.
But is that the issue or is the issue that you do NOT want the box
dropping to login: ?
> So I tried "set all network hardwired" since the manual says this
> immediately initiates PPP, and I *expected* it to start doing PAP with
> the client to auth, after (?) IPCP negotiation. OK, I see PPP noise
> immediately, but I get disconnected quickly after a successful LCP
> negotiation. Looks like it's not doing the PAP thing after all.
Set debug on and then capture the debug info and pipe it thru a proggie
that can tell you what is going on.
> Can someone explain this to me? If it won't do PAP, how is a hardwired
> PPP connection useful? where does it get its local:remote addresses?
> >From another "set s0 ... " type of command?
>
> If I'm being stupid, let me know. For now I'll just stick with
> "network dialin".
>
> Thanks.
>
>
>
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
Jake Messinger 713-772-6690 jake@ams.com
Advanced Medical Systems, Inc. jake@uh.edu
9919 S. Gessner #201
Houston, Texas 77071 http://www.ams.com/~jake
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~