Apple Remote Access MultiPort Server - Manual (Page 96)

Server activity log error messages
Whenever you’re troubleshooting, check the server activity log for errors, which
are indicated by an exclamation point (
! ). The server activity log records the
most significant events that occur on the server, including errors. This section
presents the most common errors that may appear in the server activity log.
Callback attempt failed: phone number is busy.
The client’s phone was busy when the server tried to call the client back. There
may be a timing problem between the modems (either the server tried to call
back too quickly or the client answered the phone too slowly). Consult your
modem manufacturer or try a different modem.
Callback attempt failed: modems could not connect.
The server tried to call the client back but a connection could not be established.
The client may not be at the callback number specified, or there may be a
modem incompatibility problem.
Callback attempt failed: no dial tone detected.
The server tried to call the client back, but the modem used for the callback
failed to detect a dial tone. There may be no phone line plugged into it, or the
phone line is dead.
Callback attempt failed: client not answering.
The server tried to call the client back but a connection could not be established.
The callback number may be wrong, or another application on the client
computer may be using the callback line.
Connection attempt failed: unregistered user.
The name specified by the client is not a registered user of the server being called.
Connection attempt failed: this port reserved for callback
accounts only.
A user who does not have callback enabled tried to call a Dial-In and Transfer port.
96 Appendix / Troubleshooting