News Group Posts

Chap in SCO ppp

I have an example of confuring 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: <7imp12$kh0$1@hobbes.sco.com> 


Don't blame me, I voted for Ken Wolff <kenw@dmg-grsd.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 <aapex@worldnet.att.net>
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
> <swertz@swertz.scruznet.com> wrote:
> 
> :RP <rpetkus@attglobal.net> 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
aapex@worldnet.att.net

Comments?

More Articles by Tony Lawrence - Find me on Google+

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.