Technical article 105744

I'm trying to troubleshoot a connection between Morning Star PPP or SCO's PPP and a WindowsNT Server. How do I enable logging on both sides?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

I am having difficulty troubleshooting a PPP connection between a
Windows NT server and either SCO's PPP or SCO PPP from Morning Star.
SCO's PPP and SCO PPP from Morning Star have advanced options and
settings that some PPP clients cannot handle.  Windows NT is one
such client.  How can I set up PPP logging on both sides to help
me find out the cause of the problem?

Cause

Several PPP configuration options may need to be changed for Windows NT to successfully connect with SCO's PPP. Enabling PPP logging on the SCO side may provide very useful diagnostics. The procedures for enabling PPP logging on both SCO's PPP and SCO PPP from Morning Star are outlined below.

It can be helpful to enable Windows NT logging since some types
of rejection are difficult to identify without logging on the
Windows side.  This procedure is outlined below as well.

Solution

Make sure PPP logging is enabled to an appropriate level on the
SCO system.  These vary depending on whether SCO's PPP or SCO PPP
from Morning Star is being used.
Procedure for SCO's PPP logging:

Edit the /etc/ppphosts file and add "debug=<n>" (without the quotes) where <n> is the link debugging level. If <n>=0, no debugging If <n>=1, syslog LCP, IPCP, PAP and CHAP negotiation information. If <n>=2, syslog all PPP packets.

This will enable ppp logging to /usr/adm/syslog.

SCO PPP from Morning Star logging:
Edit the /usr/lib/mstppp/Autostart file and add:
   "debug=<n>" (without the quotes) where <n> is the
    debug verbosity level, chosen from the following table:
      0       Daemon start messages
      1       Link status messages, calling attempts (default)
      2       Chat script processing, input framing errors
      3       LCP, IPCP, PAP and CHAP negotiation
      4       LQM status summaries
      5       IP interface changes
      6       IP message summaries
      7       Full LQM reports
      8       All PPP messages (without framing)
      9       Characters read or written
      10      Procedure call messages
      11      Internal timers the lower-numbered levels

The following is the procedure for Windows NT logging:

To enable WindowsNT logging for troubleshooting purposes, Run: regedit Select the following path: \HKEY_Local_Machine\System\current_control_set\.. ..\services\rasman\ppp Edit the logging file and change the '0' to '1' This enables logging in Windows NT

See also

Manual page for pppd(MST_PPP); Commented section of /etc/ppphosts

ta105447, "Connecting Win95 to MorningStar PPP, what PPP configuration settings should I use?"

ta105634, "Win95 client connecting to MorningStar PPP server, authentication fails.

From the Xinuos technical article database, record 105744. Reproduced with permission. The original is at www.sco.com/ta/105744, 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.