Technical article 105634

Win95 client connecting to Morning Star PPP server, authentication fails.

OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

PAP or CHAP authentication may fail when connecting from a
Windows 95 client to an SCO server running Morning Star PPP.  If
looking through the debug output on the server side (in the file
/usr/adm/pppd.log) you will see either an authentication timeout
error, or an error about the incorrect account name or "secret"
being used.

Cause

Windows 95 does not pass the "name" token as an authentication
variable, so the SCO server tries to authenticate the password
instead of the PAP or CHAP name.  Because the link "secret" is
interpreted as the login name, the negotiation fails while
waiting for the password to be received from the client.

Solution

The Morning Star PPP file /usr/lib/mstppp/Auth can be modified so that it will not expect a PAP or CHAP name for authentication. The format of the file is:

Name                  Secret                  Optional Fields

A typical example would look something like this:

nppp1                 passtest1
but the Windows 95 client will not pass the "nppp1" token as an
argument.  So, we modify the file to look like this:
""                    passtest1
and the authentication should occur normally.  The two
double-quotes ("") tell Morning Star PPP to expect nothing for
the login name, but to check the secret that is sent for a match.

See also

pppd(MST_PPP), ppp.auth(MST_PPP) manual pages, other articles in this database on PPP configuration and troubleshooting.

From the Xinuos technical article database, record 105634. Reproduced with permission. The original is at www.sco.com/ta/105634, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.