Open Transport/PPP error codes
7102: OT/PPP did not load properly at system start up.
7103: OT/PPP could not set up a port.
7104: OT/PPP is out of memory.
7105: The requested action is not supported.
7106: One or more resources are missing from OT/PPP's
7107: The Remote Access Connections file is not
compatible with the installed version of OT/PPP.
7108: An action requiring a connection was requested when
there was no connection.
7109: The connection attempt or established connection
was terminated by the user.
7110: The user name is unknown.
7111: The password is invalid.
7112: An unexpected error with no useful information has
7113: One or more of the installed OT/PPP files is
7114: The requested action could not be performed because
OT/PPP was busy.
7115: The OT/PPP logical port is in an unknown state.
7116: The OT/PPP logical port is in an invalid state.
7117: The OT/PPP logical port has detected an invalid
7118: Login is disabled for the given user.
7120: The server administrator requires the user to enter
7122: OT/PPP could not initialize Open Transport.
7123: The requested action could not be performed because
OT/PPP is not fully initialized yet.
7124: TCP/IP is inactive and cannot be loaded.
7125: TCP/IP is not yet configured.
7126: PPP is not selected as the TCP/IP interface in the
current TCP/IP configuration.
7128: The requested PPP protocol was rejected by the PPP
7129: PPP authentication failed.
7130: PPP negotiation failed.
7131: PPP was disconnected locally.
7132: The PPP peer disconnected unexpectedly.
7133: The PPP peer is not responding.
7134: The OT/PPP log file is not open.
7135: The OT/PPP log file is already open.
7136: The OT/PPP log entry could not be retrieved.
7138: OT/PPP can not locate the active System Folder.
7139: OT/PPP can not locate its Preferences folder.
7140: There is a preexisting file using an OT/PPP type or
7141: There is a preexisting folder using an OT/PPP
folder name and location.
7142: The Remote Access Connections file is not open.
7144: An unknown PPP control protocol type was received.
7145: PPP received a packet with an invalid length.
7146: PPP received a negotiable option with an invalid
7147: PPP received a negotiable option with invalid flags.
7148: PPP ran out of memory while negotiating with the peer.
7152: PPP encountered an error with no useful information.
7153: PPP is in an invalid state.
7163: The user canceled the password entry dialog.
7164: The user did not respond to the password entry
dialog in time.
7165: An unknown Open Transport serial port was referenced.
7166: The OT/PPP logical port is not configured.
7167: No AppleTalk services endpoints are available.
7168: The user canceled the modem script ASK or the
Manual Dialing dialog.
What does "That pesky MacTCP is acting up again." Message
The PPP/SLIP software is not successfully connecting to your
Internet Service Provider (ISP).
The PPP extension and Config PPP control panel have to be installed,
or the appropriate SLIP software. You need to verify that a modem
connection is made to your ISP before launching a TCP/IP application.
You should launch Config PPP or Config SLIP and dial out through that
- Confirmation messages from the connection software will show when a
successful connection is made,
- Or error messages will indicate what is wrong.
The MacTCP or TCP/IP control panel is not configured correctly.
See the "Correct MacTCP or TCP/IP Configuration Setup" section below
for more information.
The MacIP server is down or does not have an available IP address.
You should select a different zone that also has a MacIP server on the
network. This is selected under the EtherTalk or LocalTalk icon's
pop-up menu in the MacTCP control panel.
The Internet Gateway or Router is down or the address is entered
incorrectly (this usually applies in manual IP configurations). You
have to ask your network administrator for a list of valid Internet
Gateway or Router IP addresses.
The MacTCP or TCP/IP files are corrupt.
If you are using MacTCP, throw the MacTCP control panel, MacTCP
DNR, and MacTCP Prep files into the trash.
- Reinstall MacTCP with a custom installation from the Mac OS 7.5
installer, or drag-copy from previous system versions. You will have
to enter all necessary information in the control panel.
If you are using Open Transport and TCP/IP, throw the TCP/IP control
panel and TCP/IP Preference files into the trash.
- Reinstall the TCP/IP control panel with a custom installation from
the Mac OS 7.5.2 or higher installer. Once at the Custom Install
choices, extend Networking, extend Open Transport, and choose TCP/IP.
You will have to enter all necessary information in the control panel.
The specified protocol address
was in an incorrect format or
contained illegal information.
The specified protocol options
were in an incorrect format or
contained illegal information.
The user does not have
permission to negotiate the
specified address or options.
The specified EndpointRef or
TEndpoint * does not refer to a
The endpoint could not allocate
an address, or an address was
required and not supplied by
The function was issued in the
An invalid sequence number
was specified, or a NULL call
pointer was specified when
rejecting a connection request.
An asynchronous event has
occurred on this endpoint.
The amount of client data
specified was not within the
bounds allowed by the
The number of bytes allocated
to hold a result is greater than
zero, but not sufficient to store
The endpoint is in asynchronous
mode, but the flow control
mechanism prevents the
endpoint from accepting any
data at this time.
This endpoint is in non-blocking
mode, but no data is currently
available. It is also returned by
LookupName when no names
No disconnect indication is
No unit data error indication
currently exists on this endpoint.
An invalid flag was specified.
No orderly release indication
currently exists on this endpoint.
This action is not supported by
The endpoint is undergoing a
transient state change. This
error is returned when a
function call is made while an
endpoint is in the process of
changing states. The client
should wait for an event
indicating the endpoint has
finished changing state and call
the function again.
Note: The equivalent
state-change error code,
TSTATECHNG, is not
described in the 1992 X/Open
This error is also returned if you
attempt to use an
"incompatible" function while
another operation is still
ongoing (for example: calling
SndUData while an
OptionManagement call is still
An unsupported structure type
was passed in the structType
field. This error is also returned
when the structType field is
inconsistent with the endpoint
The endpoint name is invalid.
The argument qlen when the
endpoint was bound with Bind
The requested address is in use,
or this endpoint does not
support multiple connections
with the same local and remote
addresses. This result code
indicates that a connection
already exists. As a return value
for a Bind call, it may also
indicate that no dynamic
addresses are available for
protocols or configuration
methods that allow dynamic
There are outstanding
connection indications on the
endpoint. All other connection
indications must be handled
either by rejecting them with
SndDisconnect, or by accepting
them with Accept.
The endpoint that is to accept
the connection is not the same
kind of endpoint as this one.
When this endpoint was bound
(see Bind), the qlen parameter
was greater than zero. But to
accept a connection on an
alternate end-point, such as this
one, the endpoint must be
bound with a qlen parameter
equal to zero.
The address to which this
endpoint is bound differs from
that of the endpoint that
received the connection
request; thus, this endpoint
cannot accept this connection
The maximum number of
outstanding indications has been
reached for the endpoint.
An unspecified protocol error
A call to Sync was made at
An outstanding call was
The function completed
execution without error.