Use PAP, not CHAP.Quote:>I got two linux boxes connected by ppp, basic
>connection, no authorization. I try to dialin with Win95, and then Win95 times
>out saying that it's "can't negotiate a compatible protocol". I'm set up where
>my Linux Server dictates local and remote IP address (ie. x.x.x.x:y.y.y.y in
>the options file). I'm experimenting with 'usehostname', 'remotename <n>', and
>'domain <d>' options for CHAP, but no luck yet. Thank's in advance for any
>help.
--
Use PAP. Try the 'auth +pap login' options to pppd to make it useQuote:>Does anybody know what Win95 PPP links try to negotiate? What is it looking
>for as far as PAP or CHAP?
/usr/local/bin/pppd auth -chap +pap login kdebug 0
Plus, our usual /etc/ppp/options file(s). Main things in there
are IP address and 'modem crtscts proxyarp'.
---
Wasatch Communications Group http://www.wasatch.com
> Does anybody know what Win95 PPP links try to negotiate? What is it looking
> for as far as PAP or CHAP? I got two linux boxes connected by ppp, basic
> connection, no authorization. I try to dialin with Win95, and then Win95 times
> out saying that it's "can't negotiate a compatible protocol".
Regs /Lars
/usr/sbin/pppd -detach passive auth +pap /dev/ttyE0 38400
with the following in /etc/ppp/options:
crtscts
modem
asyncmap 0x00000000
mru 1000
mtu 1000
and the local and remote ip addresses in /etc/ppp/options.ttyE0
In /etc/ppp/pap-secrets, we have the expected
<username> * <password>
for each of our customers.
The serial port has a modem attached to it, so as soon as the modem
answers, the pppd process tries to do its thing and connect to the dial in
client.
Works great with Windows 95, Macs with FreePPP or MacPPP, and other linux
hosts. Doesn't work so well with Netscape Personal Edition under Windows
3.1. Don't know why yet.
Aaron Magill
--
Internet System Coordinator
Flying Color Graphics Inc.
1. mgetty / AutoPPP Win95 dialin ok, linux dialin NG!
I've got it set up such that 95 / NT clients can dial my Linux 2.0.29
server with no problem and get a ppp connection every time. Linux
doesn't do as well. In fact not at all. I can dial in with minicom,
but with a PROVEN set of two scripts (that I used to write this posting)
I get no connection. Mgetty sees my linux client as a standard dialin,
and doesn't fire off AutoPPP as defined in
/etc/mgetty+sendfax/login.config.
It's such a mystery that win95 and NT work, and Linux can't do it. My
NT nerds at work are really breaking my
chops bad, so any help to get this working will allow me to smush linux
in their faces but good.
I've tried several options and configs on the client and server end,
with no success. If anyone is successfully accomplishing this between
two linux boxes, please privilege me with the config files, or if you're
a guru, privilege me with your advice. FAQ / HOWTO served no help. I
surfed for three days before I decided to waste everyones resources.
I really need help.
Tanx
freddy wissing
2. a command execution question
3. PPP difficulties with win95 dialing to linux via ppp.
5. Linux/Win95 to Linux Box Via Null-Modem, then to Internet
6. documentation/specification for ext2fs and iso9660
7. Linux PPP Server + Win95 Dialin
9. Linux PPP-server + Win95 DialIn
10. How to connect a linux box with a win95 box or OS/2 box?
11. Connecting a WIN95 & Linux Box via Direct Cable Connection
12. Help: Routing.. (linux->net via win95 box)
13. How to : Win95 PC -- > (via Linux box) --> login to WinNT server