Chap in SCO ppp
I have an example of configuring non-CHAP ppp at Quick PPP setup.
I'd almost forgotten what it was like to work with dial up Internet access. Reading this post brought back memories.
It's not as bad as it might sound - the Internet was 99.99% text then and for most business use, email was almost all of the traffic - maybe a patch download or two mixed in.
From: evanh@sco.COM (Evan Hunt) Newsgroups: comp.unix.sco.misc Subject: Re: PPP on ORS - Why is it so hard to use? Date: 28 May 1999 18:58:42 GMT Message-ID: <firstname.lastname@example.org> Don't blame me, I voted for Ken Wolff <email@example.com>. >The second is to an ISP we are migrating to (because service from the ISP >mentioned above sucks). This ISP uses CHAP. How do I configure this under >OSR505? I've spent the last week trying this.
SCO PPP: Add "name=<username>" to /etc/ppphosts. Add "<name> <password>" to /etc/pppauth (or with some ISPs, including MCI and ATT/Worldnet, you need to put in a wildcard name, "* <password>"). That's all you have to do; CHAP will be turned on by the ISP during initial negotiation. MST PPP: Almost the same. Add "name <username>" to /usr/lib/mstppp/Autostart. Add "<name> <password>" or "* <password>" to /usr/lib/mstppp/Auth. IMPORTANT NOTE: Some NT RAS systems will require not just CHAP, but Microsoft CHAP, which is similar but uses a different encryption/hashing algorithm. SCO PPP does not support that protocol yet (but it will in 5.0.6). MST PPP supports it already. So if the ISP requires Microsft CHAP, you will have to use MST PPP, and you will probably have to use the "* <password>" form for your Auth file, on account of NT does stupid things with the name field in MS-CHAP challenges. -- Evan Hunt - evanh at sco dot com "The only thing better than normal, everyday spam is spam from the Lord." - Jason Abbott From - Tue Jan 11 15:22:33 2000 From: Richard Seeder <firstname.lastname@example.org> Newsgroups: comp.unix.sco.misc Subject: Re: Only 10% success rate in dialup ISP connection Date: Tue, 11 Jan 2000 09:40:10 -0600 Message-ID: <387B4EDA.AB03DA28@worldnet.att.net> RP wrote: > > The ISP (ATT) requires PAP authorization, no chat script. It gets the > info from my /etc/pppauth file. > > On Mon, 10 Jan 2000 01:06:53 GMT, Steve Wertz > <email@example.com> wrote: > > :RP <firstname.lastname@example.org> wrote: > :> Dual Boot SCO OSR 5.0.4, SCO PPP and Windows95 System. Dial up ISP > :> connection, USR V90 Sportster modem using hardware flow control. > : > :> I have no trouble getting 99% successful dial up connections to my ISP > :> (ATT) using Windows95. With SCO OSR, manual ppp connection, however, > :> using the same computer, same modem, and same telephone line, I > :> successfully connect only about 10% of the time, when the ISP server > :> traffic is heavy, and about 75% of the time, when traffic is light. > : > :> On the failed connections, I observe the modem lights and see that the > :> ISP answers on the first ring , and that the CD light goes on and that > :> my SD light flickers, but I don't see any RD activity, and the > :> connection is lost a second later. The modem timeout setting, 120 sec, > :> is not a factor. > : Don't know if your situation is the same, but AT&T Worldnet uses chap authentication, which requires the ISP's server name in the auth file. The problem is that Worldnet individually identifies each modem, so using a specific name would get you in only when you happened to connect to that particular modem. The solution is to use a wildcard (*) as the system name in the auth file, so it doesn't matter what modem you get. Worldnet's own software, run from Win9x, automatically deals with this, so it connects OK. Kind of sounds like what you're seeing, but ymmv. -- Richard Seeder email@example.com
Got something to add? Send me email.
(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version
Increase ad revenue 50-250% with Ezoic
Inexpensive and informative Apple related e-books:
iOS 8: A Take Control Crash Course
Take Control of Pages
El Capitan: A Take Control Crash Course
Take Control of the Mac Command Line with Terminal, Second Edition
Take Control of Parallels Desktop 12