Removing a dialout PPP connection
After removing a dialout PPP connection using the
Internet Manager, the line
in /usr/lib/mstppp/Devices for this connection is left
in the file. This may affect future attempts to add connections, should
that Devices file entry be incorrect.
If you are unsure as to the correctness
of the entry, please remove the Devices file entry with a text editor
after removing the dialout PPP connection
with the Internet Configuration Manager.
Multiple PPP lines may
use the same Devices file entry, so beware of
removing this line if you have multiple dialout
When you set the mailer domain in the ``Domain in From: header''
section of the Internet Manager's
``Email Forwarding'' screen, you can only choose the machine's
hostname, or a subset of it. If you want an email domain that is
not a subset of the hostname, you will have to manually edit
/usr/lib/sendmail.cf. Whenever you change any
other system-wide email configuration parameter,
the Internet Manager
will replace your changes with your machine's fully-qualified
domain name, and you will have to re-edit your sendmail.cf file
to undo these changes.
Internet Manager Advanced Security configuration page problem
In the SCO Internet Manager,
on the Advanced Security page,
you must press OK each time you
remove or add to an attribute's set of values.
Remote configuration error and Back button
If you attempt to configure an SCO OpenServer system remotely
using the SCO Internet Manager from a site that does not have
access, you see this error:
Use the browser's Back button to return to the previous page.
In this case, the previous page is the password prompt,
so your browser's Back button is stippled.
Use unique user name when adding new dial-in PPP connection
When adding a new dial-in PPP connection, the
``Local PPP account login name'' may not be a user name that
already exists on the system. Enter a new user name.
This user will be created for use only with this PPP connection.
Deleting a PPP connection on a High security system
Deleting a PPP connection (with the Internet Manager)
on a system that is configured for High security will display an error message
because users cannot be deleted on High security systems.
The PPP connection has been deleted, but not the user identified
as that connection's ``Local PPP account login name.''
To prevent the use of the user account that was associated
with that PPP connection,
use the Account Manager to lock out
or retire the user.
Line not dropped when active inbound PPP connection deleted
If you delete a PPP connection (with the Internet Manager)
while that connection is active, the line will not be dropped,
the pppd daemon will not be killed, and the
/dev/tty* file will still be owned by the UID
of the deleted user.
To correct this, the system administrator should kill the
orphaned pppd process (or reboot).
Using PPP to connect to SCO UNIX Release 3.2v4.2 or SCO Open Desktop Release 3.0
Before using PPP to connect your
SCO OpenServer system
to either of the following systems,
you must first install Support Level Supplement (SLS) net382e
on that system:
SCO UNIX System V/386 Release 3.2 v4.2.0 system
with SCO TCP/IP 1.2.1
SCO® Open Desktop® Release 3.0
This will prevent intersystem PPP option negotiation problems.
You can acquire a copy of SLS net382e from
the SCO Support Online Services, at:
If you are using PPP to connect to an SCO system
running a release of SCO TCP/IP earlier than 1.2.1,
avoid LQM option negotiation problems
by adding the PPP option nolqm
to the end of the line for that connection in these files
on your SCO OpenServer system:
/usr/lib/mstppp/Autostart (for outgoing connections)
/usr/lib/mstppp/Accounts (for incoming connections)
PPP connections not counted as logins
PPP sessions are not counted as user logins
for the purposes of licensing.
No additional SCO OpenServer Enterprise
user licenses are required to support
multiple simultaneous PPP connections.
Document contains no data error
Slower systems configured with more than one interface
may experience time-out problems.
After you press OK on the
Set Up Packet Filter Data Flow page,
time out before the Internet Manager can set up
packet filtering and respond.
If this happens, press the Reload button to return to
the Set Up Packet Filter Data Flow page
and try again (this may require more than one try).
Not a mana document: / error
You may get this error when remotely accessing
the Internet Manager if
you entered http://hostname:458/mana/mana
(the browser is appending a final ``/'').
Try again, using the correct URL: